Yeah happened to me multiple times, when I notified developers about it they said something's wrong with my Internet. Done.
Glitch - board resetting
Sort:
Hmm. Do you agree? Is that just it - my internet?
Jan 26, 2019
0
#5
It's a known but: the rewind to move 1 bug. Developers haven't been able to fix it yet.
I see. Thanks, Chuck. It's good to know it's not a problem on my end, I guess. Really annoying, though. Always seems to happen when time is critical. Wouldn't mind so much if it didn't cost others rating points too, when they think I've just sat and let the clock run out.
Jan 26, 2019
0
#7
Happened to me many times. I believe it always has something to do with capturing/moving a queen.
I heard it's sometimes possible to make another move, but it didn't work for me.
Indeed annoying, must be fixed.
Crazy_Eight, yes, I think I was attempting to capture with a queen. Glad it's not just me then, I guess. Hope they will try to fix it.
Jan 26, 2019
0
#9
a good example: https://www.youtube.com/watch?v=_4eSnxjTPoc&feature=youtu.be
Jannlee gets the bug in the 1:18.35 - 1:21.00 game , at 1:20.25 . He tried to capture a queen for the second time in the game, which caused this bug.
Feb 16, 2019
0
#10
New here, and scanning the forums in search of other answers and information. I can confirm, as of yesterday and today: Queen capture bug still exists. Yesterday I was able to overcome it after 3 page refreshes and the expense of 30 seconds. No such luck today. (This is 21 days old.)
Feb 22, 2019
0
#13
Here's a game where it looks like it happened to my opponent ...
https://www.chess.com/live/game/3482045932
I saw an update to the UI the other day, and thought the bug was fixed. But, after where the game ends, my op was constantly connecting and reconnecting. I can only assume that this is what it looks like when refreshing my own page to try and issue my next move when I get stuck.
Has anyone else noticed this? Just played a game and with only seconds left on the clock, when I tried to move the board reset itself. Tried refreshing the page and it seemed to be fixed - until I attempted the same move, then the same thing happened. Couldn't play and we lost on time. This has happened a few times now.