This question may have occurred to you, Is this your dice algorithm fair? If your accepted definition of what should be considered as "fair" is you always be a winner and always have amazing numbers you demand, the answer is No! Life can't always be fair accept the fact that you can't always be happy, winning, or not getting sick.
Our system is designed exactly neutral like a casino, and as a host, we just connect people together. we can not give you fake victory by robots to save you always happy! Thousands of players per the second request to the servers and they just respond with two numbers. A neutral place does not have the desire to cheating clients therefore the random number generator is not a business secret anymore and this claim needs to prove with evidence and logic, not just beautiful words! so let's check the code.
Math.random() creates a number between 0 - 0.9 ,Then *6 multiplies random number by 6 and this creates a number between 0 - 5 Example: 0.4 * 6 = 2.4
Math.floor() takes a decimal number and converts it into an integer 2.4 = 2
The +1 is then added to create a number between 1 - 6
We learned from the experience of others to never design a private algorithm for making numbers, so we used a simple code in JavaScript language. This code structure allows us to handle millions of requests per second and thousands of players around the world send requests to the servers and they just respond with two integers. When it comes to Google and utilizing Google Cloud Platform, there are a lot of advantages. Even if you are still 0.01% suspicious or paranoid, do not worry, our engineers will be with you to show you the code live on the servers. Contact us now.
Our product cannot perfectly emulate real-life gameplay, and our goal is to serve as an unbiased host with full transparency. As we mentioned earlier, we do not monitor the numbers, which means we do not know, during any of the games from beginning to end, what numbers were generated or will be generated. The sequence of generated numbers is not linear, but parallel. The only way to ensure randomness and balance the distribution would be to always monitor all previously generated numbers and change them to balance the game, but sadly, this is against our goal as a neutral host. For example, to fix this issue at the beginning of the game, sometimes you have to re-roll up to 15 times before one side can start. However, our code assigns a pair of dice exclusively to each person, and the distribution for 10,000 backtests was as follows.
2: 2.31 % 3: 5.29 % 4: 8.31 % 5: 11.41 % 6: 14.03 % 7: 16.54 % 8: 13.91% 9: 11.31 % 10: 8.99 % 11: 5.14 % 12: 2.76 %
Our number generator is blind to the game and the position of the pieces, and it doesn't know when the dice are useless. Its functionality is like a big public red button that hundreds of thousands of people press every second, and it just replies with two integers. Due to its parallel nature, the number generator doesn't know what numbers were generated or will be, so this experience is inevitable.