- Blind mode tutorial
lichess.org
Donate

PLEASE Stop aborting games without a fair timer.

#1

I played literally thousand of games, this time it's a classical one. Long game, my opponent takes FOREVER so I decide to change device since my bed and laptop is beside me and I close the tab for 10 SECONDS.

10 SECONDS AND MY GAME IS LOST.

It's very Annoying, like why the timer isn't fair? Even a little bit? It's not the first time it happens, is 1 minute too much to ask? Of course my opponent had no grace but, whatever it is lichess's fault, I had so much time left still.

I'm raging because I never felt like this system aborted games too slowly, NEVER, if I have to wait a little bit in a classical game because my opponent disconnected SO BE IT.
Why do you need an immediate abortion for? This is not a bullet game. I'm so defeated and mad at this pointless game, it's crazy, an hour wasted because I dared to close my tab for 5 seconds. And there is nothing I can do, beside complaining to ghosts here. I'm so tired.

I played literally thousand of games, this time it's a classical one. Long game, my opponent takes FOREVER so I decide to change device since my bed and laptop is beside me and I close the tab for 10 SECONDS. 10 SECONDS AND MY GAME IS LOST. It's very Annoying, like why the timer isn't fair? Even a little bit? It's not the first time it happens, is 1 minute too much to ask? Of course my opponent had no grace but, whatever it is lichess's fault, I had so much time left still. I'm raging because I never felt like this system aborted games too slowly, NEVER, if I have to wait a little bit in a classical game because my opponent disconnected SO BE IT. Why do you need an immediate abortion for? This is not a bullet game. I'm so defeated and mad at this pointless game, it's crazy, an hour wasted because I dared to close my tab for 5 seconds. And there is nothing I can do, beside complaining to ghosts here. I'm so tired.
#2

Mind sharing the game? It'll clear up some things. E.g. if you're position is lost the countdown will have less time, usually 10 to 30 secs. If the position is equal it takes around 300(?) secs.

Mind sharing the game? It'll clear up some things. E.g. if you're position is lost the countdown will have less time, usually 10 to 30 secs. If the position is equal it takes around 300(?) secs.
#3

@IamNOTamod said in #2:

E.g. if you're position is lost the countdown will have less time, usually 10 to 30 secs.

I highly doubt that is the case. That would require engine analysis on every single game, which would unnecessarily use an enormous amount of resources. It also would be a very bad idea even if it were reasonable to implement, because engine evaluation does not tell you how likely a human is to win or lose a position.

However, I'm pretty sure Lichess does do shorter timeouts if you abort/leave games often. So if you have a poor connection or a habit of aborting games, that could explain the short timeout. (It's also possible that you misjudged how much time had passed.)

If the position is equal it takes around 300(?) secs.

I've never seen a timeout even close to that long. Granted, I don't play classical on Lichess.

@IamNOTamod said in #2: > E.g. if you're position is lost the countdown will have less time, usually 10 to 30 secs. I highly doubt that is the case. That would require engine analysis on every single game, which would unnecessarily use an enormous amount of resources. It also would be a very bad idea even if it were reasonable to implement, because engine evaluation does not tell you how likely a human is to win or lose a position. However, I'm pretty sure Lichess does do shorter timeouts if you abort/leave games often. So if you have a poor connection or a habit of aborting games, that could explain the short timeout. (It's also possible that you misjudged how much time had passed.) > If the position is equal it takes around 300(?) secs. I've never seen a timeout even close to that long. Granted, I don't play classical on Lichess.
#4

@AsDaGo said in #3:

E.g. if you're position is lost the countdown will have less time, usually 10 to 30 secs.

I highly doubt that is the case.

Hmmn...maybe it just appears that way to me.

If the position is equal it takes around 300(?) secs.

I've never seen a timeout even close to that long. Granted, I don't play classical on Lichess.

This is for classical ONLY, for rapid I'm pretty sure it's 180 secs.

