Craft

Writing good instructions

The GM reads its always-on instructions on every turn of every game, and it follows a few clear rules far better than many crowded ones. Most worlds that play badly have too many instructions, not too few. This page says what a good one looks like, so you can check the ones you have. Which kind of instruction a rule should be is in GM instructions.

Put each rule in the right kind

Most trouble with instructions is a rule in the wrong place. Sort each one before you word it:

  • Always on is for what most turns need. The premise of the world and how the GM narrates are good always-on instructions. Ask of each one: would this apply on most turns of a game? Unless a game is nearly all combat, its combat rules don't belong here.
  • Situational is for a moment: "when X, do Y". These are some of the strongest instructions you can write, because the GM gets one exactly when its moment comes, right beside the player's move.
  • A procedure is the rough shape of something that takes several turns. The framework for running a fight is a good one. Use a procedure when steps happen in a general order, when some of it needs the GM's judgment, or when the GM has to wait for the player between steps. A step can name a script to run ("once the player picks a target, run the attack script"). That is supported and often useful, but a procedure doesn't need scripts.
  • A script is for anything exact. Whatever changes the game's state in a single turn, and any bookkeeping or logic with more than a step or two, belongs in a script, not in an instruction. Don't try to put everything into instructions.

Don't ask too much of every turn

An instruction that makes the GM read, check or audit on every turn makes it slow, costly and stiff. The pattern to look for: "On every turn you must check these five fields on every character in the scene, narrate exactly as they say, then check your reply against this list."

  • Narration instructions are about style and pacing. How the world sounds, how long a reply runs, when to cut a scene.
  • Bookkeeping instructions are about keeping the game's state in step with the story. What to record when something happens, not a checklist to run through each turn.
  • Reading is for when it's needed. A rule that tells the GM to load a file or another set of rules before every reply spends a step and its attention before the story starts. Put the few lines that matter in the rule itself, and let the GM look the rest up.

What a good instruction looks like

  • It does one job. One rule, one moment. A rule that covers combat, prices and how NPCs talk is three rules, and the GM follows none of them well.
  • It is the right kind, as above: always on only if most turns need it, situational for a moment, a procedure for steps over several turns, a script for anything exact.
  • It says what to do. The GM can act on "Keep replies to two short paragraphs". It has to guess at "Don't be wordy".
  • It is written once, plainly. No capitals, no "IMPORTANT". A rule shouted is followed too hard, and it makes the quiet rules beside it weaker.
  • It names real things. Every stat, condition, item and file it mentions exists in the world, under that exact name.
  • It gives the GM a number or an outcome, not a mood. "A failed roll costs 1 Stress" plays. "Failure should feel meaningful" doesn't.
  • It is short. If a rule needs a page, it is a procedure, or it is reference material that belongs in a file the GM looks up.
  • It is about this world. How Craft works (memory, sheets, maps, tools) is the GM's own business. A world's instructions say how this world plays.

Weak and better

Weak Why it fails Better
"IMPORTANT: NEVER let the player succeed too easily!!" Shouted, vague, and the GM overdoes it everywhere "A roll is called for when failure would change the scene. Don't ask for one otherwise."
"Remember everything the player does and keep the story consistent." The GM already keeps its own memory Delete it
"When Corruption reaches 10, the character turns." (situational) A trigger can't see a number on a sheet Put the threshold in the rule that raises Corruption: "…at 10 the character turns."
"Track the party's Heat from 0 to 6." A rule puts nothing on screen and holds no number A tracker named Heat, with this as its rules
"Combat: roll initiative, then each side acts, attackers roll 2d6 + Might against Guard, damage is weapon + margin, at 0 Health…" (always on) A whole fight, read on every turn of every scene A procedure for the fight, and a script for the attack roll
"After every purchase subtract the gold and update the inventory." The GM records changes as it narrates them Delete it
"Before every reply, read the Style Guide file, then check your reply against its banned list." (always on) A file read and a self-audit on every turn of every game Put the three lines that matter in the rule; keep the file for when a scene's prose goes wrong (changing how the GM writes)
"Roll 1d6 on the table: 1–2 bandits, 3–4 a storm, 5 a merchant, 6 nothing, then subtract a day of supplies." Exact steps and bookkeeping the GM has to work through by hand A script that rolls, picks and records, named by a short rule for its moment
"Use AC for defense." (the sheet says Guard) The name matches no field "Attacks are rolled against the target's Guard."
"Be dark, gritty, immersive and cinematic, with rich descriptions." A pile of adjectives the GM applies to everything "The tone is bleak and practical. People are tired, things are worn, and help costs something."
The same rule in an always-on instruction and in a player option's choice Two copies drift apart and can contradict a pick Keep it only in the option's choices

Wording

  • Say what to do, not only what not to do.
  • Name the style. A phrase the GM already knows brings a whole way of writing with it: "Write in purple prose", "Narrate like a hardboiled noir novel", "Write like an expert fantasy author". One such line does more than a list of rules that tries to describe the same style, and takes a fraction of the room.
  • Keep lists of small prose rules out of always on. "No em dashes", "No similes", "Never open with the weather": each is small, but the GM holds every one of them in mind on every turn, beside the story. A dozen pull against each other and against the style you named, and the GM follows all of them less well. Keep the two or three that matter most, and move the rest to prose rules.
  • Write each rule plainly, once. Emphasis on one rule weakens the rest, and a rule written twice drifts into two.
  • Few examples, and varied. The GM copies examples closely. Give two or three different ones, or describe the pattern.
  • Use the sheets' field names. If the sheet says Defense, never AC in one rule and Armor in another.
  • Write to the GM as "you", in full sentences. Notes to yourself ("combat - fast, deadly") leave the GM to fill in the rest.
  • Watch for over-correction. A rule written to fix one bad turn ("Don't let the player win easily") makes the GM overdo it everywhere.

How much is too much

  • Always on. Craft's defaults take about 2,200 of the 10,000 characters allowed. Aim to keep the world's own always-on text under about 3,900. A world near the limit almost always has rules for single moments in it.
  • One always-on instruction rarely needs more than a short paragraph. Past that, look for the part that is about one moment and move it out.
  • Situational instructions are cheap: the GM only sees the few whose moment has come. Many short ones are better than a few long ones.
  • Procedures cost a line each in the GM's list, and their text only when used. Keep the list short enough to choose from by title (see procedures).

Instructions to delete

These tell the GM to do what it already does, and they make it worse at it. Take them out:

  • memory: logs, "remember", "re-read X every turn", "keep file X in mind";
  • bookkeeping: "update the sheet", "subtract the gold", lists of fields to change;
  • the map: moving tokens, pinning new places;
  • rolls: "wait for the player to roll";
  • output: headings, JSON blocks, lists of choices, how to format speech;
  • thinking aloud: "think step by step", out-of-character reasoning;
  • forced reading: "read every file before you reply", "open X at the start of each turn";
  • copies of Craft's defaults (see Craft's defaults).

Naming a tool is fine. A rule can tell the GM to run a script, or to use one of its own tools, as long as it is a script the world has or a tool the GM has now. A rule that names one that doesn't exist sends the GM looking for nothing.

A test for any instruction

Ask these of each one. A "no" is something to fix.

  1. Could the GM act on it this turn, without guessing what you meant?
  2. Would it apply on most turns? If not, is it situational, with a trigger a story moment can show?
  3. Does everything it names exist in the world, under that name?
  4. Is it the only place this rule is written?
  5. If it were deleted, would play get worse?
  6. Does it make the GM read or check something on every turn? If so, can the rule carry what matters itself?
  7. Is it exact steps or bookkeeping? Then it is a script.