What about some lil code that checks if client was closed properly and if it wasnt aka it crashed, it wouldn't kick us out of instance so quickly?

Can't do that, all the server knows is that the client is no longer connected, the client can't send a message cause it's crashed.

Also, instance kick out time is 30 minutes, ample time to re-open your client.

Except you've lost keys that decay when you exit the game.

That's a completely different issue.

30 Minutes? That's something different then, I'm talking about 5 minutes or less kick out.

I know that its impossible for crashed client or even worse crashed comp to send a msng to server. But it should be possible to make default kickout time longer and then make client send msng that it was healthy and intended logout and therefore kickout time should be quicker.

I don't think this is possible either, unless you manually used the log out option, instead of just closing the window.

It definitely takes 5 minutes or less to kick out of Olympus, Blue Dwarf.

5 minutes is still enough time to restart a client, 5 minutes is enough time to restart a computer and router.

Not if a client patch has gone in in the meantime and patchbot is taking its sweet time to run.

except when its instant crash (the kind that doesn't reach the dump file creation). The socket is closed correctly so its quite hard for the server to tell really.

Its not impossible to catch every exits and somehow allow the server to know you crashed instead of dced, but it most likely represent quite a bit of work (not the kind of things i can slip in between 2 tasks).

oh it shouldnt distinguish crash from dc, both should get increased kick out time, it should distiguish crash/timeout from alting