lichess.org
Donate

3-fold repetition bug

Looks like lichess only looks at the position for a threefold repetition draw, instead of taking into account all the requirements for a threefold repetition.
My game was just declared drawn after triangulating my opponent, creating the same position for the third time. But this time with my opponent to move.
Might be interesting to also look at castling rights and en-passant rights.
Without looking at your game: same position in last move, last move -2, last move -4

After looking:



PS: triangulation means making a triangle - not repeating move a then repeating move b
www.fide.com/FIDE/handbook/LawsOfChess.pdf

9.2 The game is drawn upon a correct claim by the player having the move, when the same position, for at least the third time (not necessarily by a repetition of moves):
a. is about to appear, if he first writes his move on his scoresheet and declares to the arbiter his intention to make this move, or
b. has just appeared, and the player claiming the draw has the move.
Positions as in (a) and (b) are considered the same, if the same player has the move, pieces of the same kind and colour occupy the same squares, and the possible moves of all the pieces of both players are the same.
Positions are not the same if a pawn that could have been captured en passant can no longer be captured in this manner. When a king or a rook is forced to move, it will lose its castling rights, if any, only after it is moved.

9.3 The game is drawn, upon a correct claim by the player having the move, if:
a. he writes his move on his scoresheet and declares to the arbiter his intention to make this move, which shall result in the last 50 moves having been made by each player without the movement of any pawn and without any capture, or
b. the last 50 consecutive moves have been made by each player without the movement of any pawn and without any capture.
You are all right, I hallucinated.
Trying so hard to turn a drawn position in a losing one for zero upside. Well played.

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