The other day I played a game, and lost, due to a group of my stones being incorrectly marked dead during auto removal phase and there was nothing that I could do. I requested a moderator but nothing happened.
I’m playing as White.
1 Like
Don’t agree automatically to the score. Check if the dead stones are indeed dead. Score can’t be changed (you agreed on it), but mod can annul the game.
2 Likes
You can click on stones during the scoring phase to toggle their status between alive and dead. Unless your opponent is a bot, which doesn’t appear to be the case here. Are you unaware of this key part of players agreeing to the status of groups during the scoring phase? This isn’t a rhetorical or sarcastic question, I want to understand if the OGS system of auto-making dead stones, usually correctly but sometimes not, means beginners who learn go here are not aware of this part of the rules of go.
2 Likes
I’m used to playing on Badukpop, SmartGo, and GoQuest, so when I clicked “Automatic,” I thought it would be like normal. But that’s the thing, when I checked, I’m pretty sure they were fine. I said yes that I would like to “automatically remove stones,” and that was it, the game was over, and I was confused about how I’d lost. I then checked with “estimate score,” and it confirmed that I should have won.
I’m aware that in an irl game, the stones are removed or are used to fill in the opponent’s spaces (depending on the rule set). I just thought that OGS would auto count similar to other Go apps.
1 Like
Is the automatic scoring bugged or something?
The game has the appearance of score cheating. I will file a report for you. If the cheating is verified the game will be annulled and the cheater warned.
1 Like
That’s a thing?? How can I prevent that or look out for it in the future? 
Is the report different from calling for a moderator to review?
If someone marks your live stones dead, or makes other incorrect markings on the board, click the autoscore button again and file a score-cheating report. That’s the fastest way to deal with it.
Calling for a moderator is the same, but I suspect you did not pick the right category, because I do not see your report in the queue, and the game has not been annulled.
Ok, thanks for the heads up
So, when both players pass, OGS will automatically display its understanding of the life and death of groups and resulting score.
Players may manually change the status of stones by clicking on them if they think the AI made a mistake. That’s rare, but it happens (note that this happens on badukpop as well, you just can’t correct it). They can also reject scoring altogether and resume the game.
If players agree with the scoring, they click accept. The game definitely ends once both players accepted.
In your case, either the AI was wrong or your opponent manually changed it, and you accepted it.
1 Like
I checked after the game and they were live, I was proud of myself for being able to make 2 eyes. So I was confused as to why it didn’t count once the counting was over, and was worried that I made the eyes wrong.
Idk if it was the bot or the player though. I counted, clicked auto and confirmed. I didn’t think I had to re-recheck
I didn’t know score cheating was a thing, I thought it was a bug so I’m pretty sure I clicked “other”.
I see your report in the history. It was indeed filed in the wrong category, and it expired.
Does that mean its to late to refile?
I refiled the report as score cheating, and I have already voted on it. It is a very clear case in my opinion. No fault by you. You were unlucky because the marking was changed simultaneously with your acceptance (i.e., a fraction of a second before you accepted), so you had no time really to see the change, and then the other player accepted, and the game ended.
4 Likes
Thank you
All of these “opponent changed status of stones just after I accepted” score cheating cases could be avoided by making the “accept score” command from client to server not simply be an instruction to the server to accept whatever server state of scoring exists when it arrives, but include a hash of the position and marked status from the accepting client (and require that it has not changed in the last few seconds) and if that doesn’t match the server state reject it as invalid with a message like “the opponent changed the marked dead stones around the same time as you accepted the score, please carefully check all stones are marked dead or alive correctly before accepting again”.
@anoek can we please have this. It will make players happier and reduce moderator workload fixing up the cases.
10 Likes
It already works that way (technically the exact stones that were removed not a hash)
It used to do that exact thing, I’m not sure when it got changed. I’ll restore that functionality though, that’s pretty important.
14 Likes