Refactoring GM instructions
Note
Written for AI agents. Orbit and coding agents follow this page when they work on your world. You don't need it to use Craft, but it shows how an agent will approach the job.
GM instructions go wrong in the same few ways as a world grows: everything ends up always on, rules for one moment crowd every turn, counts are written as rules, and old rules stay that tell the GM to do what it already does. A refactor moves each rule to the place the GM reads it best. It does not rewrite the creator's rules: their sentences, numbers and names move, whole. This guide is for a world or game.
What each kind of instruction is, how to word one and the limits are in GM instructions. Read it with this guide.
1. Read all of it
- The whole value, the world's own instructions, player options and what it changed of Craft's defaults.
- Craft's defaults as they stand, so you can tell a rule that repeats one (Craft's defaults).
- The sizes against the limits: the always-on text, the number of procedures, the largest game (limits).
- What the rules name: the stats, conditions, dice and files they mention, to check against the world in step 3.
2. Sort every instruction
Go through them one at a time and give each one home:
| When an instruction is | It becomes |
|---|---|
| Needed on nearly every turn: the premise, the voice, the core roll, the few rules no turn may break | Always on, as it is |
| Always on, but about one moment (a fight, a purchase, a death, a journey) | Situational, with a trigger the story can show |
| Always on, with one every-turn sentence and the rest about a moment | Split: the sentence stays, the rest becomes situational |
| Several steps to run a longer moment | A procedure |
| Exact math, rolls or bookkeeping that run the same way every time | A script the GM calls |
| A count the player should watch ("track Heat from 0 to 6") | A tracker, with the rule as its text |
| A switch between ways of playing ("in hard mode…") | A player option, the world's usual way as its default |
| A rule that argues with a player option ("keep replies short") | Moved into that option's choices |
| A table or list to look things up in (spells, prices) | A file, named by a short situational rule for its moment |
| Something the GM does itself: memory, updating sheets, moving tokens, waiting for rolls, output formats, tool steps | Removed (mistakes) |
| A copy of one of Craft's defaults | Removed; or, if it differs on purpose, a reworded default |
| Two instructions about one moment | One |
When in doubt between always on and situational, situational.
3. Check each one that stays
- Triggers. Each situational instruction names one moment the story can show, never a number on a sheet, with the ruling first (triggers).
- Names. Every stat, condition and resource a rule tests exists in the world under that name, and the rules use the sheets' field names.
- The dice. One always-on instruction names the core roll, and no rule mentions dice the world doesn't use (dice).
- Rules that disagree with each other, with a rule file or with the handbook. Report them; don't pick a winner.
- Wording (writing good instructions): plain, once, no capitals for emphasis. Leave wording alone unless it is the problem.
4. Show the plan before changing anything
A refactor touches every rule the creator wrote, so they see it first:
- one line per instruction: what it is now, what it becomes, and why;
- the always-on size before and after;
- everything you would remove, quoted, with the reason;
- every disagreement and every name that matches nothing, as questions.
Ask before removing a rule's content or merging two rules whose wording differs. Moving a rule whole needs no question.
5. Make the changes
- Move sentences; don't rewrite them. A split rule keeps the creator's words in both halves. Add nothing they didn't say: an addition is an offer.
- Never change a key. Option, choice and tracker keys are what games under way point at. Change labels and text only.
- Change Craft's defaults in place rather than writing a second rule beside one.
- Keep the sections' order unless the creator asked for a new one.
- When a save is refused, fix what it names. Never shorten or drop another rule to make room without asking.
6. Test and hand over
- Read what the GM now gets on every turn, and check a few moves against the situational rules (testing a change).
- Report what moved where, what was removed, the always-on size before and after, and what you left for the creator to decide.
- Say how it reaches games. New games get a world's change from the next published version; a game under way gets it when its owner syncs (in a game).