Moves & the Fiction-Mechanic-Fiction Loop

TabletopInteractive Fiction

The loop that lets fiction call the dice and the dice answer back in fiction.

A resolution method tells the table how an uncertain moment comes out. A PbtA Move tells the table when that method fires and what its result means in the story. It is the sentence wrapped around the roll. Something happens in the fiction, the fiction matches a named condition, the dice come out, and whatever they say is read straight back into the fiction as the next thing that happens. The roll never floats free of the story on either side.

The idea is small and the consequences are large. An older style of play left it to the GM to judge when a roll was needed and what a failure ought to mean. The PbtA Move writes both of those down in advance for everyone at the table. Nobody has to argue about whether the moment deserves dice. The fiction itself settles that, and the result it produces is already written in plain sight. That single change quietly redistributes who holds authority at the most charged moment of play.

This article is about that loop and how to build one that keeps a scene moving. It assumes the layer beneath it, the Mechanical Resolution Types that decide how the uncertainty actually resolves, and it sits below the layer above it, the Turn Structure & Action Economy that decides how many of these loops a character gets and in what order. The resolution method answers how. The PbtA Move answers when, and what it means.

The Mechanism (How it works)

The grammar of a move

The PbtA Move comes from Apocalypse World, designed by Vincent Baker and Meguey Baker, where it is the central unit of resolution. Its shape is a small template that almost every later game in the lineage reuses:

When you [fictional trigger], roll +[stat].
On a 10+, [strong outcome].
On a 7-9, [mixed outcome, with a cost or a choice].
On a 6-, [the GM makes a hard move].

Each line does a specific job. The trigger is written in story terms, not mechanical ones, so it names a situation rather than a button: “when you act under fire”, not “when you want to roll”. The stat ties the roll to a part of the character, and because different character types carry different stat spreads, the same move plays out differently depending on who attempts it. The three result bands each carry their own prescribed fictional consequence, so the dice never produce a bare number that someone then has to interpret. The 6- is the most distinctive of the three: a miss does not simply cancel the attempt. It hands the initiative to the GM, who picks from a defined list of ways to make the situation worse.

The result text is itself fiction, and this matters more than it first appears. A strong outcome reads as “you take +1 forward” or “the GM tells you something useful” rather than as an abstract delta on a sheet. These are permissions and costs spoken in the language of the story, so the mechanical layer is always cashed straight back out into something happening. The roll is sandwiched between two fictional states and never leaves the fiction stranded on either side.

To do it, you have to do it

The rule that makes the whole loop turn has a blunt name in Apocalypse World: to do it, you have to do it. A player cannot reach for the effect of a move without first having their character do the thing in the fiction that the move describes. Announcing “I go aggro on this guy” does not put dice on the table. Pressing the barrel of your revolver to his forehead and telling him to hand over the diamonds does. Now the trigger for that move has fired. The dice come out. Whatever they show becomes the consequence. The converse holds just as hard. Narration that matches a trigger brings the dice out whether or not you meant to invoke the move.

This inversion, fiction before mechanics, is what the wider community came to call fiction-first design. The practical effect is that the fiction has to be established and concrete before anyone touches dice. A player who says “I roll to persuade him” has the grammar backwards. The correct sequence is to narrate the approach until the table recognises the trigger and the move fires on its own. Baker himself has pushed back on the “fiction-first” label as commonly used, pointing out that Apocalypse World contains plenty of moves with no fictional trigger at all, and that the real rule is narrower: you cannot get a move’s effect without taking its action, and you cannot take its action without getting its effect. The loop is the binding, in both directions.

A consequence for the GM follows from the same principle, and it is a craft rule worth stating plainly: do not speak the name of your move. The trigger and the outcome stay dressed in fiction. The GM describes a door kicked in or a truth revealed, not “I am separating you” or “I am announcing future badness”. The mechanical scaffold stays hidden behind the narration. This is the same instinct that interactive fiction follows when it shows the world while keeping the gears out of sight.

The triangle: fiction, mechanic, fiction

Set the grammar in motion and it traces a three-stage cycle. A fictional position develops until it reaches a trigger. The trigger fires the roll. The roll selects an outcome tier, and that tier becomes a new fictional position, which develops until it reaches the next trigger. The mechanic is the middle stage only, bracketed by story on both sides, and that is why the loop is named for fiction at both ends.

