Occasionally my Wi-Fi connection is interrupted and I am disconnected from the Showdown Server. Even if the interruption is for less than a second I will lose connection to the server. The game won't acknowledge this until a minute or so has passed, and instead essentially freezes. After realising I've lost connection, the fastest fix is to restart Showdown.
Couldn't find anything else about this and assuming the problem is server/application side. Would like a more reactive or intelligent design that addresses the stagnant wait or inability to automatically reconnect. Thanks.
I hate dealing with this
With my crummy internet, I'm almost always stuck in a state of limbo where my messages take a moment to actually go through (if at all) and clicking buttons and usernames takes a while before they actually do anything.
If there were some kind of loading icon or progress bar to indicate when this happened, it'd be a lot better than thinking that you're still connected, just to find that the move you clicked a minute ago hasn't actually gone through yet and having to constantly check this by clicking usernames to see if they load in or doing /test or something.
Thirding that this is an issue for me as well with poor Internet (2.3 Mbps download 0.42 Mbps upload according to Google's speed test). Occasionally I do get a proper disconnect message, but there are many times where I am just stuck in limbo and have to manually type a command to see if I'm still connected. Worse yet, sometimes I am connected and my internet was just lagging, so when I refresh, sometimes the delayed messages will just load up for me properly right before the refresh.
This is especially impactful in battles, where I might be playing an opponent, and it seems like they're taking a long time to choose their move, when really I've DCed and now I lost because I couldn't see them turn on the timer. Now, having dealt with this for a while, I know to check when my opponent hasn't moved after some time to make sure I'm just not in limbo, but it is definitely an inconvenience.
This is all probably something to do with websocket connections, but if it would help to run something custom in the Javascript console to help narrow down the cause of this, I'd love to volunteer to help.
