⚠⚠⚠⚠⚠⚠WARNING⚠⚠⚠⚠⚠⚠ If you don't find code, math, and logic interesting, don't read on. If you do your brain will likely melt into goop inside your head. That wouldn't be fun. If you want to read about how this project came to be, read on brave soldier. So, some background on this project: I was watching a video about a guy who said that if you rolled 6 - 6 sided dice 1,296 times, you would theoretically eventually get all six dice at the same number at least once. I did some research and found out this is not true. The odds of this happening is 1 in 7,776. Exactly 6x more than what this person said. I figured I wanted to try it, so in 20-30 minutes, I whipped up this not beautiful-looking project, but the math is solid and accurate. What this project does is it requests the amount of iterations ie. the amount of times it runs the simulation to get the same number on each "dice" and then the max value ie. if you had a 6, 8, 10, etc. sided dice. Note: Anything over 12 takes over 30s to complete with only 10 iterations. I know this is a lot of fancy coding and math words, but if you just tried the project it would make much more sense than reading these paragraphs of explanations here. Why are you still reading? Go try it out :D. If you still tried and couldn't figure it out, comment, and I will try to make it make more sense in your specific scenario. I ran it at multiple amounts of iterations and got numbers really close to the projected 7,776 250: 7961 - 185 Away 350: 7201 - 575 Away 500: 7512 - 264 Away 1,000: 7412 - 364 Away 1,500: 7846 - 70 Away 3,000: 7798 - 22 Away! 5,000: 7683 - 93 Away 10,000: 7803 - 27 Away! 15,000: 7772 - 4 Away!!!! @Miss_Amuchi Now, these numbers are averages because the actual values varied wildly. When I was getting the value for the 350 one, I got a value of 65039 times it rolled to get all at one value, then when I rolled the 500 one, legit - no joke - one took 14 rolls to get the same on each. If you have the patience to wait through entire minutes running this, I would love to know: a) who actually read this whole thing and b) the average number of "rolls" for larger numbers: 15K, 50K, 100K, 1M?? Comment it and I will add it with your name next to it for all the real ones who read the whole thing :D Another thing: It doesn't really matter if you use Scratch or TurboWarp except for one thing: the more iterations you do it is better on TurboWarp. I ran the 1,000 on Scratch and 1,500 and higher on TurboWarp - at the same time - and the 1,500 on TurboWarp finished before the 1,000 on Scratch got halfway. Link: https://turbowarp.org/1320454424?fps=60 Note: I just put this in a word counter and got 554 words. This is a whole research paper instead of the documentation to a Scratch project lol. I probably spent more time writing this than making the project. Thanks for checking this out :D I really appreciate it. Wanna go drop a follow?
