Buying Trouble

A Fate Die Rolling Variant

Intent

I’ve been running a lot of games in the Blades in the Dark family lately, and enjoying it a lot.  I really missing having aspects as a knob to turn, but it’s full of other shiny bits.  The one that I really enjoy is the mechanization of the complications as something orthogonal to difficulty.  It’s an idea that exists in other forms in other games, Fate included, but it’s a tricky piece of tech that I’ve sometimes struggled with.

This is, hopefully, the end of the struggle.

Trouble

This rule has only two parts: Complications, and Buying Trouble

Complications

Complications are twists on a situation.  Stylistically, they have a fair amount in common with aspect compels, but mechanically they are separate from the aspect economy, and are instead tied to the situation at hand.  Aspects are fertile ground for inspiration for complications, but it’s bad sport to use a complication for something which is more appropriate to a compel.

Complications are created as a result of rolls, and it’s important to remember that the complication should never negate the success. The complication is *something else* going wrong – it may complicate the situation (thus, the name) but it should never devalue the success. Specifically, if the player takes a complication in order to avoid a problem, the complication should not be that problem. 

 Complications might include:

  • The arrival of opposition
  • Unwelcome information being released
  • Resources being used up
  • Flumphs

Complications come in 4 different levels

  1. Annoying – These are minor complications – maybe a small resource loss or a moment of slapstick.  
  2. Inconvenient – This complication is making the current situation a little more difficulty.  It might require another roll, an unexpected resource spend or otherwise keep things from going quite as smoothly as hoped. As a tip, this is *roughly* the severity of a compel. 
  3. Problematic – The complication is a problem of it own, and needs to be dealt with or avoided. 
  4. Disastrous – Things Go Bad.  This complication is a BIG problem, and is likely to totally upend the situation.

Buying Trouble

When a player rolls dice, they have the option of dropping all dice showing minuses to ‘buy trouble’.  Doing so changes the result of the die roll, but introduces a complication  of a level equal to the number of minuses spent.  

Example

Finn is picking a lock, because RPG Conduct Code demands that all examples include at least one door.   His player rolls – – + +, for a net zero.  Finn could take that, but he’s in a hurry – the guards are coming and he’s tight on time, so he buys trouble, and changes his roll from a 0 to a +2 and the GM is free to introduce an inconvenience.   

The GM should explicitly NOT have the effort take longer, or have the guards show up as a complication – that’s exactly what the player was buying trouble to avoid, so it would be a Jerk move.

If Finn’s been making trouble elsewhere, this would be a great time for that to be found out, and perhaps have an alarm go off.  This is going to make things harder, but it doesn’t create an immediate consequence.

But supposing he hasn’t, the GM might have the door go someplace other than Finn’s player expects.  Perhaps his map is wrong, or he picked the wrong door, and now he’s lost, or in an awkward location.

If Finn had bought more trouble (say, he’d rolled  – – – +), then the door might go someplace like a closet, or to a room where the staff are preparing a meal, and now he has a whole new problem. 

Using These Rules

You can drop these rules into any Fate game, and they’ll work fine.  However, there are some interactions that are going to be worth watching.

First, in games where there are a LOT of Fate points in play, this is going to be a less appealing option, because the mechanical utility of this approach depends on the pressure to offset a bad roll.  If fate points are bountiful, there’s very little pressure to take consequences.  That’s not necessarily a bad thing – presumably the many fate points mean that compels are keeping things plenty interesting, so complications are less necessary.  This rule still works in those games, it just may come up less often. 

Second, this approach synergizes well with having aspects flip dice rather than give a flat +2, because it keeps bonuses bounded, and it introduces a bit of a dynamic of using aspects to avoid trouble when appropriate. 

Options

Nuanced Trouble

There may be a temptation to let players decide how much trouble they want to buy (rather than have it be all or nothing) .  That’s fine, and it’s a reasonable option, but it has the risk of introducing analysis paralysis.  Don’t use this option if your players are going to take more than half a second deciding how many minuses they’ll spend.

Closed Economy

For players who like to constrain the overall Fate Point budget in play, consider this option:  

  1. The GM starts play with a fixed pool of Fate Points (say, 1 per player)
  2. When the player takes a complication, the GM may opt to take a number of Fate Points equal to the level of the complication.
  3. The GM’s Fate point pool is limited to those on hand.

Bargains

Aka “The Morgan Rule” – If you want to steal Devil’s Bargains from Blades, they can turn blanks to plusses.  Not sure if this really works, but – putting a pin in it as I think.

Next

So, this is pretty much version 0.1. I’m genuinely excited to try this at the table and see how it evolves. I suspect the closed economy option has got a lot of legs, because I think it might be a real solution to the se’f-compel issue. My biggest concern is to see how well it plays with the flow of fate points. They might be complimentary, but there’s a non-zero chance of them tripping over each others shoelaces, in which case this might be the basis for something else entirely.

2 thoughts on “Buying Trouble

Leave a Reply to Rob Donoghue Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.