It is not just about "a stable internet connection". It depends how far the players are away or how well their isps interact. IMO: The auto-pause on disconnection feature from autociv should get implemented in the main game. Connection, disconnections, pauses should be logged. Logging should be done with timestamps

The problem is that without retrieving reports from all players, we don't know if the game is still in progress. As there is no artificial limit to the duration of games, we'd have to wait a few hours to be reasonably sure it's over.

@Atrik: fix pingall pls Line 15 ChatCommandHandler~autociv.js const ignore = new Set([selfNick].concat(this.botsListIgnore)); const ignore = new Set([selfNick].concat(that.botsListIgnore)); change this to that and add "WFGBot" to botsListIgnore  

@Dunedan I made this thread primarily to see whether we could conclude that this is indeed the preferred solution in the first place, or what else. What's your take on this? About the implementation: Your idea of recording the game starts sounds pretty good to me. The rating taking a few hours to update would be suboptimal in my opinion, though, since players might not know or notice that it happens. I guess, better late than never, but maybe we can figure out a way to make it work without such a delay?

It wasn't included in R28 because we were already way to far into the release process by the time I opened the PR. But, yes, the implementations are done, what's left is reviewing, finalising, and eventually merging it. My goal is to get everything into R29. I'm working on it.