-
Notifications
You must be signed in to change notification settings - Fork 7
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
Ko error #6
Comments
More pure reproduction:
but if you uncomment the two moves, so that the capture also puts another stone in atari, the last move can't be taken back. |
Hi, thanks for the report I'm looking into it. What are the rules used ? and version of the crate ? |
I corrected the issue, 0.16.0 is now yanked. the others versions don't seems to hove this issue. It was an issue in detecting the Ko point I forget to add a condition from a rework I had done for 0.16.0. I added you reproduction into my tests ! |
Hi there,
thank you for your great library. I was just using it in my rust yew project.
I just stumbled upon a situation. Just in some shapes, I get this situation, where after taking 2 stones, the API thinks that it is a ko, even though it's not.
In the screenshot, the transparent stone is the about to be placed stone, that is returning an error.
Would be great if you could have a look at it.
Thank you for your great library!
ps: I have this frontend in: https://github.com/janos-r/yewban
The text was updated successfully, but these errors were encountered: