#133510: "The opponent intentionally did not counted a dead stone in a game where defeat was confirmed."
What is this report about?
What happened ? Please select from below
What happened ? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are taken care of in PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if any.
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
-
• Please explains what you wanted to do, what you do and what happened
When the game is over and the opponent counts a dead stone, you can see that the opponent didn't choose his dead stone at all and pressed the finish of selection button. This is a clear cheating attempt to unfairly change the outcome in a game where defeat has been decided. Please check it and take proper action on this.
• What is your browser?
Google Chrome v127
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
• What is your browser?
Google Chrome v127
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
• What is your browser?
Google Chrome v127
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
• What is your browser?
Google Chrome v127
-
• Which part of the rules was not respected by the BGA adaptation
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
-
• Is the rules violation visible on game replay? If yes, at which move number?
When the game is over and the opponent counts a dead stone, you can see that the opponent didn't choose his dead stone at all and pressed the finish of selection button. This is a clear cheating attempt to unfairly change the outcome in a game where defeat has been decided. Please check it and take proper action on this.
• What is your browser?
Google Chrome v127
-
• Which was the game action you wanted to do?
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
-
• What do you try to do to trigger this game action?
When the game is over and the opponent counts a dead stone, you can see that the opponent didn't choose his dead stone at all and pressed the finish of selection button. This is a clear cheating attempt to unfairly change the outcome in a game where defeat has been decided. Please check it and take proper action on this.
-
• What happened when you try to do this (error message, game status bar message, ...)?
• What is your browser?
Google Chrome v127
-
• At which step of the game did the problem occurs (what was the current game instruction)?
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
-
• What happened when you try to do a game action (error message, game status bar message, ...)?
When the game is over and the opponent counts a dead stone, you can see that the opponent didn't choose his dead stone at all and pressed the finish of selection button. This is a clear cheating attempt to unfairly change the outcome in a game where defeat has been decided. Please check it and take proper action on this.
• What is your browser?
Google Chrome v127
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
• What is your browser?
Google Chrome v127
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
• What is your browser?
Google Chrome v127
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Literally, The opponent intentionally did not designate a dead stone in a game where defeat was confirmed, which unfairly changed the outcome of the game.
• What is your browser?
Google Chrome v127
Report history
Because of my first experience with this, I managed to save my game in this way:
My opponent & I passed. My opponent refused to mark the dead stones. When the question came, "Do you want to have a stage of designate dead stones after next series of passes?", I naturally answered, "yes". I kept playing and killed enough groups to make the game clearly won, and when we both passed, there was no re-counting of dead stones.
Sure enough, my opponent had selected "no", as I suspected he would.
This clearly promotes cheating. The proposed solutions are as follows, going from best to worst:
1) An algorithm that automatically designates dead stones.
2) NO QUESTION about having another stage for designating stones. Since there was already one stage, but the players COULDN'T AGREE, that means that there AUTOMATICALLY needs to be another round of dead stone designation. This should just happen every time.
3) If the question remains like it does now, it should be that if EITHER or BOTH of the players answers "yes", then there should be a stone counting stage.
Add something to this report
- 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 a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
