All reports
golf_displayed reports
#123844: "Not optimal scoring"
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
In the third game, I (mgu2) had a row of 2's. The game was set to "Line scoring" and the game scored this game as two rows. However, it was more optimal for my board to be scored as three columns because the 2s would not have been matched and would have counted as -2 each rather than a row of 0.
When scored as rows, I had 12 points, which resulted in me losing. If the game had chosen columns as I suspected it would, my score would have been 6.• Is the rules violation visible on game replay? If yes, at which move number?
End of game scoring• What is your browser?
Google Chrome v124
Report history
13. May 2024 23:22 • mgu2 • Bug has not been reproduced by delopers yet:
All cards are revealed and scored
Myslexic Drew: 12 points
♦7 ♥K ♦3
♣4 ♣K ♥2
mgu2: 12 points
♦2 ♣2 ♠2
♥4 ♠7 ♦A
Myslexic Drew: 12 points
♦7 ♥K ♦3
♣4 ♣K ♥2
mgu2: 12 points
♦2 ♣2 ♠2
♥4 ♠7 ♦A
13. May 2024 23:24 • ufm • This is not a bug:
There is no such thing as 'optimal scoring'. You can't selectively apply column/row scoring.
13. May 2024 23:25 • mgu2 • This is not a bug:
Why did the game selectively apply row scoring rather than column scoring?
13. May 2024 23:30 • ufm • This is not a bug:
It didn't selectively apply scoring... You created a row and it triggered row scoring. Columns and rows are NOT exclusive.
13. May 2024 23:34 • mgu2 • This is not a bug:
And this leads to my scoring bug: Why was it programmed to trigger row scoring?
Row scoring resulted in 12 points. If it triggered column scoring instead, it would have resulted in 6 points.
Row scoring resulted in 12 points. If it triggered column scoring instead, it would have resulted in 6 points.
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.
