# Double It

In the back of one of the manuals for the Civilization computer games – I forget which one – there’s a section that talks about how the game was designed. This contains a nugget of wisdom for game designers of any stripe: “If something isn’t working, double it or halve it.”

I think that this principle is a very sound one. Suppose you have a situation like “The penalty for juggling while skateboarding isn’t high enough – nobody feels its that difficult in game, though everyone agrees it would actually make it quite a lot harder in the real world. Plus the guy who can force people to skateboard feels way underpowered because putting people on skateboards is barely impacting their juggling at all.”

It might be tempting to increase the penalty by one and see if it makes a difference. The problem is that playtesting tends to produce a fairly limited set of data points, because of random variance (Even if the game has no randomness the skill of the players you have is a factor and even if you are testing with the same players over and over they will have good days and bad days). It’s fully possible to have an experience where something is weak, so you make it more powerful and then to play a half dozen games in which it does even worse. Just by chance.

So to actually see the difference there’s a sense to making big changes. We’ll not increase the penalty by one – we’ll double it! It may well be that doubling makes it waaay too hard to juggle while skateboarding, but if that’s the case you know the undoubled variable was a little too small and doubled was far too high and that gives you information to pick the right point in between. Compared to the very real chance of learning nothing with a one point bump, there’s a good argument for doubling.

The thing about doubling is that you really have to understand where your zero point is.

Imagine two systems for a game.
In system A I roll D6 + 3 and need to get a 7+
In system B I roll D12 + 3 and need to get a 9+
The chance of success in both are the same. But if (for whatever reason) we double that +3 then they change a lot. I don’t know about you, but I’d be super confident of rolling 7 or higher on D6+6.

The trick is to understand what doubling something actually *is*, specifically it’s making it twice as big relative to zero. However in our first game zero is clearly not the default state, presumably when we set the target as “7+” we anticipated that under normal conditions the player would have some sort of bonus to the roll. Perhaps in the average situation a player has +1 to this roll – in that case we should treat that average case as zero and double relative to that. So when we want to double our +3 modifier rather than doubling the number itself we double the difference between it and the zero point, making it a +5.

If you’re feeling fancy you could look at the ratio of success to failure and aim to double that rather than doing anything with the raw numbers. D6+3 will have a ratio of 1:1 between successes and failures, so we might want to double that to 2:1, which means wanting a 66% chance of success. That means we want 3/6 sides of the dice to result in success and so can make the modifier D6+4 – it turns out that the random factor and target numbers we’re working with are sufficiently small that in this case a one point bump does make a big enough difference!

I’ve been doing a lot of this with Genesis recently, having built up datasets to the point that they show me which things it’s great to be a god of (Fire, Showmanship) and which ones tend to lead to failure (Madness, Undead) I wanted to make a new version to rebalance things. However it takes a *lot* of plays to get a decent amount of data for Genesis since a lot of the gods aren’t used in any given game so keeping the number of iterations down is important. That means adopting a policy of making significant changes that are going to show enough of a difference to meaningfully drive decisions, but doubling the level of a card in this game isn’t something that makes sense. A card is level 1-10 so fully half of them can’t be doubled without extending the range. It’s been better to look at “How many other cards in the game will this beat” and to aim to change that number significantly, though of course changing any card slightly changes that number for every other card ðŸ˜‰

The point is that while doubling a thing feels dramatic making big changes during testing is healthy. You learn more than small changes and sometimes it turns out that a big change is what you needed and you can keep it as is. The rule of “double” isn’t necessarily important so much as the overall philosophy, but if you do want to keep it the trick is to be mindful of what you’re doubling and relative to what zero point: Raw numbers often don’t tell the whole story.

# Thematic Dice Rolling Systems

A while back I wrote an article comparing different ways to roll some dice and get a result that produced the same average result but had different probability profiles. Today I wanted to talk about a way to make use of some of those features: Making the method of dice rolling tie into the theme of a game.

Consider Zombicide. If we grab ourselves a precision rifle and fire on a zombie we roll 1D6 and will kill it on a 3+. One the other hand if we go for the submachinegun we roll 3D6 and will kill it if any of them work out as a 5+. The rules never explicitly state “Accurate weapons roll fewer dice but need lower numbers to hit, inaccurate ones do the opposite” but the pattern is established through repetition on most of the games weapons.

This is a good feature for a game to have. Ideally a game should have a lot of little things that are needed for the game to progress and serve other gameplay purposes building on each other to establish links between the theme of the game and what the players are actually doing. Even if the probability is the same if you set off some kind of huge explosion throwing a large pile of dice is more satisfyingly “explosiony” than throwing a small pile.

