-
-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect castling/gating check in FEN validation #777
Comments
Please specify more detailed steps to reproduce the issue such as variant config if any, CLI/GUI commands/input, expected vs actual output. |
It happened on pychess when he created a custom setup S-chess game with above FEN.
|
Thanks for the context. Technically looks correct to me though, since in a non-960 game there can't be an unmoved king on a different file than the e-file. If this also happens in 960, then I guess it would be a bug. |
I think I checked in 960 in the new game dialog. Or not.I have to double check this .... |
I’ve noticed an error when setting up custom seriawan chess positions with castling rules disabled causing the gating rules in this variant to fail to initialize when generating otherwise plausible chess starting positions wither symmetrical or non symmetrical. May need to update the coding to recognize custom setups without castling rules to allow gating the pieces when placing them in such scenarios like this.
edit: here’s the original post explaining the exact scenario with the FEN code showing how it can be reproduced.
rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/QBBNNRKR[HEhe] w BCDFGbcdfg - 0 1 is a custom Seriwan chess setup that should work correctly if castling rules are disabled. Apparently the gating rules in Seirawan chess doesn’t recognize this possiblility. This may need an update to the coding to account for this scenario.
The text was updated successfully, but these errors were encountered: