Sunk ship spawn locations are broken

  • Since siren song voyage any ship sunk, even those not doing the voyage now spawn an island away. No matter where we are. Twice now I've stolen a fort of the damned, and every time the ship spawns one island over and is able to come back to contest before we even take supplies.

    This happens away from fort of the damned, after sinking a ship 5 times in 10 minutes, we were at reapers, when they spawned once again one island over. We actually saw them just appear, and then immediately drop sails to come once again contest.

    Im sure this is an unintentional change, but it's ruined contesting forts or even doing world events as a whole. At least before this update if you had a ship keep coming to contest you would typically have 5+ minutes to repair, resupply, and continue the event. Now it's just a drain on supplies.

  • 10
    Posts
    7.2k
    Views
  • I'm going to agree. We were running FOTD tonight without the siren song quest activated. We stacked a few forts and then a ship came at us. We sunk them and they spawned at Snake Island. 1 Island away. Before we could regroup they were back and sunk us. We spawned at Port Merik. We saided back and sunk them again. They spawned at Crooks Hollow. We sunk them again and they spawned somewhere close by because they were back before we finished another wave. They sunk us and back to Port merik. We sailed back and got sunk again and this time we spawned at Smugglers Bay. We got back too late. Why are they spawning so close every time?

  • As long as those defeated are willing to keep trying that is a good thing compared to those who are defeated and whine on the forums.

    It has however made it harder for those who at the core want to avoid PvP. But soon those who want to avoid PvP will have Safer Seas.

  • Multiple times the same ship spawned within view the other night when me and a buddy were playing. Weren't doing the siren song event or anything, just getting attacked by the same guys.

  • Highly disappointed to see this wasn't addressed with today's patch.

    For SoSS, the close respawns make total sense. For everything else, it's borderline game breaking.

  • For those complaining about the spawn location. How do you know the other crews don’t have the voyage voted down? You don’t.

  • @tesiccl

    Because there's no voyage active for anyone as its in the cooldown period. This isn't a troubleshooting exercise, it's been proven by multiple streamers that the close respawns are active regardless of the SS being opted into.

    We had to sink a brig 4 times the other day after they respawned an island away after we stole their stacked Veils. I boarded them MULTIPLE times and got confirmation that they were not opted into the voyage. The message was NOT on their mast, nor was it on ours.

    It's 100% broken.

    EDIT: Timing was impeccable. This happened just a minute ago to Hitbo after they sunk a crew fighting over a FoTD.

  • @tesiccl It sounds like if you have the voyage voted on then getting sunk by anybody at any event causes you to spawn one island over. This is causing some players to vote on the skull mission even though they have no intention of completing it because of the close to action respawn if they get sunk. I agree with @SweetSandMan this is a game breaking and I would consider it an exploit.

  • Ship respawns are definitely broken atm. It's not just when the siren song voyage is active; ships are now respawning much closer than they used to. It's a big problem for game balance and needs to be fixed.

  • As fun as it is to have a constant stream of ships coming to get sunk, getting attacked by the same brig/sloop several times when trying to move the loot from a Fort of Fortune is a bit tiring.

10
Posts
7.2k
Views
1 out of 10