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

Jump to bottom

[PATCH] Don't re-send CECP engines the last move after a setBoard(). #651

Closed
pychess opened this issue Feb 4, 2015 · 3 comments
Closed

[PATCH] Don't re-send CECP engines the last move after a setBoard(). #651

pychess opened this issue Feb 4, 2015 · 3 comments

Comments

@pychess
Copy link
Collaborator

pychess commented Feb 4, 2015

Original issue 651 reported by UncombedCoconut 2011-03-09

This is a 1-liner.
To reproduce the problem, use "enter game notation" to match pychess vs pychess after "1. e4". Pychess gets "usermove e4" twice and dies.
@pychess
Copy link
Collaborator Author

pychess commented Feb 4, 2015

@pychess
Copy link
Collaborator Author

pychess commented Feb 4, 2015

Original comment 1. posted by lobais 2011-03-09

Great catch! Wonder how long that bug has been around :O

  • changed status to: Fixed

@pychess
Copy link
Collaborator Author

pychess commented Feb 4, 2015

Original comment 2. posted by lobais 2011-03-09

issue #400 has been merged into this issue.

@pychess pychess closed this as completed Feb 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants