All reports
Space Base reports
#63467: "Random Number generator"
rejected: Developers think that it is not a good idea or that the cost/benefit ratio is too high
6
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.
The random number generator for this game does not seem to work properly. If you roll 2d6 (two normal dice), the probabilities for each number are weighted most toward the middle numbers, six(13.89%), seven (16.67%), and eight (13.89%). This means that 44.45% of the time, the dice should equal one of those three numbers. After more than 80 plays of this game, I can tell you that there is no way those percentages are holding up. What appears to be happening is an even chance (9.09%) of rolling each number from 2 through 12, rather than the proper spread we should be seeing. The end result is an overwhelming amount of rolls away from what should be the most commonly rolled numbers.• Which browser are you using?
Google Chrome v100
Report history
Apr 25th 2022 4:10 • Talon378 • This suggestion has not been analyzed by the developers yet:
This is occurring in every game I play of this game. The lack of compliance to what should be the proper probabilities for the spread of rolls means that the strategy of the game is altered and becomes MUCH more random.
May 6th 2022 7:05 • Rick_M • This suggestion has not been analyzed by the developers yet:
I also sense that the dice rolls are not random. We just played 4 games and (1)(2) roll was much too frequent. I remember the first time I played and rolled 4 elevens in a row to start the game. I'd run some stats on the dice, but capturing the data from a game would be much too tedious.
Also, we had the same 4 players and selected replay option. The game displays message saying that player order is randomized, but we were in same order each game.
Also, we had the same 4 players and selected replay option. The game displays message saying that player order is randomized, but we were in same order each game.
May 9th 2022 2:01 • Talon378 • This suggestion has not been analyzed by the developers yet:
Table #265890439
I had purchased sectors and set my board up to give me victory points any time I rolled a 7 or above. I rolled victory points once, and has to spend a cube to move to victory points a second time. It is ridiculous that in 50+ turns I could not roll a 7 or above. Fix your dice roller!
I had purchased sectors and set my board up to give me victory points any time I rolled a 7 or above. I rolled victory points once, and has to spend a cube to move to victory points a second time. It is ridiculous that in 50+ turns I could not roll a 7 or above. Fix your dice roller!
Jun 21st 2022 20:06 • Biking Gamer • This suggestion has not been analyzed by the developers yet:
I concur - the dice rolls on this game (and others) does not appear random. I recommend using the milliseconds on clock time as a seed for your random number generator -- that should produce more random results.
Feb 10th 2023 16:29 • Andrew C-137 • This suggestion has not been analyzed by the developers yet:
@ Rick_M
A simple solution for tracking dice throws is already there. All that needs to change with the stats at the end is to breakout a second column so that you can see the occurrences of single die results, then the second column shows "Two-Die" results. Right now having them combined is meaningless, but to see those separately, along with a total column at the end, will give you easily scrapeable data. One game of course won't be enough (anyone who's played roulette and seen a run of 50 reds knows what I'm talking about), and you'll have to extrapolate for 1's and 12 over 2 and 6's, but seeing that data over dozens of games might help people see if it's truly close to random.
A simple solution for tracking dice throws is already there. All that needs to change with the stats at the end is to breakout a second column so that you can see the occurrences of single die results, then the second column shows "Two-Die" results. Right now having them combined is meaningless, but to see those separately, along with a total column at the end, will give you easily scrapeable data. One game of course won't be enough (anyone who's played roulette and seen a run of 50 reds knows what I'm talking about), and you'll have to extrapolate for 1's and 12 over 2 and 6's, but seeing that data over dozens of games might help people see if it's truly close to random.
Feb 12th 2023 16:18 • Shazzypaz • Developers think that it is not a good idea or that the cost/benefit ratio is too high:
Developers are instructed to use the bga_rand() function, no flexibility to use another function. If you are concerned about the randomness, please upvote boardgamearena.com/bug?id=72077.
Apr 7th 2023 1:40 • Antstad • Developers think that it is not a good idea or that the cost/benefit ratio is too high:
Just upvoted. I sware it's getting worse on the site.
Add to this report
Please add here anything that seems relevant in order to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? 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.
