- Blind mode tutorial
lichess.org
Donate

"warning, letting clock run out instead of resigning will result in a temporary ban"

#1

This message was just sent to my opponent after a recent game. They proposed a takeback after what I thought was an obvious blunder. I did my usual ask "what move did you mean to make" since I only takeback slips or opening brainfarts. I think there may have been a language barrier or they weren't checking chat, so the clock ran out.

So, simple feature change request, I think that if there's an active takeback request, players shouldn't receive a warning/ban. If a player thinks the opponent might allow a takeback, there's no reason to resign. I was on the other end of this where I meant to trade pieces and slipped, and my opponent waited for my time to almost expire before accepting the takeback, where I would have waited for it to expire.

At the risk of getting off-topic, I have an idea for amending the takeback system to help with this:

  • side A offers takeback
  • side B asks for a confirmation of what they intended to play. clock paused during this time.
  • side A locks in a move within ~10 seconds.
  • side B gets ~10 seconds to allow or deny the locked in move
  • play on

I can see this idea getting abused by people who never intended to allow the takeback, but I think it's better than the sometimes >2 minutes I've waited for takeback responses.

This message was just sent to my opponent after a recent game. They proposed a takeback after what I thought was an obvious blunder. I did my usual ask "what move did you mean to make" since I only takeback slips or opening brainfarts. I think there may have been a language barrier or they weren't checking chat, so the clock ran out. So, simple feature change request, I think that if there's an active takeback request, players shouldn't receive a warning/ban. If a player thinks the opponent might allow a takeback, there's no reason to resign. I was on the other end of this where I meant to trade pieces and slipped, and my opponent waited for my time to almost expire before accepting the takeback, where I would have waited for it to expire. At the risk of getting off-topic, I have an idea for amending the takeback system to help with this: - side A offers takeback - side B asks for a confirmation of what they intended to play. clock paused during this time. - side A locks in a move within ~10 seconds. - side B gets ~10 seconds to allow or deny the locked in move - play on I can see this idea getting abused by people who never intended to allow the takeback, but I think it's better than the sometimes >2 minutes I've waited for takeback responses.
#2

I can't understand why people take the warning so seriously: it's a warning. Not like they get banned immediately. Only if it happens repeatedly.

Regarding takebacks: I'm curious. Do a lot of you do this negotiating with their opponent? I never do.

But then I usually decline the takebacks anyways, because mouse I consider slips or "brain farts" as part of the game, especially with shorter time controls. Or I fail to notice the request

And if the opponent want's to wait.. well. it's their time to do with as they please. I wouldn't expect a feedback response after 2 minutes.

I can't understand why people take the warning so seriously: it's a warning. Not like they get banned immediately. Only if it happens repeatedly. Regarding takebacks: I'm curious. Do a lot of you do this negotiating with their opponent? I never do. But then I usually decline the takebacks anyways, because mouse I consider slips or "brain farts" as part of the game, especially with shorter time controls. Or I fail to notice the request And if the opponent want's to wait.. well. it's their time to do with as they please. I wouldn't expect a feedback response after 2 minutes.
#4

tbo I like takebacks just maybe give the guy who approved it 2 minutes extra (not bullet and ultrabullet.)

tbo I like takebacks just maybe give the guy who approved it 2 minutes extra (not bullet and ultrabullet.)

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