How an audit works
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.
There are three audits of how well a world is set up for the GM, each about one area: the instruction audit, the map audit and the file type audit. Each is run on its own and has its own checks. A creator who wants more than one runs them one after another. This page is the method they share.
An audit is a report. It changes nothing. Not a file, not a rule, not a setting. It ends by recommending where to start, and a fix starts only after the creator says which to make.
1. Run the world check
Craft measures a world in code, over every file, in one step. Start there: the numbers are exact and they tell you where to read.
The report gives you:
- Findings and numbers for instructions, maps and file types.
- Features in use: how much of the world uses each of Craft's features, such as how many maps have a scale or an exit.
- The parts: every GM instruction in full, split into readable parts. A long part is split into numbered ones.
- The samples: the files worth opening, picked by code.
Use only what belongs to the audit you are running. Each audit names its findings, numbers, parts and samples.
2. Read it yourself
An audit has no readers to hand work to. What it reads depends on itself: a rule on the script it names, a sheet on the rules that read it. So you read everything the audit names, whole, before judging any of it, and you keep it all in view while you judge.
Each audit says what to read and in what order.
3. Cross-check
Before writing:
Join findings that are one problem.
Look across what you read. A rule that names a field the sheets don't have shows only when the two are side by side.
Check what you would lead with. Read the rule or file behind each of your top findings again before you write it.
Settle what you couldn't confirm. For a script you didn't find or a field you didn't look up, list the folder or search for the name. Then report it as a fact, or drop it. Never hand the creator a "check whether".
Say whose numbers they are. The check counts the world's own rules and its options' instructions, a default of Craft's it reworded among them. The parts also hold Craft's untouched defaults, so a part can hold more than the check's number. Give the check's.
Drop what has no quote.
Take numbers from the check, not from your own sums.
Rules that hand off to each other aren't duplicates. A procedure that says "starting a fight has its own rule" and a rule that says "run the rest by the procedure" are one design in parts.
Size a fix to what you found. Never propose deleting a rule because another covers the same moment until you have read both and the second holds everything the first says.
If the creator named a turn that went wrong, look at what the GM was handed on that turn and find which text led it there (seeing what the GM sees).
4. Report
The written report is what the creator asked for. Write it out in full in your reply, in plain words. Lead with what goes wrong, not with numbers: give a number only where it shows how big a problem is.
What you looked at, and how it stands. A sentence on what you read ("all 129 rules, the 2 procedures, the 19 trackers and the 25 scripts"), then a short overall assessment: is the world in good shape for the GM, and what holds it back most.
The issues, grouped by priority. Under High, Medium and Low, leaving out a group with nothing in it.
- High: the GM gets play wrong now. An issue is High only if you can name the moment in play, what the GM does wrong there, and quote what causes it: two rules that disagree (quote both), a number the sheet works out wrong, a rule that waits on a script or a file the world doesn't have. A name that points at nothing is Medium when the same rule also says what to do.
- Medium: the GM is slower or less reliable than it should be.
- Low: tidying that helps a little. Two places that say the same thing and agree are Low.
For each issue: a short heading that says it plainly; what is wrong, in a sentence or two, with one example quoted; what it does in play; and the fix, saying what to change, with the guide for it.
Where to start. Recommend the fix to make first, usually the top high-priority one, and say why in a sentence. When there are issues, end on an offer: "Would you like me to help you fix the fight start first?"
Leave out what is good, what you didn't check, a list of features and a section of numbers. Size is not an issue while it is within its limit: a rule, procedure or script that is long, or close to its limit, is fine. Only going over a limit is. A feature the world isn't using belongs in the report only as the fix for an issue you found.
Quote what you criticize, and say what you would write instead. Keep the creator's rules in the creator's words: a fix moves their sentences, it doesn't rewrite them.
5. Fix what the creator picks
The report ends with your recommendation; a fix starts only when the creator says which. Each kind of fix has its guide:
- instructions: refactoring GM instructions;
- the character type and other types: improving file types;
- tokens: putting characters on maps;
- many files at once: bulk work.
Do one at a time, and run the world check again afterwards to show the numbers before and after. New games get the changes from the next published version, and a game under way when its owner syncs.