Reconnect does not work correctly #502
Comments
|
Here are some log example of my own disconnect during a tournament match: Client Log: |
|
My question is - why do you need to handle manual disconnects differently from connection losses? Could you simply make it so if one play disconnects for any reason - as long as one player stays connected, the game will exist still giving the other a chance to reconnect? To help with server issues, I think it would also be a good idea to have some sort of time (5-10 minutes maybe?) where if both players disconnect it doesn't immediately end the match. This gives one or both parties a chance to reconnect right away and not let the current match be lost. |
|
The point is that people playing and if they are loosing or stop playing for other reasons, they often simply close XMage and don't concede the match regularly. So in all this cases (and believe me this happens a lot), your game and you would hang around for some more 5-10 minutes until the game ends. But at least it would be a possible direction to go. Maybe we could ask the user while closing XMage if he want's to quit all running matches/tournaments (set "yes" to default) and if the server does not get this response explicit, we handle it as a "lost of connection". So all unexpected disconnect reasons should be handled as "lost of connection" and the user should be able to reconnect. |
|
Another problem with reconnect I identified is that for every reconnect the card db check for new cards is done. That slows down the server especially if multiple clients get disconnected at the same time and try to reconnect. Than the h2 db requests are probably a bottleneck. |
|
I'll close this issue because it seems to be outdated. |
Currently the reconnect to games / tournaments does not work correctly.
If I test it local by killing a client it works.
But on public server it does not work.
It seems like connection lost is handled like a manual disconnect.
Any ideas / suggestions are welcome.
The text was updated successfully, but these errors were encountered: