warzone2100
warzone2100 copied to clipboard
Inf. lag when somebody closes game incorrectly
Sometimes socket (connection) to client can not be closed properly and TCP socket does timeout super-slow causing infinite "zzz" appear. During this time only thing host can do is to kick this player from the room. Problem become 100 times stronger inside an autohosted rooms where there is no host to interact or no GUI/renderer present to do so (like in Autorating). Possible solution is to auto-kick players if several ping requests timed out or no socket activity detected for a long time. This "broken" connection is not reproducible (at least I failed even with router poweroff). However some people (again in Autorating rooms) had issues with connection reset: on client shows up host quit message and on host just player dropped/left, this issue can be somehow connected. Confirmed on 3.4.1
If still the case, that could be a major issue.
It is in fact still the case but there is autokick option now however it only works in-game, not in loading phase.
@maxsupermanhd Can you please create a separate issue for auto-kick not working during loading phase and link it to this one?
@maxsupermanhd Can you please create a separate issue for auto-kick not working during loading phase and link it to this one?
It is this issue https://github.com/Warzone2100/warzone2100/issues/3781 but one described here is still a fundamental problem with how game handles connection of clients. Autokick is a crutch made personally by me for me and autohoster and not a correct solution. There should be some heartbeating/pings and automatic disconnects (autokick) but with ability to cancel it.
Correct and only actual solution is to implement reconnects.