A friend of mine had an issue when playing backgammon today. All her checkers were in the home board, some were on 1 and some were on 6. This is what happened when she tried to bare them off:
It's your turn. You roll the dice: 6 1 You take a checker out of the board from point 1. // she pressed enter twice on point 6 This move is impossible. You move a checker from point 6 to point 5.
It seems that the game thought that she used up her 6 to take a token off the 1, which isn't needed since there was an actual 1 she could use, and according to this guide even if she had no tokens on point 6 she would have to use the next highest point to bare off, so probably point 5 or point 4.
Skor: +0
2. YNWA,
It is not a bug and it is a bug if that makes sense.
When your friend rolled a 6 and a 1 your friend should have chosen 6 first then chosen 1. I have made this mistake when I first played gammon. In real life you can choose which token you want to take out first but not in the PR version. If you take out the token on 1 the computer will assume you have used up your 6, leaving just the 1 left.
Skor: -1
3. Sylphrena,
Nice find, I can also reproduce this bug. Most clear example: You roll the dice: 5 5 You move a checker from point 15 to point 10. You move a checker from point 10 to point 5. You take a checker out of the board from point 1. You take a checker out of the board from point 1.
Additional roles while the token is still in 5: You roll the dice: 5 6 You take a checker out of the board from point 2. You take a checker out of the board from point 4.
Skor: +0
4. Aminiel,
Hello,
I modified a little the logic deciding which die to use. Until now, it simply took dice in order. Now it tries to take the smallest possible die first.
So in the situation of the initial report, it should now behave as you expect, i.e. use the 1 to remove the checker on square 1 or 24.
Tell me if it's globally better now, or if it brings new or more frequent problems in other situations.
