Christopher Head
Comments
Torabi, that seems very likely. In which case the bug is that one of the messages is printed in the wrong place: either the connected message should be printed earlier (so it would show up in this case), or the disconnected message should not be printed for a connection that fails at this stage.
Aden: This is hosted on a machine under my physical control. I am the only person with SSH access. It is not whitelist-controlled, but is not advertised anywhere except to friends. Your last line is indeed the problem: player disconnect message without player connect message. While I did not recognize the username in this particular case, I am fairly sure (but not 100%) that I have seen the same effect with people I do know. Also, the IP address was from a local ISP and could very reasonably be a friend-of-friend.
I would like to add an additional piece of data: the username listed in the disconnect message does not have a file in the players/ directory!
Kumasasa: The bug is that the connected message is missing. The username and IP were included in the original output and look reasonable; I redacted them here for privacy because this is a public tracker. This text was actually taken from the server console, not the log file, though the same appears in the log file as well. There was enough scrollback in the console to see server startup, and note that the “list” command was issued at the top of the snippet and indicated no players connected at that time.
Mustek: I obviously have my own server in my client’s server list. I started my client, went to the server list, even pressed Refresh a few times, and shut down the client. There was no output on the server console. Viewing a server list containing the server in question does not produce this effect.
Unfortunately, I do not know how to reliably reproduce this bug so cannot answer one way or the other whether it still exists in current versions.