Brand new thing: my opponent's time always runs down to zero, then I lose.
For real, this happens.
For real, this happens.
0.0001. The entire precision of the clock is not displayed, not sure if there is a setting that you can change...
@BlockMyPremove said in #2:
> 0.0001. The entire precision of the clock is not displayed, not sure if there is a setting that you can change...
No
I meant this: my opponent's clock runs down to zero, and I lose on time. Then the opponent's time is displayed with more than a second
> 0.0001. The entire precision of the clock is not displayed, not sure if there is a setting that you can change...
No
I meant this: my opponent's clock runs down to zero, and I lose on time. Then the opponent's time is displayed with more than a second
I meant this: my opponent's clock runs down to zero, and I lose on time.
Lichess.org/lag
Your opponents may be getting lag compensation.
Your opponents may be getting lag compensation.
@Akarsh_2010 said in #5:
> Lichess.org/lag
> Your opponents may be getting lag compensation.
Then why do I lose when I have 5 seconds and it's not checkmate or forfeit?
My clock stays the same, my opponent's clock runs down to 0, then it resets to x-amount of time, and I lose.
AND IT'S NOT MY INTERNET
> Lichess.org/lag
> Your opponents may be getting lag compensation.
Then why do I lose when I have 5 seconds and it's not checkmate or forfeit?
My clock stays the same, my opponent's clock runs down to 0, then it resets to x-amount of time, and I lose.
AND IT'S NOT MY INTERNET
It's not just you and not just Ultra bullet. I play lot's of Classical so there's this day I was wondering why my opponent is taking 14 mins to just make their second move so I maybe thought it was my lichess with the problem when I reloaded the page I found out I'm the one who used 14 mins on move two and the guy already made a move long time ago
@KDMFan said in #6:
> Then why do I lose when I have 5 seconds and it's not checkmate or forfeit?
>
> My clock stays the same, my opponent's clock runs down to 0, then it resets to x-amount of time, and I lose.
>
> AND IT'S NOT MY INTERNET
This happened to me in rapid too. My opponent must have thought I was stalling since I was losing, when in reality I was waiting for 10 minutes. Turns out they already made a move ages ago and I lost on time after using 9 minutes on the last move.
It also happened to me in ultrabullet as well.
> Then why do I lose when I have 5 seconds and it's not checkmate or forfeit?
>
> My clock stays the same, my opponent's clock runs down to 0, then it resets to x-amount of time, and I lose.
>
> AND IT'S NOT MY INTERNET
This happened to me in rapid too. My opponent must have thought I was stalling since I was losing, when in reality I was waiting for 10 minutes. Turns out they already made a move ages ago and I lost on time after using 9 minutes on the last move.
It also happened to me in ultrabullet as well.
happened too in hyper
@KDMFan said in #6:
> Then why do I lose when I have 5 seconds and it's not checkmate or forfeit?
>
> My clock stays the same, my opponent's clock runs down to 0, then it resets to x-amount of time, and I lose.
>
> AND IT'S NOT MY INTERNET
Again, its not your fault, it's the opponents internet, which is terrible by how you describe it. To make it fair, lichess credits back the time it takes for the move to be sent to the server and you. This is highly misused by people in time controls like hyper and ultra, which is known as "lag cheating"
@Scandinavian_Axe said in #7:
> It's not just you and not just Ultra bullet. I play lot's of Classical so there's this day I was wondering why my opponent is taking 14 mins to just make their second move so I maybe thought it was my lichess with the problem when I reloaded the page I found out I'm the one who used 14 mins on move two and the guy already made a move long time ago
In this case it is your internet. You disconnected and did not reconnect by refreshing, which lead to you thinking it is your opponents turn when in reality it's yours. Many, many, many, many fourms made about this, and all of them get the same response.
@cherrytea78 said in #8:
> This happened to me in rapid too. My opponent must have thought I was stalling since I was losing, when in reality I was waiting for 10 minutes. Turns out they already made a move ages ago and I lost on time after using 9 minutes on the last move.
>
> It also happened to me in ultrabullet as well.
Look at my two above responses.
@youbeatmelol said in #9:
> happened too in hyper
Above.
> Then why do I lose when I have 5 seconds and it's not checkmate or forfeit?
>
> My clock stays the same, my opponent's clock runs down to 0, then it resets to x-amount of time, and I lose.
>
> AND IT'S NOT MY INTERNET
Again, its not your fault, it's the opponents internet, which is terrible by how you describe it. To make it fair, lichess credits back the time it takes for the move to be sent to the server and you. This is highly misused by people in time controls like hyper and ultra, which is known as "lag cheating"
@Scandinavian_Axe said in #7:
> It's not just you and not just Ultra bullet. I play lot's of Classical so there's this day I was wondering why my opponent is taking 14 mins to just make their second move so I maybe thought it was my lichess with the problem when I reloaded the page I found out I'm the one who used 14 mins on move two and the guy already made a move long time ago
In this case it is your internet. You disconnected and did not reconnect by refreshing, which lead to you thinking it is your opponents turn when in reality it's yours. Many, many, many, many fourms made about this, and all of them get the same response.
@cherrytea78 said in #8:
> This happened to me in rapid too. My opponent must have thought I was stalling since I was losing, when in reality I was waiting for 10 minutes. Turns out they already made a move ages ago and I lost on time after using 9 minutes on the last move.
>
> It also happened to me in ultrabullet as well.
Look at my two above responses.
@youbeatmelol said in #9:
> happened too in hyper
Above.
This topic has been archived and can no longer be replied to.