Lobby Refresh/Joining Issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gang Garrison 2 |
Fix Released
|
Low
|
Unassigned |
Bug Description
Occasionally, I've experienced a bug when leaving a server. After leaving a server and attempting to join another on in the lobby, the lobby will instead refresh. This will continue to occur even upon exiting to the title screen and then rejoining the lobby. What is stranger is after experiencing this bug, going to Join Manually and using the default data(loopback + 8190) will attempt to the connect to the server you tried to join before encountering the refresh bug. I'm guessing the client gets the data of the server but doesn't actually do anything with it when it refreshes?
If this was a confusing explanation, you can PM me on the forums([NIGA] LC) and I can try to give a better one. Thanks.
Changed in gg2: | |
status: | Fix Committed → Fix Released |
When you click a server in the lobby, GG2 instantly starts connecting and considers this as being "in a game", even though you don't see any reaction yet. If a server does not respond it will take a few seconds until the connection attempt fails. If you click a different server (or the same one) during this time, the old connection attempt will be aborted and gg2 "leaves the game" by going to the lobby room/screen. Since it never left that room though, this just looks like a refresh. GG2 then starts a new connection to the server you clicked. If this one is unreachable too (perhaps because it was the same one), this process can be repeated several times. If you just stop and wait for a few seconds, you should get a "Connection failed" message after a few seconds.
So, until that point there is probably no actual bug, although it might be a good idea to switch to the same room used for map downloading immediately when starting a connection and showing a message like "Connecting, press Esc to abort", so that players will know what is going on.
As far as I remember, the "join manually" code works a bit different and simply does nothing if there is still a connection attempt running, which explains why you got connected to a server you tried joining earlier - perhaps there was a connection hiccup and it finally reacted.