The first step to creating a role playing game, for me, was to get a dice mechanic that I was happy with. Ignoring the actual ‘game’, you have to start with an engine, and to build an efficient engine you need to build it around a core. That core is what the players interact with the game the most: the dice.
I, like many people before me, have been studying dice mechanics in tabletop games. There are plenty of random discussions online where people toss around systems that they like or dislike. There are honest to goodness research papers that try to analyze dice mechanics from an academic point of view. And of course, there are plenty of blog posts - just like this one - that explain what conclusion they came to when going down this thought path.
The best sites that I’ve found try to define exactly what dice systems are trying to represent. My favorite of these definition sites is http://rpg-design.wikidot.com/evaluation. It breaks down the different possible simulated variables, and why the “perfect system” would use one way over another. This site inspired me to create what I’m calling an “inverse dice” system.
What dice systems today are missing is reduced variance as character skill increases. I define variance as the number of possible outcomes for a given roll. Reducing variance represents the character’s ability to perform more consistently. This is important because as characters become more skilled, they want to not only to be able to succeed at higher level tasks, but also fail less often (and eventually not at all) at easier ones. This means both raising their maximum dice roll, and skewing their distribution towards higher numbers.
So what do current systems do for us? Single die systems have a flat distribution, and a static variance. Multi-dice systems have a bell curve, but still always the same variance. They do increase the ‘average’, but it doesn’t actually skew the distribution at all. Dice pools are interesting, but actually have more variance as skill increases, since each die you add increases the number of possible outcomes. So far, no one is fitting our bill.
One of the simplest yet most innovative dice mechanic in recent years has been D&D 5e’s “advantage/disadvantage” mechanic. By no means were they the first to think of this concept, but I will cover their true innovation in a future post. Really, what the “roll two, take the higher” mechanic does for us is skews the distribution in one direction. This gets us a lot closer to the “ideal” distribution described in the rpg-design wiki article than a “normal” distribution does. But still, actual variance doesn’t change, as there are still exactly 20 outcomes. In fact, this mechanic boils down to about a 20% increased chance of success (roughly +4).
An unfortunate way of thinking about all of this is the fact that success & failure do actually boil down to a simple % chance. No matter how wonderful a distribution or varied variance you have, the roll will always come down to % chance of success vs. % chance of failure. So do percentile systems have it right? No, but not because they are necessarily wrong. The problem with straight up percentile systems is that they are either boring, too complicated, or more typically, both. Boring, I say, because generic % ups and downs do not excite players. Most people don’t want to know their exact chances.
"Never tell me the odds!" - Han Solo
But that’s not all - percentile systems also have a hard cap. You can’t get better than 100% chance of success. This is not great if you want a flexible game design, because when we want to know the chance of killing the rat vs. the dragon vs. the demigod, all of those numbers have to be relative. If you define your scope such that the dragon is a 99% difficulty enemy, what is the demigod? What these systems actually do is always compare skills and abilities against their target, and calculate %’s during the game. But that’s too complicated. We don’t want to calculate it ourselves - we want that information hidden away in our dice.
Instead, we want to easily see our character’s skills being represented relative to the presented challenge. The dice should be the formula; we shouldn’t have to apply the formula in order to roll the dice. An ideal system would allow us to simulate the world around the dice with infinite relative numbers. A +1 knife vs. a +50 dinosaur vs. a +1000 meteor just isn’t easy to do in percentiles.
Yikes… we’re almost running out of options! This is why I have not found a system that represents this ideal curve, and that some people have claimed it to be probably impossible. But we have a few things left to explore…
One of the more intriguing systems I’ve encountered is Savage Worlds. This system uses increasing dice sizes to represent character skill increasing. Unfortunately, this has the clear problem of increasing variance as skill increases, since larger dice sizes mean more possible outcomes on each roll. Yet, maximums are increasing, and most interestingly - even with ‘flat’ distributions per roll, the system actually has a really nice curve when compared against itself, with a property I also like: diminishing returns.
What really hooked me though, was the discussion around exploding dice in Savage Worlds. You “explode” when you hit the max number on a die, and you get to roll an extra die to add to your result. This leads to random wild rolls that can upset the game by having an unskilled character for some odd reason get really high results. Of course, while this is fun, a lot of people are turned off by it, because it doesn’t make any sense. Why should someone with less skill be more likely to pull of something extreme? The system still works, of course, but with this explosion mechanic, the chances of success per die increase don’t even change that drastically.
I hope at this point you might be thinking what I’m thinking. Let’s inverse the Savage Worlds system. Flip it on it’s head. Lets do smaller dice sizes as skill increases. Let’s make critical hits a ‘1’, meaning that the smaller your dice size, the greater chance of a critical hit. Awesome!
However, how do we actually make that work in a real system?
Dice Mechanics 101: Comparison > Addition > Anything else.
Basically, we don’t want to ever have to multiply, divide, or subtract (or, obviously, anything more complicated). This unfortunately means we can’t subtract, which would have been a very nice implementation to our shrinking dice (e.g. Challenge Rating [CR] - roll).
To solve this, we need to think about what other tools we have to play with. Some systems like GURPS have a “roll under stat” system, which is neat because most systems have character stats and skills rolled into one ( i.e. stat + skill = roll bonus ).
So in ‘roll under’ systems, success would be: roll + skill + CR < stat.
Wait a minute, this is perfect! Our problem with GURPS’s mechanic is that it has a static variance roll of 3d6, so let’s replace roll + skill with our shrinking dice mechanic. All of a sudden not only do we have a really simple equation: roll + CR < stat, we have created a solution for the most elusive of dice mechanics: the reduced variance!
Skill Roll + CR < Stat
But we’re not done yet. One thing we don’t have is a normal distribution. This is important because it reduces the chance of wild outcomes in regular systems - a way of mock-reducing variance, if you will. Or… is it? In fact, this brings us back around to how everything boils down to %’s. Remember, the only actual problem with % systems is that they tend to be uninteresting, and more importantly overly complex due to the need to calculate the chances as part of the game. So do we really need a bell curve? I don’t think so! Our single-die system is actually just fine, because while alone it has a ‘flat’ distribution, when compared with itself over the different skill levels, we see that the reduced variance actually creates a nice % skew curve!
Bonus points: the D&D advantage/disadvantage is still very elegant, because again ‘comparison’ > ‘addition’, so instead of adding +4, we get to roll an extra die and compare, which is actually more fun. So let’s borrow (okay - steal outright) the advantage/disadvantage system, and we’ve got ourselves a deliciously simple and satisfying system.
Now, while I have searched fairly extensively, I have not encountered a system that uses inverse dice like this. If you know of such a system, please let me know! I am unlikely to be the first in any of these thoughts, so it would be of great help to see how someone else implemented it, so that I can learn from their success/failures.
Interested to see how this system worked at the table? See my updated post about Inverse Dice in Practice.