Craft

Craft feature audit

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.

Craft keeps adding features, and a world built a while ago doesn't use the ones that came after it. This audit says which of Craft's recommended features a world uses and which it doesn't, and for each one it skips, why the creator might want it. It also names anything still built the old way. It reports and changes nothing until the creator picks what to add.

It asks one question: does the world use what Craft offers? Whether the parts it has play well is a different question, with its own audits: instructions, maps and file types.

1. Run the world check

Craft checks a world in code and returns a report. It reads every file, so its counts are exact, and it takes one step.

2. The features

Feature What it gives the GM Guide
Map scales Distance and travel time, and which maps are scenes and which are for travel Maps
Exits How to leave a map and where the party comes out Exits
Grids Each person's square on a scene map, and who is in reach Grids
Tokens Who is in a place when the party arrives Putting characters on maps
Linked locations What is inside or next to what, without drawing it on a map Linked locations
Root map The map games open on and travel from Maps
Complete game starts An opening that begins in a scene, with the people and notes it needs Game starts
Situational instructions A rule handed over only when its moment comes Triggers
Procedures The shape of something that takes several turns Procedures
Trackers A count or clock the GM keeps and the player sees Trackers
Player options Choices the player makes, such as difficulty or tone GM instructions
Scripts Exact rolls, tables and bookkeeping done the same way every time Scripts
Art direction One look for every picture the world makes Art direction

A feature counts as used when most of what could use it does. One used on fewer than half of what could use it, or on none, is not used yet. A count with no total (scripts, procedures) is used when it is above zero.

Before calling a feature worth adding, check that the world has something it fits. A world with one map doesn't need linked locations, and places already joined by exits on their maps don't need a link as well: suggest links for the places no exit reaches. A world with no fights or counts doesn't need trackers. Leave out what doesn't fit, and say nothing about it.

3. Report

Write it for the creator, in plain words. Name features as Craft names them, and the world's own places, rules and characters by their names.

  1. One line on where the world stands. "Your world uses 9 of the 13 features Craft recommends."
  2. What you're using. One short line each, with how much where it helps: "Exits: 8 of your 9 maps".
  3. What you're not using yet. For each: what it is in a sentence, why it would help this world, with one example from the world ("the cellar under the Rusty Tankard could be linked to the inn, so the GM knows how to get there"), and roughly what adding it takes. Most useful first.
  4. Built the old way. Only when upToDate lists something: one line each, what it is and what it costs in play. Leave the section out otherwise.
  5. An offer. End on the one you'd add first: "Would you like me to set up linked locations for the cave first?" When nothing is worth adding, offer the first fix from what is built the old way instead.

4. Add what the creator picks

Change nothing from the report alone. When the creator picks a feature, follow its guide from the first step, one feature at a time. When they pick something built the old way, follow the guide its upToDate entry names; an upgrade to the current GM (upgrading) comes before anything else. Run the world check again afterwards and say what changed.

New games get the changes from the next published version, and a game under way when its owner syncs.