All reports
kalah_displayed reports
#584: "The game didn't end when opponent's house has no seeds."
fixed: Bug has been fixed
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
This game didn't end when opponent's house has no seeds.
It had to end immediately, but game was continue.• Is the rules violation visible on game replay? If yes, at which move number?
Move n°52 to n°53• What is your browser?
Mozilla v5
Report history
5. Apr 2014 22:18 • stst • This is not a bug:
This is not a bug. This adaptation has the following variant of end of the game: The game ends when a player, at his turn, is unable to move and the remaining stones are captured by his opponent. This rule is observed at this playing.
6. Apr 2014 5:04 • akuru7 • This is not a bug:
I'm sorry, I didn't understand well yet.
Another adaptation of Kalah is end at same situation.
Please tell me exact all conditions of game end at this adaptation.
Another adaptation of Kalah is end at same situation.
Please tell me exact all conditions of game end at this adaptation.
6. Apr 2014 12:15 • stst • Bug has been confirmed by developers:
Sorry, Sorry!
This case is a bug.
The conditions of end of game at this adaption:
1) A player, at his move, is unable to move. The game ends and the remaining stones are captured by his opponent.
2) A player has more than half of all stones in his kalah.
At your case:
Move 53:
Masschy plays 1 stones from a hole n°6
Masschy places 1 stones into his/her Kalah
Masschy gets additional move, because last stone falls in Kalah. Masschy is unable to move at the additional move (no stones in his holes). Game has to be ended (condition 1 of end of game), but it was continued.
This is a BUG. I will correct this bug soon.
This case is a bug.
The conditions of end of game at this adaption:
1) A player, at his move, is unable to move. The game ends and the remaining stones are captured by his opponent.
2) A player has more than half of all stones in his kalah.
At your case:
Move 53:
Masschy plays 1 stones from a hole n°6
Masschy places 1 stones into his/her Kalah
Masschy gets additional move, because last stone falls in Kalah. Masschy is unable to move at the additional move (no stones in his holes). Game has to be ended (condition 1 of end of game), but it was continued.
This is a BUG. I will correct this bug soon.
7. Apr 2014 6:26 • akuru7 • Bug has been confirmed by developers:
I think almost all other adaption of Kalah is end "when one player no longer has any seeds in any of his/her houses" at any side turn.
Does BGA's adaption have different rule?
Does BGA's adaption have different rule?
8. Apr 2014 8:37 • stst • Bug has been fixed:
The bug was corrected.
The game ends at two cases:
When a player, at his turn, is unable to move, because his no longer has any stones in any of his holes. The remaining stones are captured by his opponent.
OR
When a player collected more half of all stones in his/her Kalah.
I'm sure that it's the most logical variant of end of the game.
The game ends at two cases:
When a player, at his turn, is unable to move, because his no longer has any stones in any of his holes. The remaining stones are captured by his opponent.
OR
When a player collected more half of all stones in his/her Kalah.
I'm sure that it's the most logical variant of end of the game.
21. May 2014 8:49 • Freches_Feechen • Bug has been fixed:
Das Spiel endet noch immer nicht, wenn der eine Spieler mehr als die Hälfte der Seeds hat!
21. May 2014 12:29 • stst • Bug has been fixed:
I didn't see bugs at your 2 games. If it is, then specify a game table.
5. May 2020 20:07 • magister_ludi_43 • Bug has been fixed:
This bug has not been completely fixed. From what I can see, it only is fixed in some cases. From what I can tell - the cases are when the opponent runs out of seeds by capturing vs when they run out of seeds by landing in the goal.
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.
