While some players are playing they get kicked and this message is spammed over the console
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Kicking player ID 0, no record of such connection ID exists.
Any idea why that happens?
In between the player being kicked and the player receiving the kick message, their sync packets will still be sent to the server, especially with players with higher pings. Because the server already kicked them and cut off their connection, it sees sync packets from these players as having no such connection ID.
Main point is why Kicked? Why does the server kick them? There should be a reason they get kicked.
Quote from: Doom_Killer on Jun 25, 2015, 05:35 PMMain point is why Kicked? Why does the server kick them? There should be a reason they get kicked.
Because they don't have a valid connection ID anymore. They'll get the original kick message but if we keep accepting their now-invalid packets you'd probably cause clients or the server to crash by referencing a player that technically doesn't exist at that moment.