Suggestion: Change the logout process

Council Of Stellar Management Assembly Hall
1

I understand that regional disconnections may not be a server-specific issue, given the global nature of the server.

However, if they can’t fix the disconnections, they need to take steps to mitigate of it’s impact.

One issue is that disconnections while cloaked can cause significant losses in information warfare (especially in blackout systems like Wormhole).

If the client is terminated while cloaked, it’s reasonable to maintain the cloak status for five minutes before proceeding with the logout process - to give them chance to reconnect.

Being left in an unmovable state for 5 minutes is not beneficial at all, so there is little room for exploitation.

2

I would assume a disconnect would be considered a safe log off. If so the ship warps away from its position

1 Like
3

Indeed. Though to be precise an emergency warp will trigger (on time out).

Though keep in mind that:

  • It may take time (sometimes even several minutes) for the server to register the disconnect (time out) thus it is possible you can sign back in before it happens and if you had cloak running it will still be running unless something prevents it (capacitor runs out, decloaking effect or by moving too close to an object, etc.)
  • If you’ve turned off emergency warp then it will not trigger on disconnect (time out) but I’m not sure if in that case your ship will still run its modules, but probably it will. Just a guess though.
4

In my recent testing, all modules that were running at the condition emergency warp deactivated continued to function when client terminated, except for the cloaking module.

I know this is a measure to prevent exploits.

What I’m saying is that, whether it’s a selective client shutdown or a disconnect, cloaking should be maintained for 5 minutes, and then decloaked and warped out should be performed just like any other logout process.

This takes into account the high probability of experiencing disconnects during operations due to the long-term of cloaking modules in space, and the potential for information warfare damage even when declocked from a distance.

Again, being left in space for five minutes without being able to move is unlikely to be exploited.

I’ve experienced numerous failures due to disconnects during cloaking operations.

It’s not fun if I think an operation failed due to a technical issue rather than a game-related one.