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

Rare blunders #1

Open
sscg13 opened this issue Jan 3, 2024 · 0 comments
Open

Rare blunders #1

sscg13 opened this issue Jan 3, 2024 · 0 comments

Comments

@sscg13
Copy link
Owner

sscg13 commented Jan 3, 2024

Very infrequently the engine will blunder (for instance, obviously hang material) and recognize this on the very next move.
A possible cause could be incorrectly storing the best move and reporting a different unintended move somehow.
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
1 participant
@sscg13