Damn subtle bug about chess.js HOT 3 CLOSED

The code

          castling[turn] =
            castling[turn] ^= ROOKS[turn][i].flag;

is not the bug itself, but it is capable to do magic of "restoring" castle status. There was bishop at a8 moving to g2 that was erroneously detected as rook. The rook is also can restore castle status if rook moves twice from a8. The first move from a8 will reset castle flag, then if rook returns back to a8 and leave it again - we should check it, I am not sure but it can be also very surprising

I also wonder why castling[turn] is assigned twice, = and ^= are both assignments

from chess.js.

Good find. Looking back on some of this old castling code is a little embarrassing. I've got a fix that I'll post shortly along with a regression test or two. Thanks for the report.

from chess.js.

Great, this bug was very tough to find

from chess.js.