All reports
buttons_displayed reports
#33634: "White die seemed to roll against the odds"
rejected: Developers think that it is not a good idea or that the cost/benefit ratio is too high
1
What is this report about?
What happened ? Please select from below
Suggestion: in my opinion, the following would greatly improve the game implementation
Detailed description
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
White die rolled so many 5's and 6's, we thought it might be glitching.
• What is your browser?
Google Chrome v87
Report history
8. Feb 2021 1:10 • texpenguin • This suggestion has not been analyzed by delopers yet:
10 6s, 8 5s, and 10 of all other numbers combined. I know it's not impossible to roll that, but it's highly unlikely. Made for a very unfun game, for sure.
8. Feb 2021 18:15 • Freemind • Developers think that it is not a good idea or that the cost/benefit ratio is too high:
Hey,
BoardGameArena has through the years had complaints about the random numbers. This has lead to extra consideration being put into how they are generated meaning that the current way we generate random numbers passes quite a lot of the standard tests to decide if something is random. The current version of buttons use this implementation of the random numbers (and thus random dice throw), so we od not think that there is something wrong there.
Also I would not say this is highly unlikely. For sure if you specify the exact number, and especially the exact sequence then it is extremely unlikely, but then most other dice throws are too. However, if we just take the premise "two of the numbers occur more than half of all the 28 white dice throws" this event is not so unlikely.
BoardGameArena has through the years had complaints about the random numbers. This has lead to extra consideration being put into how they are generated meaning that the current way we generate random numbers passes quite a lot of the standard tests to decide if something is random. The current version of buttons use this implementation of the random numbers (and thus random dice throw), so we od not think that there is something wrong there.
Also I would not say this is highly unlikely. For sure if you specify the exact number, and especially the exact sequence then it is extremely unlikely, but then most other dice throws are too. However, if we just take the premise "two of the numbers occur more than half of all the 28 white dice throws" this event is not so unlikely.
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.
