All reports
kalah_displayed reports
#585: "Said NO to enemy capture. Enemy capture still worked."
notabug: This is not a bug
1
What is this report about?
What happened ? Please select from below
Rules: a rule of the game has not been respected
Detailed description
• Which part of the rules was not respected by the BGA adaptation
Before the game, the host selected NO for Enemy Capture. But Enemy capture still worked.• Is the rules violation visible on game replay? If yes, at which move number?
Move 14, 17, 18 and 19• What is your browser?
Google Chrome v33
Report history
5. Apr 2014 22:01 • stst • This is not a bug:
This case is not a bug, because it was not "Empty capture" but normal capture of stones from opponent's hole (basic rule). The "Empty Capture" variant permits to capture the last stone when landing in an empty hole on the player's own side even when the opposite hole of the opponent is empty.
5. Apr 2014 23:59 • stst • This is not a bug:
I didn't notice that you spoke about "Enemy capture", but such option is absent. And "Empty capture" option is present. See above about it.
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.
