Go to Part 1
We’ve reached the end of the road: The dice have been rolled. The mechanics have determined success or failure.
Now the GM needs to describe that outcome. (They need to complete the fiction-mechanics cycle by bringing the result back into the fiction.)
If the result is a success, this usually means answering two key questions:
- How does the intention succeed?
- Are there any complications (i.e., unintended side effects)?
If the result is a failure, the questions are:
- How does the action fail?
- What are the consequences of failure?
The process we talked about in Fictional Cleromancy sort of naturally elides into this: As you’re thinking about graduated results, you’re thinking about what the potential outcomes of the action can be. You can usually just carry these thoughts forward through the mechanical resolution.
The actual narration of what’s happening in the game world is, of course, more art than science. But when it comes to describing outcome, there are a few general principles that you can keep in mind.
INTERNAL vs. EXTERNAL FACTORS
First, consider the question of why the outcome happened. What were the determining factors?
Bear in mind that both internal and external factors can influence the outcome of a skill check. (The distinction here is between failing to crack the safe because you’re simply not skilled enough and failing to crack the safe because your lockpick was defective and snapped off.) A lot of GMs default exclusively to the former (the character made a skill check; the check was a failure; therefore it was the character’s fault), but it’s arguably more effective to remember that the randomness of the dice models the entire situation, not just variance in the character’s ability: Sometimes you fail a Steath check because a guard comes around the corner at exactly the wrong time. You fail a Jump check because the ground is unexpectedly slippery. And so forth.
Another way of thinking about this is that, in any given skill check, there are myriad factors that determine its ultimate success and failure. Some of these factors – generally the ones we care about the most – are known. (For example, in D&D we’re always interested in whether a character’s armor will protect them from an attack, so their AC is always factored into the attack roll.) A lot of factors, however, aren’t important enough or consistent enough for us to want to specifically track them, so we use a random number generator to account for all the different factors that could impact the success or failure of any given action (and then trust to the GM to adjudicate the result accordingly).
For example, let’s say that the PC goes to a library and makes a Research test in order to find a particular piece of information. The test fails. The GM decides that it’s because the library doesn’t own a copy of the book that would contain the information.
Some people struggle with this because, if the book wasn’t present in the library, then the PC shouldn’t have had any chance at success on their Research test. This is a fundamental misunderstanding, however: Nobody at the table knows that the book isn’t there until the fictional cleromancy of the random number generator (combined with the GM’s ruling of what that outcome means) gives them that information. The library’s ownership of the necessary book is just one of a multitude of different external factors that could result in failure. (Other external factors might include whether the books has been checked out; if the book has been shelved incorrectly; has the book been damaged; does the book exist at all; and so forth.) The point is that we don’t care about any of these external factors enough to track it or model it mechanically, and so they all get abstractly bundled into the random number generator.
And, because all of these factors are bundled into the random number generator, it’s the GM’s responsibility to creatively unbundle them as they describe the outcomes of action resolution.
But what if we DO care about whether or not the specific book we want is available in this specific library? Well, in that case the GM would specifically determine that – through a listing of all the books in the library; or a list of all the places where that book exists; or maybe through a random percentile check – and then, like the armor bonus to AC, directly factor it into the success or failure of the Research test. (For example, if the GM knows that only one copy of the book survives anywhere in the world and they know that copy isn’t in this library, the Research test would automatically fail.) But when you make an external factor like this explicit, it’s no longer part of the abstract factors being modeled by the random die roll.
(It should be fairly obvious, of course, that no matter how many factors you make explicit there will always be factors you haven’t accounted for when you’re making a skill check. If there weren’t, in fact, you wouldn’t be making the skill check: You’d simply be defaulting to yes or saying no. Saying that the outcome of the action is random is inherently saying that there are factors that may or may not affect the outcome.)
FACTORS INFLUENCING OUTCOME
The ways in which characters can succeed or fail are as varied and limitless as the panoply of actions they can attempt in the first place. With that being said, there are some general principles you can keep in mind when describing outcomes.
SKILL: The most obvious of potential factors. Sometimes you have the best game of your life and sometimes you screw up and fall on your face. A lot of things can impact success or failure, but sometimes you succeed because you’re just that good (or fail because you’re just not good enough).
KNOWLEDGE: Is the character familiar with this particular model of safe? Do they recognize the patterns in a game of chess? Sometimes having just the right piece of information makes the difference between success and failure.
POWER: Sometimes people succeed because they just put more power into the attempt, or fail because they didn’t. A guard raises his sword to parry the barbarian’s blow, but her mighty thews sweep it aside and crush the guard’s skull.
FINESSE: And sometimes actions succeed because of the precision with which they are performed.
ENVIRONMENTAL FACTORS: Slippery floors. Frigid weather. Jammed locks. Floors that buckle under foot. Piles of fetid garbage that get in the way of your swinging sword.
TIME REQUIRED: How much time does it take to complete the action? High margins of success might indicate that the action took less time for the character to perform. A failure might result from something taking too long.
LUCK: Sometimes the biggest reason a character succeeds is because they’ve gotten lucky. The giant’s sword was going to take their head off, but it deflected off a falling piece of rubble. They were about slide off a cliff to certain doom, but they grabbed a piece of scrub brush and miraculously its roots held.
THE TARGET: Whether the target is an object or a person actively opposing the character, they can obviously have an impact on the success or failure of an action. These are the locks that are devilishly difficult or the gullible guard who easily falls for your lie.
BYSTANDERS: In addition to the character directly targeted by an action, it’s possibly for other characters to either interfere or assist in the attempt (whether wittingly or unwittingly).
TOOLS: You’re only as good as your tools. Lockpicks break, elven blades slide through seams in armor, inferior IC makes a system vulnerable, and luck charms crafted by your beloved can give the edge in a mystic duel.
These obviously don’t represent the totality of factors that can affect outcome, but hopefully they’ll provide a little inspiration.
(Way back in 1999 I wrote Dice of Destiny for Pyramid Magazine which mechanized this process by assigning qualities similar to these factors to individual dice in a dice pool system. If you find yourself struggling to diversify your outcome descriptions, you might want to check it out.)
MAKING FAILURE INTERESTING
Something else to remember is that the gatekeeper of mechanical resolution is that failure should be interesting, meaningful, or both. In other words, it should have consequences.
This can be one advantage of using external factors in explaining failure: If the character’s research at the library reveals that the book they need only exists in one place, for example, their next action will be to figure out how to get access to it.
What this means, in practice, is that failure generally should NOT cause a return to the status quo. This doesn’t necessarily mean failing forward, but it’s usually best if the outcome of an action – regardless of success or failure – should in some way change the situation. FATE refers to this as “blaming the circumstances”, and the advantage is that the new situation creates new options (which prevent the situation from stagnating or becoming a dead end).
(All of this also applies to success, but as I’ve mentioned previously this generally takes care of itself: Success implies that the character is one step closer to achieving their goals. A stated intention can almost always be summarized as “I want to change the current situation” and, therefore, the success of that intention automatically carries with it a change in the current situation.)
KEEP IT PITHY
Vivid descriptions are great, but try to get the ball back to your players ASAP.
A necessary corollary of making the outcome of an action interesting by giving it consequences it that you will have created a situation which (ideally) demands a fresh response from the PCs. Once you’ve established that new context, give the player’s the opportunity to make that response.
Instead of narrating the outcome themselves, a GM can instead prompt a player to provide the description. (Often this is the player attempting the action, although it can also be outsourced to other players at the table.)
For example, the GM might say, “You’re spotted as you try to sneak onto the mansion’s grounds. Who spots you?” Or, “You make a loud noise as you climb in through the roof. What’s the noise and how are you responsible?”
(Providing specific improvisation prompts like this – instead of simply asking a generic, “How do you fail?” – is generally more effective because it focuses the player’s response. You’re less likely to get a blank look if you ask a player to finish painting a picture instead of just handing them an empty canvass.)
Using the technique in this form grants the player a limited degree of narrative control. As such, it tends to work great in storytelling games (where it becomes part of a wider tapestry of methods for sharing narrative control). When used in a roleplaying game, on the other hand, I’ve generally found it problematic: It doesn’t really give the players any narrative autonomy (since they can only take narrative control when the GM gives it to them), but periodically forces them into a potentially disruptive and undesired authorial stance.
(In other words, if you want players to have that kind of narrative control, you’re probably better off playing a game that’s designed to do that.)
But that’s not the be-all or end-all of the technique. Instead of having the player get into an authorial stance and describe how the external world affects their character’s intention, you can instead have the mechanical result serve as an improv seed that informs how they play out the scene.
This can be particularly useful for social scenes: Instead of playing out an entire seduction attempt and then rolling to see if it succeeds, for example, you can make a Seduction attempt and then roleplay the scene based on the mechanical result.
This, however, begins to transition us into a discussion of fortune positioning, which is what we’ll covering in the next installment of the Art of Rulings.
Go to Part 10