Pending Failing to confirm ready for Game 2/3 should result in auto-loss

The structure of Best of 3 matches being in different subrooms allows for players to quit one of the games but still be placed into the next one when it begins. This is fine in principle, but has the upshot that the second game doesn't register a player disconnecting from the first game and enforce the 1-minute disconnection auto-loss, which then forces the remaining player to play a non-game to resolution.

I know there have already been suggestions for timer losses over sustained inactivity or going to timer on multiple consecutive turns, which have been shot down over concerns that there are legitimate reasons to go to timer in such cases, but I think there are two things that make this different:

1) There is absolutely no reason to not confirm ready for the next game immediately. There is no decision making process except "do I want to continue this match?" If the answer to that question is no, the player should auto-lose anyway.

2) The consequences to the other player are more severe. As opposed to a few turns of waiting an inactive player out, the remaining player is forced to play an entire second game against an absent opponent.

If this still seems too harsh, I would suggest making it so that players are not automatically placed into the next game when it starts, and only join when they click the 'ready for game 2/3' button, and if a player hasn't connected by the time their opponent has chosen their team, they are subject to a disconnect timer.

As a sidenote to all this, it should also be possible to report players for stalling/quitting chess.com style.
 
As a sidenote to all this, it should also be possible to report players for stalling/quitting chess.com style.
No. Never going to happen.

Anyway, as it is, I designed the next game timer to give players time to breathe between games. It's also designed to enforce the disconnect timer side-by-side with the 'start next game' timer - ie, if a player has a dc time of 60 seconds, it'll wait 60 seconds for confirmation before disconnecting them. If they've already been disconnecting in that battle, the dc timer will be lower, and it will likewise give them less time to confirm for the next battle. If it's not doing that, that's a bug.
 
Back
Top