#85323: "My opponent's move ended early and kutakatia was declared, which didn't make sense"
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 given PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if applicable.
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
-
• Please explain what you wanted to do, what you did and what happened
Move number 23 (North)
• Which browser are you using?
Mozilla v5
-
• 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 Imgur.com to upload it and copy/paste the link here.
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
-
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Move number 23 (North)
• Which browser are you using?
Mozilla v5
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
• Which browser are you using?
Mozilla v5
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
• Which browser are you using?
Mozilla v5
-
• Which part of the rules was not followed by the BGA adaptation?
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
-
• Is the rules violation visible on game replay? If yes, at which move number?
Move number 23 (North)
• Which browser are you using?
Mozilla v5
-
• What was the game action you wanted to do?
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
-
• What did you try to do to trigger this game action?
Move number 23 (North)
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Mozilla v5
-
• At which step of the game did the problem occur? What was the current game instruction?
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
-
• What happened when you tried to do this game action (error message, game status bar message, ...)?
Move number 23 (North)
• Which browser are you using?
Mozilla v5
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
• Which browser are you using?
Mozilla v5
-
• 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 Imgur.com to upload it and copy/paste the link here.
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
-
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Move number 23 (North)
• Which browser are you using?
Mozilla v5
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
The north player was executing a kutakata move and suddenly his pieces stopped moving around the board and a kutakatia was declared. This makes no sense because he shoulnd't have stopped, and he has more than one capture move available (wrong conditions for kutakatia)
• Which browser are you using?
Mozilla v5
Report history
But up front: Kutakatia is about 1 pit being blocked because it is the only harvest, not from how many pits one could reach it (see Nino's book, definition of Kutakatia).
You did a kutakata in move 23, leaving pit a3 as your only possible harvest for next round. It does not matter, if it is reachable from different pits (as it was from A3 and B6), only that there is a single pit to harvest - thus it was blocked for your opponent when doing a kutakata (marked black in game).
With his move a2, which was a kutakata, he would have emptied a3 after going around the board, which is not allowed, thus the move has to stop.
So everything is fine here. In case you have Nino's book (English version), you'll find an example explaining exactly that situation on page 85/86.
Add to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? 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.
