All reports
classicgo_displayed reports
#161133: "Didn't agree about dead stones, resumed play, then game didn't count dead stones."
What is this report about?
What happened ? Please select from below
The interface blocked me to do some game action authorized by the rules
Detailed description
• Which was the game action you wanted to do?
Table #642822106
Have the game count the dead stones to give the proper score to both players.• What do you try to do to trigger this game action?
My opponent and I didn't agree about the marking of dead stones, so we resumed play. My opponent selected "No" to the question, "Do you want to have a stage of designate dead stones after next series of passes?" He was losing, and by selecting "no", he almost won the game, as the game didn't mark the dead stones, and didn't give my the resulting 36 points I should have received.
I only won because I was far enough ahead in points. However, Go is usually so close in score that every point makes a huge difference. This prevents people from playing by the rules.• What happened when you try to do this (error message, game status bar message, ...)?
No errors, the game simply ended without allowing use to mark the dead stones. The game didn't identify the dead stones correctly, and didn't even ask if we agreed with the counting result. As several stones were not marked as dead, I lost the stones and the territory they were in.
In my recent table, #642822106, my opponent selected "No" to the question, "Do you want to have a stage of designate dead stones after next series of passes?", which almost cost me the game. This violates the rules of the game.• What is your browser?
Firefox v133.0.3
Report history
ElessarDunadan • Bug has not been reproduced by delopers yet:
12. Mar 2025 14:47 • Table #642822106
imgur.com/a/olkcuJm
In bug ID #14642, this problem is marked as fixed, but it actually doesn't fix anything. Rather, it only allows for cheating to continue happening.
imgur.com/a/olkcuJm
In bug ID #14642, this problem is marked as fixed, but it actually doesn't fix anything. Rather, it only allows for cheating to continue happening.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.