In fact, PS handles packet loss very well AFAICS. According to my logs, the client is dropping massive amounts of packets all the time due to my machine being unable to handle the load.
As has been mentioned, the real cause for linkdeads are server crashes, which simply are a matter of time until they\'re gone.
However, there is something I wish for regarding the linkdead issue: the client should not quit. If anything, it should go back to the main menu (login screen). Or, even better, it should ask whether to do that or to \"freeze\" the current game (having stored the login details and char selection) and periodically trying to relogin automaticly.
Obviously, upon reconnection, you\'d be autospawned to whereever and in whatever condition the server last saved your char, but you wouldn\'t have to go through all the loading stuff.
Furthermore, how about a \"save\" function? I know it sounds crazy, but IMO it makes perfect sense.
After all, \"logout\" is coupled to \"save\" already, so why not have \"save\" separately? There wouldn\'t be any way to abuse it, because the client would just send \"save\" to the server, which would do the save, i.e., just like \"quit\" with immediate relogin. This way, you would be able to mitigate the possible impact of linkdeads without the pain of going through restarting the client.
To ease the impact of players keeping pressing \"save\" every second, the save command could be limited to once every 30 seconds or something, so that players would still not mindlessly keep saving every minor change, but major ones.
