Closed hwoodward closed 4 years ago
Ideas: On server side disconnect during an active game - keep the player object with all the status around. On client side don't quit - try to reconnect with a saved code from the server
On server getting a connection request during an active game - look for the 'reconnect code' information in the connect request and verify it.
Also look into if podsixnet has any options for handling a weaker connection. (I know they don't yet allow UDP communication)
PodSixNet doesn't seem to have any current options to help with this. We will have to see how common it is to get a sense of what is 'good enough' for a fix.
Describe the bug When a player crashes out and disconnects from the server we get stuck when it reaches there turn (see #12 for plans on how to proceed if they quit and aren't coming back). We also have NO mechanism for allowing them to reconnect.
To Reproduce Steps to reproduce the behavior:
Expected behavior We want to save a status and reconnect ability for the clients. Ideally knowing their name or a code given on startup would allow you to reconnect. We also want them to come back with all their information intact.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.