Procedures
A procedure is a set of steps the GM follows to run a longer moment in play, such as a fight, a negotiation, a heist or making a new character.
When to use a procedure vs a script
Use a procedure when the GM has to judge as it goes: how a fight unfolds, when a negotiation turns, what a failed step costs. Use a script when the steps can be written out exactly, such as math, rolls and bookkeeping that should come out the same way every time.
A quick test: if your steps read like "do this, then this, then check that" and leave the GM nothing to decide, write a script. The GM runs a script and narrates the result, where it would have to work through a procedure one step at a time, and can slip.
The two work together. A procedure for a whole fight can tell the GM to run a script for each attack. Scripts lists what a script is good for.
A third kind of rule, the situational instruction, covers a moment too short to need steps:
| Write | When the rule is |
|---|---|
| A situational instruction | A short ruling about a single moment, up to 1,000 characters |
| A procedure | Several steps for a longer moment, where the GM has to judge as it goes |
| A script | Exact logic: math, rolls and bookkeeping that run the same way every time, or a card the player uses |
How the GM uses a procedure
The GM doesn't read your procedures on every turn. It keeps a list of their titles, and beside each title a line saying when to use it. When the story reaches one of those moments, the GM picks the procedure from the list and reads all of it.
The trigger check helps. Twice a turn it reads the moment, and when a procedure's "when" line fits, it names the procedure to the GM as one that may apply. It never hands over the text, as it does a situational instruction's: the GM decides whether to read it, and the title and the "when" line are all either has to go on.
A procedure that belongs to a player option's choice is on the list only while a player has that choice picked.
Writing one
A procedure has a title, a line saying when to use it, and the steps.
The title (name) is what the GM sees in its list, so name the
procedure after its moment. "Ship combat" is a good title. "Rules 2"
doesn't tell the GM when it applies. Every procedure you write needs a
title.
When to use it (trigger) is one line that starts with "When", such
as "When the ship fights another ship". It is required. The GM reads it
next to the title when it decides whether the moment has come.
Triggers explains how to write a good
one.
The steps (body) go in the order the GM should follow them. Start
with a sentence that says what the procedure runs, then give each step.
A step can name a script to run when the moment calls for one: "once
the player picks a target, run the attack script". That is optional.
Many procedures need no scripts at all.
Two things don't belong in the steps:
- A rule that already has its own situational instruction. Leave it there, so the rule is written once.
- A tracker. A procedure can't define one. Give the tracker its own instruction (see trackers).
Here is a whole procedure:
Salvage dives
When the crew dives into a drowned building
A dive runs room by room.
- Before it, ask what the crew is after and who stays topside on the line.
- In each room they search, roll 2d6 + Wits. On 10 or more, they find what they came for. On 7 to 9, they find it, but the air runs low or the structure shifts. On 6 or less, they find trouble instead.
- After the third room the air is gone. Anyone still below takes 1 harm for each extra room until they surface.
- Back topside, the crew splits the haul, and someone on the shore has seen them come up.
In the Game Master place, add an instruction and set Applies to Procedure. The form then shows Use it when… and Pruned beside the Title and the text, which holds the steps.
How long the GM keeps it
Once the GM has read a procedure, the text takes up room it could use
for the story. You choose how long it stays (pruning, shown in the
editor as Pruned):
| Setting | The GM keeps the text | Use it for |
|---|---|---|
After use ("after-use", or left out) |
Until the turn ends | A moment that fits in one turn, such as making a character or a single combat action |
On compaction ("on-compaction") |
Until the game's memory is next compacted | A moment that runs over several turns, such as a whole fight or a long negotiation |
A compaction happens in a long game, when Craft folds the older turns into a summary to make room for new ones.
Most procedures should use After use, because it frees the room soonest. If the same moment comes up again later, the GM reads the procedure again.
Keeping the list short
The GM chooses from titles alone, so it chooses better from a short list. To shorten one:
- Merge procedures that work the same way. Two kinds of contest with the same steps can be one procedure.
- Turn a short procedure into a situational instruction.
- Split a procedure that is over the length limit into one procedure for each phase, each with its own title and "when" line.
- Don't repeat Craft's procedures. If your world fights in its own way, either write a procedure that holds only the differences and sits beside Craft's Running a fight, or replace Craft's with your world's version (see Craft's defaults).
Limits
| Limit | Value |
|---|---|
| Length of one procedure | 10,000 characters |
| Procedures in one game | 25 |
The count is taken for the game with the most procedures a player could set up through their option picks. It includes Craft's own Running a fight, which a world can change or remove.
Four more procedures are built into every game: Travel, Trackers, Hidden things and People on the map. They don't count toward the limit, and a world can't change them.