You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Separating this suggestion to a new feature request.
Being blindly dumped at a random spawn location is not user friendly as it can lead to the victim being spawn killed a significant amount of times in a row, literally 6 or more times is not uncommon for me.
Being dropped into the middle of a dozen torpedoes coming at you from all directions with no way out or right near some spawn camper level 9 destroyer/carrier indiscriminately sinking everything in sight is real annoying at the minimum. Especially with the overly severe sinking penalty currently deployed.
When you are sunk you can still see whats going on in the location you were sunk at. I would submit using a similar technique for the spawn after sinking and give the user a button to either accept or reject the randomly chosen spawn or alternatively allow the user to delay the spawn at that location for a period of time to let things cool down somewhat.
The text was updated successfully, but these errors were encountered:
Being blindly dumped at a random spawn location is not user friendly as it can lead to the victim being spawn killed a significant amount of times in a row, literally 6 or more times is not uncommon for me.
Yikes...
Being dropped into the middle of a dozen torpedoes coming at you from all directions
I keep saying/thinking we need to fix this, but then I forget.
right near some spawn camper level 9 destroyer/carrier indiscriminately sinking everything in sight
The code is supposed to make this rare (the code will reject over a hundred bad spawns, searching for a good spawn, before settling on a mediocre spawn). But maybe it's not rare enough.
I would submit using a similar technique for the spawn after sinking and give the user a button to either accept or reject the randomly chosen spawn or alternatively allow the user to delay the spawn at that location for a period of time to let things cool down somewhat.
Being able to see where you will spawn sounds great from a player perspective. However, the implementation is not necessarily possible as described. What happens if the game allocates some space but another player wanders into it? Or if a dredger puts land? Or if the border shrinks? Of if the land un-erodes? Or a player/oil rig spawns? Lots of edge cases there.
Seeing the spawn point before choosing a vessel would help as well. Choosing a Drednaught and being spawned into an area with a lot of subs means I won't stand a chance. Even showing the general area chosen for your respawn, choosing a vessel, and then getting a final allocated space with a quick camera move from your pre-spawn view to your actual spawn location.
While we're brainstorming, the ability to have 3 seconds to choose a bearing before getting a random one would be great. If I see I'm spawning into a wall of torpedoes, I'd rather be able to face into them and be hit by one than spawn in sideways and take them all broadsides.
Separating this suggestion to a new feature request.
Being blindly dumped at a random spawn location is not user friendly as it can lead to the victim being spawn killed a significant amount of times in a row, literally 6 or more times is not uncommon for me.
Being dropped into the middle of a dozen torpedoes coming at you from all directions with no way out or right near some spawn camper level 9 destroyer/carrier indiscriminately sinking everything in sight is real annoying at the minimum. Especially with the overly severe sinking penalty currently deployed.
When you are sunk you can still see whats going on in the location you were sunk at. I would submit using a similar technique for the spawn after sinking and give the user a button to either accept or reject the randomly chosen spawn or alternatively allow the user to delay the spawn at that location for a period of time to let things cool down somewhat.
The text was updated successfully, but these errors were encountered: