Disconnect Buffer for Winning Positions

Sort:
Avatar of GMLeu

Feature Proposal: Disconnect Buffer for Winning Positions

Problem:

Currently, Chess.com gives disconnected players 2 minutes 30 seconds to reconnect. While this prevents abuse, it unfairly punishes players who are clearly winning but suffer an unavoidable internet hiccup. Losing a completely winning game this way feels worse than any blunder.

Proposed Solution:

Introduce a hidden reconnect buffer for players in winning positions.

  • Trigger Condition: If Stockfish evaluation is +3 or higher in favor of the disconnected player at the moment of disconnect.
  • Buffer Length: Extend reconnect time to 4 minutes total.
  • Hidden Mechanism: Both players only see the standard timer (2 minutes and 30 seconds). The extra 90 seconds is invisible.
  • Fairness Protection: If the disconnected player is losing or equal (eval < +3), no extra time is given.

Why This Works:

  • Prevents abuse: Since players don’t know when the buffer applies, they can’t exploit it.
  • Protects fairness: Winning players won’t lose purely to internet issues.
  • Maintains opponent’s experience: Opponents still only see 2:30, so no one feels stalled.
  • Aligns with competitive integrity: A decisive winning position deserves to be played out, not decided by WiFi drops.

As an example:

In a recent game I played, I was completely winning (up a full rook and pawn w/ eval at +5) when my connection briefly dropped. Despite having a decisive position, I was flagged as lost after 2 minutes and 30 seconds. A hidden reconnect buffer in such cases would have preserved the fairness of the result without affecting my opponent’s experience.

Of course, as any other player I thought that it would just be a small WiFi hiccup that would only last 30 seconds up to 1 minute. But after seeing it's still not reconnected, and that the WiFi logo on my phone had an exclamation mark (!) next to it, I immediately went to turn it off and on again asap. But unfortunately, I had to wait for a whole minute for it to come back, being delayed by 5 seconds after the reconnect timer went to 0.

Avatar of justbefair

Seems like a good idea. I can't believe that they currently give two and a half minutes. I think the length of time depends on the time control.

So it seems like they already have an evaluation in place for a disconnect while losing. Seems like it shouldn't be that hard to add a disconnect while good case.

Maybe you could submit it as a suggestion.