I make games

  • 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle






  • 2d10 would be used if each arrow had a 10% chance of being cursed. But that’s not the case. There are 10 arrows, five are cursed, and 2 are selected. Therefore the first arrow would have a 5/10 chance of being cursed, while the second selection would have either a 4/9 or 5/9 chance of being cursed depending on whether or not the first arrow was cursed.

    To solve this, requires using combinatorics. There are 10 choose 2 (45) ways to choose two arrows, of which there are 5 choose 2 (10) ways to choose 2 arrows that are non-cursed. This works out to be 2/9 odds to pull two safe arrows. Which means you need to get funkier with the dice.




  • Sorry, that’s almost it but they don’t emulate hundreds or thousands of frames, you’re right in thinking that would be implausible. Basically what happens is retroarch makes a savestate every frame and keeps a running list of the last few. When you press a button, retroarch will load one of those states from a few frames ago, press the same button then, then disable video and re-emulate those “rewound” few frames in fast forward. Then once it’s caught up to the present it re-enable video rendering. The end result is that you see the effect of your input happening the frame after you press it, instead of the normal input delay of 2 or more frames. It’s pretty neat. But yea, this means that they’re only emulating an extra 3-5 frames or so not hundreds, and they only have to do it when you press a button, not all the time.