@AsDaGo said in #3: > > E.g. if you're position is lost the countdown will have less time, usually 10 to 30 secs. > > I highly doubt that is the case. Hmmn...maybe it just appears that way to me. > > If the position is equal it takes around 300(?) secs. > > I've never seen a timeout even close to that long. Granted, I don't play classical on Lichess. This is for classical ONLY, for rapid I'm pretty sure it's 180 secs.
#5

Also, I can't understand why you would close the tab before opening the game on a new device. If you didn't close the tab, you would be gone for exactly 0 seconds and wouldn't have to worry about any timeout.

Also, I can't understand why you would close the tab before opening the game on a new device. If you didn't close the tab, you would be gone for exactly 0 seconds and wouldn't have to worry about any timeout.
#6

@IamNOTamod said in #4:

This is for classical ONLY, for rapid I'm pretty sure it's 180 secs.

Sadly, unless something changed recently, it's only 120 seconds (80s for rapid, 40s for blitz). And half of that when "losing" (which is determined by material, IIRC). Unfortunately some values on Lichess were set with blitz in mind and are not very appropriate for a classical game. (TBH, 40s seems too long for blitz or bullet so the only value which is kind of OK is probably the rapid one.)

@IamNOTamod said in #4: > This is for classical ONLY, for rapid I'm pretty sure it's 180 secs. Sadly, unless something changed recently, it's only 120 seconds (80s for rapid, 40s for blitz). And half of that when "losing" (which is determined by material, IIRC). Unfortunately some values on Lichess were set with blitz in mind and are not very appropriate for a classical game. (TBH, 40s seems too long for blitz or bullet so the only value which is kind of OK is probably the rapid one.)
#7

this is strange i just tested it with myself and its very inconsistent like checking the latest message i got used to be 295 secs (180+180) and then in the same game just a minute later now when i do the exact same thing that used to give 295 secs it gives me 10?? this question should be on the faq!

this is strange i just tested it with myself and its very inconsistent like checking the latest message i got used to be 295 secs (180+180) and then in the same game just a minute later now when i do the exact same thing that used to give 295 secs it gives me 10?? this question should be on the faq!
#8

I'm pretty sure that this happens when you repeatedly leave the game. Just don't leave the game it's not that complicated.

I'm pretty sure that this happens when you repeatedly leave the game. Just don't leave the game it's not that complicated.
#9

@HommeSaoul said in #1:

I played literally thousand of games, this time it's a classical one. Long game, my opponent takes FOREVER so I decide to change device since my bed and laptop is beside me and I close the tab for 10 SECONDS.

Closing the tab is a deliberate action, so the server assumes you quit the game on purpose. Why would you not just navigate to Lichess on the new device without doing anything to prematurely quit the game on the old one?

@HommeSaoul said in #1: > I played literally thousand of games, this time it's a classical one. Long game, my opponent takes FOREVER so I decide to change device since my bed and laptop is beside me and I close the tab for 10 SECONDS. Closing the tab is a deliberate action, so the server assumes you quit the game on purpose. Why would you not just navigate to Lichess on the new device without doing anything to prematurely quit the game on the old one?
#10

@lq2 said in #7:

this is strange i just tested it with myself and its very inconsistent like checking the latest message i got used to be 295 secs (180+180) and then in the same game just a minute later now when i do the exact same thing that used to give 295 secs it gives me 10?? this question should be on the faq!

If I remember correctly, the amount of "absence time" is per game, not per disconnect. Or at least something in that spirit.

@lq2 said in #7: > this is strange i just tested it with myself and its very inconsistent like checking the latest message i got used to be 295 secs (180+180) and then in the same game just a minute later now when i do the exact same thing that used to give 295 secs it gives me 10?? this question should be on the faq! If I remember correctly, the amount of "absence time" is per game, not per disconnect. Or at least something in that spirit.