Skip to content
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

King's movement - castling - WinBoard support #84

Closed
lrozenblyum opened this issue Mar 15, 2014 · 1 comment
Closed

King's movement - castling - WinBoard support #84

lrozenblyum opened this issue Mar 15, 2014 · 1 comment
Labels
Milestone

Comments

@lrozenblyum
Copy link
Owner

  1. WinBoard engine must receive our castling correctly
  2. We must interpret WinBoard castling correctly

It's an important step in castling integration #76

@lrozenblyum
Copy link
Owner Author

Probably accidentally we FIT into winboard format.
Winboard supports castling exactly in the same way we send it!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Normal moves: e2e4
Pawn promotion: e7e8q
Castling: e1g1, e1c1, e8g8, e8c8
Bughouse/crazyhouse drop: P@h3
ICS Wild 0/1 castling: d1f1, d1b1, d8f8, d8b8
FischerRandom castling: O-O, O-O-O (oh, not zero)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I think we haven't selected SAN : (and probably don't need it)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Beginning in protocol version 2, you can use the feature command to select SAN (standard algebraic
notation) instead; for example, e4, Nf3, exd5, Bxf7+, Qxf7#, e8=Q, O-O, or P@h3. Note that the
last form, P@h3, is a extension to the PGN standard's definition of SAN, which does not support
bughouse or crazyhouse.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

lrozenblyum added a commit that referenced this issue Mar 30, 2014
lrozenblyum added a commit that referenced this issue Sep 26, 2014
No code has been changed to use new features. Need to go through CI to ensure all infrastructure is ready.
lrozenblyum added a commit that referenced this issue Sep 26, 2014
No code has been changed to use new features. Need to go through CI to ensure all infrastructure is ready.
@lrozenblyum lrozenblyum added this to the 0.1 milestone Feb 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant