Upgrading from the original GM
Every other doc describes Craft's current Game Master, GM Harness 2 (V2). This one is for worlds and games made before it. They run on the original GM (GM Harness 1, or V1) until they are upgraded, and the upgrade goes one way.
What the upgrade changes
The original GM read its rules from instruction files, and a world built its own memory and trackers out of files. The current GM keeps those itself, so an upgraded world stops building them:
| Before (V1) | After (V2) | |
|---|---|---|
| Rules | GM instruction files, each with a trigger | The world's GM instructions, plus player options |
| Memory | Whatever the world built: logs, state files, memory fields | Built in |
| What changes in play | Tracker files the GM was told to update | Trackers in the game's current state |
| Who is where | Tokens the GM moved on the map | The current state: the scene, who is in it and where |
| File visibility | Pinned, partial, searchable or hidden | Visible or hidden (pinned and partial count as visible) |
| The first turn | An opening instruction file | The game start's opening current state and opening notes |
| Exact procedures | Instructions the GM carried out step by step | Scripts the GM runs |
After the upgrade the GM never reads the old instruction files. Before it, the original GM never reads GM instructions. Writing to the wrong one changes nothing in play.
Who gets the upgrade, and when
- A world has one engine. You can see it in the world's Settings › Game Master. A world copied from another, built on a system, or imported keeps the engine of its source.
- New games take the engine of the version they start from: the latest published version, or the live world before its first publish. So players get GM Harness 2 only once a version on it is published. Until then, a world that switched its draft still starts V1 games.
- A game keeps its engine, with one exception: a V1 game can move to GM Harness 2 once, when its owner takes the world's V2 update or upgrades the game with AI. A game never moves back.
- Going back means restoring a version of the world saved on the original GM. Nothing else switches a world back.
A world on the original GM shows an Upgrade banner at the top of its workspace.
The steps, what happens to games in progress and how to go back are in Moving to GM Harness 2.
Doing it well
- Save a version first. A version saved on the original GM is the way back, engine and files included.
- Translate everything, then trim by play. An upgrade carries over every rule about the world, its mechanics and its tone, and leaves out only what the current GM does itself and copies of Craft's defaults. When you edit by hand afterwards, remove what play shows the GM handles on its own.
- Move exact steps into scripts. Math, rolls and bookkeeping that run the same way every time are more reliable as a script than as instructions.
- Point the GM at files it needs. A rule file that used to be pinned is no longer in every prompt. If the GM needs a rule every turn, write it as a short always-on instruction. For a file it misses at the right moment, a situational instruction can name it.
- Hide old bookkeeping files, don't delete them. Games still on the original GM read them, and a hidden file can be shown again.
- Test before you publish, and recommend a fresh game: a game moved from the original GM doesn't play as well as one started on GM Harness 2.
Mistakes
- Writing instruction files after the upgrade. The GM never reads them. Put the rule in the world's GM instructions.
- Writing GM instructions on a V1 world. The original GM ignores them, and the app's translation replaces them whole when it is applied.
- Expecting players to have GM Harness 2 after the switch. New games take the engine of the latest published version. Publish a version on GM Harness 2.
- Deleting old instruction, tracker or memory files. Games still on the original GM read them, and a game that syncs a newer version can lose a file deleted from the world. Hide them instead.
- Leaving tracker or memory files visible. They make the current GM worse: it has written changes into them instead of the sheets they belonged on. Use trackers.
- Leaving the opening in the opening instruction file. The current GM never reads it. Move it to the game start's opening current state and opening notes (see Game starts).
Reference
- Moving to GM Harness 2: How a world built for the original GM moves to GM Harness 2 (saving a way back, translating its instruction files, cleaning up, publishing), what happens to games in progress, and how a game moves on its own.