Closed colding10 closed 1 year ago
Describe the bug At position e2e4 b8c6 g1f3 g8f6 b1c3 d7d5 e4d5 f6d5 d2d4 d5c3 b2c3 e7e5 d4e5 d8d1 e1d1 c8g4 f1b5, the move a9d8 suggested by the engine is illegal. a9 is out of bounds.
e2e4 b8c6 g1f3 g8f6 b1c3 d7d5 e4d5 f6d5 d2d4 d5c3 b2c3 e7e5 d4e5 d8d1 e1d1 c8g4 f1b5
a9d8
a9
To Reproduce Steps to reproduce the behavior:
position startpos moves e2e4 b8c6 g1f3 g8f6 b1c3 d7d5 e4d5 f6d5 d2d4 d5c3 b2c3 e7e5 d4e5 d8d1 e1d1 c8g4 f1b5
go wtime 168235 btime 63208 movestogo 32
Expected behavior The rook moving is understandable. However, it should be a8d8.
a8d8
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.
This issue has been patched. The issue was related to the way C++ handles modulo with negative signs, and floor division.
Describe the bug At position
e2e4 b8c6 g1f3 g8f6 b1c3 d7d5 e4d5 f6d5 d2d4 d5c3 b2c3 e7e5 d4e5 d8d1 e1d1 c8g4 f1b5
, the movea9d8
suggested by the engine is illegal.a9
is out of bounds.To Reproduce Steps to reproduce the behavior:
position startpos moves e2e4 b8c6 g1f3 g8f6 b1c3 d7d5 e4d5 f6d5 d2d4 d5c3 b2c3 e7e5 d4e5 d8d1 e1d1 c8g4 f1b5
go wtime 168235 btime 63208 movestogo 32
Expected behavior The rook moving is understandable. However, it should be
a8d8
.Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.