- Blind mode tutorial
lichess.org
Donate

What If 2 players resign at the same time?

I know it’s almost impossible for 2 players to resign at the same time. But I’m just curious. This is also my first forum on Lichess.

I know it’s almost impossible for 2 players to resign at the same time. But I’m just curious. This is also my first forum on Lichess.

We should try that some day
But I guess that the one who clicked 0.001s earlier would be the one resigning

We should try that some day But I guess that the one who clicked 0.001s earlier would be the one resigning

I have very little knowledge about data transfer but I am very sure that two resignations at the same time are technically not possible because the incoming data/information is always one after another. Same with outgoing data from one router if two players are on the same local network for example.

I have very little knowledge about data transfer but I am very sure that two resignations at the same time are technically not possible because the incoming data/information is always one after another. Same with outgoing data from one router if two players are on the same local network for example.

Pressing it at the same time is practically impossible as numbers go on forever in decimal places but if two people did actually press it at the same time I think they both go up 100 rating points.
No I'm just kidding, I think it's impossible but if it does happen there has to be one piece of information going first as @Resurr3ction said :)

Pressing it at the same time is practically impossible as numbers go on forever in decimal places but if two people did actually press it at the same time I think they both go up 100 rating points. No I'm just kidding, I think it's impossible but if it does happen there has to be one piece of information going first as @Resurr3ction said :)

One of the resignations would always be processed before the other so that most likely one that comes second would be discarded (as the game has already finished). But it can happen easily that the second resignation will be sent before the information about the first is received byt player's application. After all, it already happened to me with a move that it was ignored because either the opponent has resigned or my time ran out before it was processed.

One of the resignations would always be processed before the other so that most likely one that comes second would be discarded (as the game has already finished). But it can happen easily that the second resignation will be sent before the information about the first is received byt player's application. After all, it already happened to me with a move that it was ignored because either the opponent has resigned or my time ran out before it was processed.
<Comment deleted by user>

@Toscani said in #7:

I would assume the server compares the client side timestamps (UTC) to determine which player asked it first. The only way to prove it, would be to find it in the code.

That would be so funny (to exploit). I'd be more than surprised, if it's not the servers time, that is used to make a decision.

@Toscani said in #7: > I would assume the server compares the client side timestamps (UTC) to determine which player asked it first. The only way to prove it, would be to find it in the code. That would be so funny (to exploit). I'd be more than surprised, if it's not the servers time, that is used to make a decision.
<Comment deleted by user>

But, to keep a useless discussion going in a pointless direction, .... What if it happened in an OTB and the TD arrives and the two players argue about who resigned first?

Maybe motivated by something like the plot for the movie 'The Producers' who wanted their play 'Springtime for Hitler' to fail.

But, to keep a useless discussion going in a pointless direction, .... What if it happened in an OTB and the TD arrives and the two players argue about who resigned first? Maybe motivated by something like the plot for the movie 'The Producers' who wanted their play 'Springtime for Hitler' to fail.

This topic has been archived and can no longer be replied to.