However as well as the visceral feel we should also remember what different systems do to the probability curve. Thematically you might want an explosion to be and feel chaotic compared to – say – a sniper. Throwing a boatload of dice has that visceral feel, but in terms of what it actually does the “many dice” thing tends to be more reliable because when you roll several dice together you get a bell curve. That is to say that the average result occurs more often and the extreme result less often, compared to rolling one dice where rolling a middle number and rolling the highest or lowest number all have the same chance to happen.

So are we stuck in a situation where the visceral feel of a thing is directly opposed to its actual effect on the game? Of course not!

We can think about how we apply modifiers. If someone is rolling some D6s and needs X+ on each one to get a hit we’ve got three levers: We can change how many dice are rolled, we can change what result is needed for a hit and we can change how many hits are needed.

On a side note, it’s generally desirable to modify as few things as possible so that when someone sees “-1” they know what it applies to because the game is consistent – but it’s still worth considering which one to modify.

If a modifier applies to the number of dice it has a more profound effect on “1D6 3+” than “3D6 5+”. Adding an extra dice increases the chance of success by 23% for the first pool, only by 9% for the second. Taking one away is even more profound since with zero dice the first pool can’t succeed at all.

By contrast if it applies to the number that has to be rolled it will affect the “Big dice, high number needed” pool more dramatically since that target number applies to every dice and it has more dice to be affected.

So if we’re looking to make it so that we can use a big pile of dice for explosions or shotguns or risky behaviour in general but also have the probability profile make those things riskier rather than more certain – where does this mean we put our modifiers?

The answer is “It depends”. Specifically it depends on why you might be modifying a dice roll. If the most common sort of modifier is a positive modifier because the character doing it is really skilled it makes the most sense for it to be a dice modifier. That way a skilled character gets the most out of doing a precision activity – the game will “feel right” when a champion marksman adds more to a sniper rifle than a scattergun.

On the other hand if the most common modifiers are negative situational modifiers because the weapon’s old or you moved or whatever then applying them to the target number may have the desired effect. The chaotic weapon will break down when the circumstances are against it but the reliable one will – well – be reliable.

Modifiers aren’t our only option either. A lot of games use rerolls as a means to provide reliability. If you’re happy that your game won’t be slowed down too much by the extra decision and roll step involved in having one then providing them can be a way to distinguish risky but dynamic actions from reliable less dynamic ones. That way we can still give our grenade a huge dice pool but make our sniper rifle’s smaller dice pool stick more closely to the bell curve – if the pool is smaller but less than half the size then providing one reroll makes it effectively larger in terms of reliability – so it can be small for the visceral action of picking dice up and doing things with them but large in the abstract mathematical sense of how it actually behaves.

Finally – the most important thing to consider is how a game breaks free of a fail/success binary. The examples above talked about “Roll one hit to succeed” but even in the Zombicide example, there’s a reason to roll more than one hit. If the player scores several hits they kill several zombies – good times.

This feeds into the theme as well. It means that “3D6 5+” has an advantage over “1D6 3+” not only in having a better average and being able to more consistently score a success – but also in that it can potentially kill up to 3 zombies where the other version will only ever kill 1.

It didn’t have to be this way – the rule could have been “Look at only the highest dice, if it’s below the target number nothing happens, otherwise it kills a zombie plus an additional zombie for each point it exceeds the target by”. Then a 3+ could kill up to 4 zombies and 5+ could only get 2 even if it had lots of dice.

The rule makes sense for that game – it’s intuitive that a spray of automatic fire could kill several zombies were one very well placed shot usually wouldn’t – but perhaps your game isn’t about shooting zombies. Perhaps your player is rolling for their ad campaign to convince the nation that keeping the planet inhabitable to humans is more important than saving a few quid on groceries. If your critical success is “Convinced some persuasive celebrity” then maybe a “Brute force the campaign with lots of money” approach should roll lots of dice and be consistently effective, but you want the best chance of a critical effect to lie with a “Carefully targetted ads” approach.

There’s not only one way to do these things – the point of this article is to remind us to be conscious of them. There are a hundred ways to resolve “I’d like the player to throw some randomisers to see if this works” into a rule. It’s worth taking the time to pick the one that not only makes your game work best as an abstract mathematical model, but also the one that’ll help players to be invested in the theme and for the things that happen to seem like they intuitively make sense from the actions the mechanics are describing.

# Know what you don’t want

A brief apology for missing last week’s update – my spine failed while I was swimming and made a semi-convincing attempt to drown me (but it’ll have to try harder than that!) I’ll write a bonus post next week to make up for it ðŸ™‚

Genesis Icons

I recently hired a graphic designer to put together some icons for the upcoming Genesis game. I told them that I needed icons for a number of different domains, which would be things gods had power over. So a water icon for the god of water, a death icon for the god of death and so on. Specified the size of the icon, showed the graphic design it was going to slot into, provided some hex codes for the colour palette I wanted to use and left it with him. Here’s the first draft that got sent to me for approval: