Aggro Range Issue and Ridiculous Spawn Distance (Flintlock Peninsula to Discovery Ridge)

  • KayraKeriKupcu
    Sailor

    Hi everyone,

    We recently experienced a very frustrating situation and I wanted to bring it up here to see if this is a known bug or intended mechanics.

    We were about to dock at Flintlock Peninsula when a Skeleton Ship suddenly aggroed on us. Even though we managed to pull right up to the island, the Skeleton Ship did not lose interest or de-spawn; instead, it kept bombarding us from a distance.

    Deciding to fight back, we sailed away from the island to engage them. Just as we were about to sink them, a sudden explosion (likely a Gunpowder Barrel) killed both of us on the crew at the same time.

    When we respawned, we expected to be somewhere nearby so we could sail back and recover our lost loot. Instead, the game spawned our new ship at Discovery Ridge, which is literally the furthest possible island from Flintlock Peninsula. Needless to say, we lost all of our hard-earned loot because of this absurd distance.

    I have two main questions/complaints about this:

    Skeleton Ship Aggro: Isn't it a bug for a Skeleton Ship to keep attacking and targeting you even after you've nearly fully docked at a large island? Usually, they are supposed to lose interest or back off.

    Spawn Distance: Why on earth does the game spawn a ship at Discovery Ridge after sinking at Flintlock Peninsula? It honestly felt like the game was intentionally punishing us. At this point, just kick us from the server entirely; it would be less insulting than making us sail across the entire map for no reason.

    Has anyone else experienced this crazy spawn behavior or persistent Skeleton Ship aggro recently? Thanks for reading.

  • Login To Reply
    7
    Posts
    463
    Views
  • Ekvator Tilkisi
    Rogue

    Hi everyone,

    I was the other player in the crew during this incident, so I wanted to share my perspective as well.

    I was the one dealing with the Skeleton Ship while we were on board. As described above, our ship eventually sank. It could have been another player, it could have been our own mistake, or it could have been something we simply didn't notice. In the end, our ship sank, and we fully accept that.

    What doesn't make sense to us is what happened afterward. We sank on the far eastern side of the map, yet our new ship spawned all the way over on the western side. That part felt very strange.

    We hadn't played Sea of Thieves for almost two years and only came back earlier this week. Has the game's respawn system or the current meta changed while we were away, or did we encounter some kind of bug? In the past, whenever our ship sank, we would usually respawn close enough that we still had a chance to sail back and recover our treasure if we were quick enough.

    Because we were spawned so far away, there was no realistic way to return in time, and around three hours of progress ended up being lost.

    Thanks for taking the time to read this, and fair winds to everyone!

  • D3ADST1CK
    Vanguard
    Insider
    Founder

    @ekvator-tilkisi said in Aggro Range Issue and Ridiculous Spawn Distance (Flintlock Peninsula to Discovery Ridge):

    What doesn't make sense to us is what happened afterward. We sank on the far eastern side of the map, yet our new ship spawned all the way over on the western side. That part felt very strange.

    If you sink from PvE, you will respawn close. If you sink from PvP, the game will try to place you far away to prevent ships from being able to re-engage immediately.

    Spawning at the other end of the map after a keg explosion seems to point to a player on a different crew sinking you with a keg.

  • D3ADST1CK
    Vanguard
    Insider
    Founder

    @kayrakerikupcu said in Aggro Range Issue and Ridiculous Spawn Distance (Flintlock Peninsula to Discovery Ridge):

    Skeleton Ship Aggro: Isn't it a bug for a Skeleton Ship to keep attacking and targeting you even after you've nearly fully docked at a large island? Usually, they are supposed to lose interest or back off.

    No, the only way to get them to back off is to get a lot of distance between you. Parking at a large island will just get them to circle the island and continue shooting at you. They will also despawn if a Skeleton Fleet World Event spawns.

    Spawn Distance: Why on earth does the game spawn a ship at Discovery Ridge after sinking at Flintlock Peninsula? It honestly felt like the game was intentionally punishing us. At this point, just kick us from the server entirely; it would be less insulting than making us sail across the entire map for no reason.

    See my post above for a reason.

  • BurnBacon
    Vanguard
    Insider

    We recently experienced a very frustrating situation and I wanted to bring it up here to see if this is a known bug or intended mechanics.

    things like this should be Sent to Support.

    Just as we were about to sink them, a sudden explosion (likely a Gunpowder Barrel) killed both of us on the crew at the same time.

    Yup, those new skeleton ships tend to have the smugglers' kegs on board. If your far away, no problem. Happens to the best of us.

    When we respawned, we expected to be somewhere nearby so we could sail back and recover our lost loot. Instead, the game spawned our new ship at Discovery Ridge, which is literally the furthest possible island from Flintlock Peninsula.

    Yup. Players didnt like when a player ship would sink, they spawn say 2 islands away. So they meddles with it and this what happens...

    Isn't it a bug for a Skeleton Ship to keep attacking and targeting you even after you've nearly fully docked at a large island?

    No. They dont care, it use to also spawn on you from the depths while you were on the island, but that was removed.

    Usually, they are supposed to lose interest or back off.

    Nope.

    Why on earth does the game spawn a ship at Discovery Ridge after sinking at Flintlock Peninsula?

    many factors. Could be there wasn't enough "safe space" near DR to spawn you, and as said before. Players complain about sunk player ships spawning so close to where they sunk/Near other players.

    It honestly felt like the game was intentionally punishing us

    You sunk, due to carelessness. Yeah. Lesson learned.

    just kick us from the server entirely; it would be less insulting than making us sail across the entire map for no reason.

    Nah, I rather stay on the same server, and idk..NOT sail back knowing the loot wouldnt be there. :/

    We hadn't played Sea of Thieves for almost two years

    A lot of nonsense changes were added. Blame the "community" for these changes.

    around three hours of progress ended up being lost.

    Whew...3 hours of loot and you never thought, Hey...maybe we should sell stuff? If it wasnt a Skeleton ship that sank you, a Player would have and same results.

  • Europa4033
    Commander
    Insider

    Did your crewmate light the keg on the skeleton ship without saying anything?

  • Boneheart1237
    Marauder
    Insider

    @kayrakerikupcu said in Aggro Range Issue and Ridiculous Spawn Distance (Flintlock Peninsula to Discovery Ridge):

    Skeleton Ship Aggro: Isn't it a bug for a Skeleton Ship to keep attacking and targeting you even after you've nearly fully docked at a large island? Usually, they are supposed to lose interest or back off.

    I don't think so, I've been attacked by skelly ships at port and even during forts before

    Spawn Distance: Why on earth does the game spawn a ship at Discovery Ridge after sinking at Flintlock Peninsula? It honestly felt like the game was intentionally punishing us. At this point, just kick us from the server entirely; it would be less insulting than making us sail across the entire map for no reason.

    I think the respawn location is random, but I'm not too sure. The caveat to a closer respawn point would be an enemy crew returning over and over again despite sinking, which in the past has been pretty annoying before the merge on sink changes

Login To Reply
7
Posts
463
Views
3 out of 7