Proposal Discussion Method for combatting ctrl-alt-del'ing players

Since Frontier really don't want players to be doing this as it causes CTD's on others, perhaps a method of combatting it could be along the following lines:

If a player ctrl-alt-dels / is not heard from by the instance controller for a period of time, their ship is kept in the instance on autopilot flying in a straight line so that it does not crash other players in that instance.

When connecting to multiplayer, as part of the server authentication - the client encrypts the save game file using a key, with it being sent to the remote server to compute the decryption key. Obviously, this will require separating out 'single player' save games from 'multiplayer' save games.
When a player *cleanly* exits the game - the server sends the decryption key to use to restore the save game / transmits a clean copy of what their save game should be.

If a player's save game cannot be read (still encrypted) - it requests the remote server send them a copy of their most recent save game from the servers, which then replaces the one on their machine and is re-encrypted. This request is logged and if it happens too many times just after they were killed - the server refuses and the players save is intentionally left corrupted. This would require them to start a new commander from scratch.


Alternatively - Each time the player connects to multiplayer - their save is re-downloaded from the servers each time, rather than using the locally stored save game.

The idea is so that the servers will be the authoritative source for the save game file - if the server says you died then you died.

Any thoughts / potential problems with this idea?

Edit: Bah - clicked the new thread button in the wrong tab! Could a mod please move this to gameplay+features :)
 
Last edited:
I'm hoping that adding Law enforcement would help with a lot of ctrl-alt deletes.

At present a lot of players are doing that when they are killed by griefers, past that point I'm hoping that FD can come up with a working solution.
 
It might be worth the autopilot shutting down the ship engines instead and drawing to a stop in case of terrain in the flight path.
 
Please don't. I'm expieriencing regular disconnects because someone cut the wrong wire and now everytime someone picks up the phone, the internet is down. It's like I'm back in the 90s (though I wouldn't remember a thing of it honestly :p). So don't add some sort of countdown... There must be another way
 
It sounds like your filter is broke, I had that problem once.

The only thing I can think of is if the game saves as soon as you are killed. It would cut down on the effectiveness as people might not have the time to always react.
 
Last edited:
There kind of needs to be some sort of heartbeat to the public IP of the broadband router to check network status (that's quite a lot of ICMP (ping) traffic though, and having to maintain state for every connection in the game).

That way the perpetrator would need to restart or disconnect their router to simulate a broadband network break - which takes time to do as the router has to resynch. It also means that gamers who have genuine network issues are treated as fairly as they can be.

You'll never cut this kind of thing out completely but it has to be made as inconvenient as possible.
 
Please don't. I'm expieriencing regular disconnects because someone cut the wrong wire and now everytime someone picks up the phone, the internet is down. It's like I'm back in the 90s (though I wouldn't remember a thing of it honestly :p). So don't add some sort of countdown... There must be another way

Sorry to say, but most likely it that's how it will be implemented, at least that's how it was discussed in FD.
 
Back
Top Bottom