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.

Sign up for GitHub

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

Jump to bottom

Move decision - castling #131

Closed
lrozenblyum opened this issue Jul 14, 2014 · 3 comments
Closed

Move decision - castling #131

lrozenblyum opened this issue Jul 14, 2014 · 3 comments
Labels
evaluation
Milestone
0.1

Comments

@lrozenblyum
Copy link
Owner

Child of #130

Prefer saving castling possibility
@lrozenblyum
Copy link
Owner Author

Particularly done (however after actual castling we mark king/rook moves as not good which is not nice)

@lrozenblyum
Copy link
Owner Author

After castling all moves are equal now.
After either king or both rooks next moves are equal now.

Need to improve processing when rook was captured. It might prevent king movement in wrong way

@lrozenblyum lrozenblyum mentioned this issue Jul 3, 2019
Closed
40 tasks
@lrozenblyum lrozenblyum added this to the 0.1 milestone Jul 3, 2019
@lrozenblyum
Copy link
Owner Author

Basic job has been done long time ago. Closing.
New job is done in #293

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
evaluation
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
1 participant
@lrozenblyum