I was playing a long game, and in a critical position where I was totally winning, it appeared my opponent had abandoned the game and let the clock run. When his time ran out, I opened a new tab to analyze the position, only to discover that I was the one who had lost on time.
It was a long 'classical' game (lasting at least one hour) where I had a winning position. For some reason, I lost on time even though the page showed my opponent's clock running. Is there any way for me to recover the lost rating points? My opponent's rating was significantly lower, so the rating loss was substantial, especially since this was a long time control, which I don't play often.
I'm not sure if this is the proper channel. I have seen this happen to others, and the advice was to refresh the page, but the page seemed fine. This bug happened right after my opponent miscalculated and lost a piece, which led me to believe they had simply abandoned the game.
Anyway, sorry for the rant.
I was playing a long game, and in a critical position where I was totally winning, it appeared my opponent had abandoned the game and let the clock run. When his time ran out, I opened a new tab to analyze the position, only to discover that I was the one who had lost on time.
It was a long 'classical' game (lasting at least one hour) where I had a winning position. For some reason, I lost on time even though the page showed my opponent's clock running. Is there any way for me to recover the lost rating points? My opponent's rating was significantly lower, so the rating loss was substantial, especially since this was a long time control, which I don't play often.
I'm not sure if this is the proper channel. I have seen this happen to others, and the advice was to refresh the page, but the page seemed fine. This bug happened right after my opponent miscalculated and lost a piece, which led me to believe they had simply abandoned the game.
Anyway, sorry for the rant.
The page seems fine until you refresh, then you see that your opponent already made their move.
I've not had the problem since I made refreshing a habit when my opponent takes longer.
You can't get points back:
https://lichess.org/faq#disconnection-loss
The page seems fine until you refresh, then you see that your opponent already made their move.
I've not had the problem since I made refreshing a habit when my opponent takes longer.
You can't get points back:
https://lichess.org/faq#disconnection-loss
Why do players never think to refresh, I wonder? We get 2 or 3 such posts a day, for crying out loud!
Why do players never think to refresh, I wonder? We get 2 or 3 such posts a day, for crying out loud!
@IamNOTamod said in #3:
Why do players never think to refresh, I wonder? We get 2 or 3 such posts a day, for crying out loud!
To be fair, while this approach is solving the problem (and it's a rather obvious fix when you see the "lichess is restarting" message), it still shouldn't be necessary and should get fixed.
Telling people to refresh really shouldn't be the "solution" for this.
@IamNOTamod said in #3:
> Why do players never think to refresh, I wonder? We get 2 or 3 such posts a day, for crying out loud!
To be fair, while this approach is solving the problem (and it's a rather obvious fix when you see the "lichess is restarting" message), it still shouldn't be necessary and should get fixed.
Telling people to refresh really shouldn't be the "solution" for this.
#4
"Telling people to refresh really shouldn't be the "solution" for this."
- What else? Making board and clock server side only would cause unwanted delays.
Maybe there should be a warning: if in doubt, CTRL F5.
#4
"Telling people to refresh really shouldn't be the "solution" for this."
* What else? Making board and clock server side only would cause unwanted delays.
Maybe there should be a warning: if in doubt, CTRL F5.
@tpr said in #5:
#4
"Telling people to refresh really shouldn't be the "solution" for this."
- What else? Making board and clock server side only would cause unwanted delays.
Maybe there should be a warning: if in doubt, CTRL F5.
Fixing the problem on the server would be the right thing to do. I totally understand that this might as it might not be easily reproducible at scale.
Making board and clock server side only would cause unwanted delays.
Not sure what you mean. Server already is the authority for this - as it should. Obviously every client would let their clock run, as it is done now.
But there has to be a more resilient way to show a broken connection, and forcing a reconnection in case something is broken. As of now, the current solution just isn't reliable. It often works, but sometimes people get no visual clue that something is wrong, whatsoever. And the instances skyrocket when there are server restarts, as you can easily see when new threads come up in the forum.
This does not seem to be unfixable by design. Some naïve solution would be that the client needs to get some fresh data from the server every second, and if it doesn't, it shows a broken connection and tries to reconnect.
We already do have some detector for broken connection in the client - it is just not working all the time.
@tpr said in #5:
> #4
> "Telling people to refresh really shouldn't be the "solution" for this."
> * What else? Making board and clock server side only would cause unwanted delays.
> Maybe there should be a warning: if in doubt, CTRL F5.
Fixing the problem on the server would be the right thing to do. I totally understand that this might as it might not be easily reproducible at scale.
> Making board and clock server side only would cause unwanted delays.
Not sure what you mean. Server already is the authority for this - as it should. Obviously every client would let their clock run, as it is done now.
But there has to be a more resilient way to show a broken connection, and forcing a reconnection in case something is broken. As of now, the current solution just isn't reliable. It often works, but sometimes people get no visual clue that something is wrong, whatsoever. And the instances skyrocket when there are server restarts, as you can easily see when new threads come up in the forum.
This does not seem to be unfixable by design. Some naïve solution would be that the client needs to get some fresh data from the server every second, and if it doesn't, it shows a broken connection and tries to reconnect.
We already do have some detector for broken connection in the client - it is just not working all the time.
#6
"Not sure what you mean. "
- The principled way would be to only have the board and clock at the server side, and locally on your computer only display moves and start the clock when a move has been acknowledged by the server.
However, then you would move a piece and the move would only show and your clock would only stop after the server has acknowledged. So there would be a delay between your move and it showing and your clock stopping to run.
"resilient way to show a broken connection"
The problem is somewhere between your computer and the server. Neither lichess nor you have control over it.
#6
"Not sure what you mean. "
* The principled way would be to only have the board and clock at the server side, and locally on your computer only display moves and start the clock when a move has been acknowledged by the server.
However, then you would move a piece and the move would only show and your clock would only stop after the server has acknowledged. So there would be a delay between your move and it showing and your clock stopping to run.
"resilient way to show a broken connection"
The problem is somewhere between your computer and the server. Neither lichess nor you have control over it.
Note that your "full server-side clock" wouldn't address this issue, or not completely.
I have first-hand experience with this issue. I played my move, it got to the server, the server restarted, my opponent made a move, which did not show up for me. My client was happily saying "reconected", my opponent's clock kept running - but obviously the server got my move, and even the response by my opponent.
@tpr said in #7:
Neither lichess nor you have control over it.
While often it is indeed somewhere in the middle, this is clearly a case that lichess messes up. But apart from the reason for a disconnect, lichess could still work better in all cases of disconnect. The client not showing the disconnection reliably is a solvable problem - no matter if it's about a server restart or some lost packets along the way. And fingerpointing at some other possible cause does not actually solve the problem.
Note that your "full server-side clock" wouldn't address this issue, or not completely.
I have first-hand experience with this issue. I played my move, it got to the server, the server restarted, my opponent made a move, which did not show up for me. My client was happily saying "reconected", my opponent's clock kept running - but obviously the server got my move, and even the response by my opponent.
@tpr said in #7:
>Neither lichess nor you have control over it.
While often it is indeed somewhere in the middle, this is clearly a case that lichess messes up. But apart from the reason for a disconnect, lichess could still work better in all cases of disconnect. The client not showing the disconnection reliably is a solvable problem - no matter if it's about a server restart or some lost packets along the way. And fingerpointing at some other possible cause does not actually solve the problem.
@IamNOTamod said in #3:
Why do players never think to refresh, I wonder? We get 2 or 3 such posts a day, for crying out loud!
I played over 700 games and was the first time it happened. Given the game situation, he blundered a piece one move before, I assumed he just leave the game, as unfortunately often happens. Now I know that's a thing.
@IamNOTamod said in #3:
> Why do players never think to refresh, I wonder? We get 2 or 3 such posts a day, for crying out loud!
I played over 700 games and was the first time it happened. Given the game situation, he blundered a piece one move before, I assumed he just leave the game, as unfortunately often happens. Now I know that's a thing.
The same thing happened to me once. No idea why.
The same thing happened to me once. No idea why.