The shape of this loop is a structural cousin of something interactive fiction already does. An IF passage choice point converts a player’s fictional intent into a discrete branching event. The result then comes back as prose the player reads on. The trigger-and-outcome move is the tabletop version of that same conversion. A fluid fictional intent gets pinned to one defined event with known branches, and whatever the dice say returns to the flow as the next thing in the story. The corpus traces this parallel directly through the branching-narrative lineage. The lesson runs in both directions. A move that never returns its result to the fiction is as broken as an IF branch that sets a flag and shows the player nothing. The loop is only worth building if both ends close.

The load-bearing middle band

The reason the loop generates momentum rather than just resolving and stopping lives in the middle result. On 2d6 with no modifier, the three bands are not evenly likely.

Band	Result	Probability at +0
Strong hit	10+	~17%
Mixed hit	7-9	~42%
Miss	6-	~42%

At the stat spreads characters typically carry, a +1 or +2 in their best stat, the 7-9 band stays the most common single outcome. This is by design, not accident. Baker built the curve so that complication is the default state of play rather than the exception. The 7-9 forces a choice or attaches a cost; either way it drops a new problem into the scene. Characters rarely just succeed or just fail. They succeed at a price, or they succeed only by picking which of two bad things they will accept.

That structural commitment is what makes the mixed result the engine of the whole system. A game with only hit and miss produces a two-beat rhythm: success clears the obstacle and failure blocks it, and either way the scene is roughly where it started. The 7-9 produces a three-beat rhythm in which the most common resolution transforms the situation instead of settling it. This is the same fork that Mechanical Resolution Types names as the most consequential single choice in resolution design, the split between a binary method and a tiered one. The PbtA Move is what gives those tiers their meaning. A tiered die with no authored consequence is just three numbers; the move is where the third number becomes a real event in the story. The two layers are designed together, and neither works alone.

Player moves and GM moves

The word “move” covers two different things in PbtA, and confusing them is a common early mistake. Player moves are the dice-driven loop described above. GM moves (the GM is called the MC, the Master of Ceremonies) are a different kind of move entirely: no dice, no trigger roll, just a structured list of narrative interventions the MC is allowed to make.

	Player move	GM (MC) move
Fires when	the fiction hits a written trigger	the players hand the MC a chance (a 6-, a pause, a lull)
Uses dice	yes	no
Outcome	one of three written tiers	one item chosen from the MC’s list
Authority	shared, defined in advance	held by the MC, bounded by the list

The MC’s list is the part that does the quiet work. It reads something like: separate them; capture someone; inflict harm as established; use up their resources; turn their move back on them; reveal an unwelcome truth; announce future badness; offer an opportunity, with or without a cost; tell them the consequences and ask. This list is a creativity prompt and a constraint in one. It tells the MC what kinds of escalation are legitimate, and by doing so it forecloses the free-form “the GM decides what happens” that the whole system was built to replace. On a player’s 6-, the MC reaches into this list. The result is that even failure is bounded and generative rather than arbitrary. The MC’s list is to the MC what the move grammar is to the player: a procedural vocabulary that keeps authority shared even at the moment it is being exercised.

The Specimen

Dungeon World (Sage LaTorra and Adam Koebel, 2012) is the clearest case of the move grammar carried into a new genre without being copied wholesale. It keeps the trigger and the 2d6 curve with its three bands intact, then rewrites every move for fantasy adventuring: Hack and Slash, Volley, Defy Danger (its version of Act Under Fire), Parley. It also adds a layer Apocalypse World does not have. On a Hack and Slash 10+ you do not just succeed; you deal your damage and choose whether to avoid the enemy’s blow or deal damage again, and damage is its own separate roll. A game can stack extra mechanical layers on top of the move without breaking the fiction-first trigger underneath it. The move grammar is a frame, not a fixed list. Each game in the lineage rewrites its moves from scratch to fit the pressures of its own fiction.

Moves as character identity

There are two tiers of player move, and the split carries most of what makes characters feel distinct. Basic moves are available to everyone: in Apocalypse World these are the things any survivor of that world can attempt, like acting under fire or reading a person. Playbook moves belong only to a character who has taken that playbook, and they are where the character types diverge. The detailed craft of building those character packages is its own subject, Playbook Design; what matters here is how a move encodes who a character is.

A playbook move is not an ability bolted onto a sheet. It is a claim about the character written as a trigger. The Driver’s move “My Other Ride is a Tank” encodes that this person’s relationship to vehicles bends physical plausibility. The Battlebabe’s “Dangerous and Sexy” encodes that, for this character, beauty and threat are not separate registers but fire at once. This is a different design instinct from a class feature in a D&D-lineage game, where a Fighter’s Extra Attack is a numerical capability. The move is character description in procedural form. Later games push this further. Masks: A New Generation (Brendan Conway, 2017) gives teenage superheroes shifting Labels rather than fixed stats, so a move outcome can shift how a character sees themselves, and the consequence of a roll becomes a lasting change to who the character is mechanically able to be.

Custom moves and the limits of the frame

Beyond basic and playbook moves sits a third kind: the custom move, written by the MC or designer for one specific threat, place, or situation rather than for a universal category. A plague might carry a move that triggers on exposure. A particular NPC might come with one that fires when players deal with them under set conditions. Custom moves do two things. A player who meets one learns that the situation is now mechanically defined and the stakes here are encoded. A designer who writes one concentrates mechanical weight exactly where the fiction generates its characteristic tension. Published PbtA games lean on custom moves heavily to carry the specific themes of their setting.

The frame has a failure mode, and it is worth knowing because it is the most common way PbtA designs go wrong.

The Hazard

The seductive move is “when you do anything risky, roll +cool”. It looks like a move. It has a trigger and three outcomes. But the trigger is collapsed: it fires on everything, which means it names nothing. A working trigger points at a recurring, characteristic, high-stakes situation in the specific fiction the game is about. “When you sneak past a guard” works because stealth under threat keeps coming up in the genre it serves. “When you do anything risky” evacuates the fictional specificity that made the move a move at all. The deeper version of the same mistake is bolting the move grammar onto a genre whose tensions do not run through individual action under pressure. PbtA assumes characters take actions that have consequences for them; a fiction built on collective processes or the passive receipt of information generates pressures the grammar addresses poorly, and play drifts away from triggers that never fire. The test before you finalise a move list: does the fiction reliably put characters at this exact decision point? If play can run for an hour without a given move firing, the trigger is too narrow or it is the wrong move for this game.

Removing the dice without breaking the loop

The loop turns out to survive the loss of its own randomiser, which is the strongest evidence that the dice were never the point. Belonging Outside Belonging (Avery Alder, 2018) removes dice entirely and replaces them with a token economy. A weak move gives the player a token. A strong move spends one. A regular move needs no token at all. The trigger-and-outcome structure stays intact; only the arbitration changes from probability to resource management. A character can take decisive uncontested action only after first accumulating tokens through prior vulnerability and cost. The fiction-first principle and the tiered structure both survive. That survival tells you the move was always the binding between fiction and mechanic, not the particular mechanic it happened to bind to. How far a system can lean on emergent resolution of this kind is the subject of Elegance, Emergence & Randomness. Where the resolution layer sits relative to the world it models is System vs Setting.

Where this fits

The bigger picture. The PbtA Move is the layer that gives a resolution method its meaning in the story. The dice or cards underneath it answer how an uncertainty resolves; the move answers what fictional question was being asked and what each result means once it lands. So the two layers are designed as a pair and assessed together. A rich move sitting on a binary die throws the whole weight of the interesting middle outcome back onto the GM, and a finely tiered die sitting under a thin move is just numbers with no story attached. The move is also where a system makes its claim about authority. By writing the trigger and the outcomes down in advance, it takes the most charged decision in play, when to roll and what failure costs, out of pure GM fiat and turns it into something the table shares. That places any move-driven game firmly toward the rules-first end of the spectrum that Rulings vs Rules & the Authority Contract maps, because the move encodes in advance what a looser game would settle by ruling in the moment.

Next steps. Once the loop is built, the craft turns to the packages of moves that make each character distinct, Playbook Design. After that comes the economy that decides how many loops a character gets in a scene and when, Turn Structure & Action Economy. To place the move-driven game within the wider field of design traditions it belongs to, start from the TTRPG Format Taxonomy. The four-outcome shape the move depends on, success, success-at-a-cost, and the two flavours of failure, is the same engine that drives a scene forward in prose fiction, and that engine in its own right is Try-Fail Cycles & Escalation. The way a move converts fluid intent into a discrete branching event is the tabletop cousin of the choice point in Branching Narrative Craft.