Building a world
This guide is about the whole job: what "done" means when you build a world, a game system or a playable game in Craft, the order that keeps the work from being redone, and a checklist for the end. Each feature has its own doc with the details. This one says how they fit together.
Decide what you are building
What was asked for decides when the work is finished. There are three common outcomes:
- A world or setting. Characters, places, factions, items and lore that link to each other and make situations worth playing. It can work with any rules.
- A game system. How actions are resolved, the file types that model its concepts, layouts that make them usable in play, GM instructions that apply them, and a few example files that show the pieces working together. See designing a game system.
- A playable game. A world and a system put together for one experience: a game start, characters to play or a way to make one, GM instructions, and a place for everything that changes in play.
The rest of this guide describes the full playable game, the usual target for a big build. A lore wiki, a setting bible or a rules reference is finished when it is what was asked for. Leaving out pictures, maps or a game start on purpose is a choice, not a gap.
From a document
When the creator hands over written material (lore, a setting bible, house rules), every section and every named person, place and rule in it is part of the ask. Keep each fact as written: names, titles, who leads what, numbers and ranges. Afterwards, search for the document's names and phrases to check each one landed, and list in the reply any part that didn't become a file or a rule (a section of everyday life, say), so the creator can ask for it.
Start from play
Craft games look and feel like visual novels and play with the freedom of a tabletop RPG. Before you choose folders or fields, name the moments players will have again and again: what they see, choose, roll, discover and change. Build toward those moments:
- people and places worth presenting, with pictures;
- rules clear enough for the GM to rule on the spot;
- state the GM can update as the story changes the world.
A large archive of lore is not a good game by itself. Every part should serve something a player does.
The order of work
Build in this order. Each step leans on the ones before it.
- The project's settings. The art direction, so every picture matches, and the Game Master's name and voice (project settings).
- The file types. The kinds of things in the world, their fields, and the references between them (file types, references and computed fields). A few well-designed types beat many thin ones.
- A few example files of each type, written to the full standard below. They become the model for the rest, and they show early whether the schema works.
- The rest of the files, things other files point at first (classes, items, factions, places), then the people, then the files that tie them together. For many files, plan once and let Orbit hand them to its subagents (see bulk work).
- The rules. GM instructions for how the GM runs the world, trackers for what the story keeps count of, and scripts for procedures that must come out exactly the same every time.
- The places. Maps where moving around matters, and linked locations for how places connect.
- The way in. At least one game start, the characters on offer, and for a campaign, character creation and a prelude (flows).
- The pictures. The cover first, then the files players meet most (images).
- The project page, last, once there is something to show. Then publish a version: once a world has one, new games start from the latest published version, not the draft (publishing).
What a finished file has
A file that saves is not yet finished. Each important file should have:
- A real description. What a player sees or feels, in the world's voice. Two to five specific sentences beat one generic line: "A reliable ranged weapon" is a placeholder.
- The GM's truth, where the schema has room for it (notes, background, secrets): the hidden fact, the hook or the complication that makes the thing playable, not only describable. The best files interlock: a person's secret points at a place's rumor, which points at an item's history.
- Links. Records point at each other through reference fields, and prose names files with mentions (links and mentions). If no field fits, add a reference field to the type. A world where nothing points at anything is a list, not a world. A place inside another (a saloon in its town) is linked as part of it (linked locations), not only said in its notes.
- The values the rules use. Stats and skills that rules and computed fields read are set on every file; when you leave some empty, say which.
- Numbers that mean something. If one sword is worth 5 and another 90, the text should say why.
- Names players will say. The GM finds people and places by name. If
a character goes by a nickname, put it in the file's name
(Jim "Crash" Gifford), or in an
aliasesornicknamefield marked as a key field, so the GM can connect it to the right file.
Mechanics need rules and a home
A mechanic is reliable only when the world says how it works and where its state lives. For each one, decide:
- The rule: when it applies and what the GM does, in a GM instruction.
- The state: where its current value lives. A value that belongs to one person or thing is a field on that file. A count that belongs to no one sheet (Heat, supplies, standing with a faction) is a tracker.
- The view: how players see and change it, in the type's layout or the tracker.
- The procedure, if it has exact steps (damage, crafting, a level up): a script, so the GM calls it instead of working it out. For XP, levels and level-ups, see designing progression.
For a whole rules system, the order to design it in and where each part lives, see designing a game system.
The GM keeps the game's memory, the scene, who is where, the time, turn order and the party's objectives itself. Don't build files or rules for those.
Making it playable
A world is ready for players when:
- The rules are where the GM reads them: the world's GM instructions.
- At least one game start is complete: a starting location, the characters on offer and an opening in the world's voice, all linked to real files. It also sets who is in the scene, its purpose and first objective, and the opening notes (game starts).
- The characters on offer are finished records, not stubs. Players read their cards before choosing. Which characters can be picked is set on each game start.
- The Game Master has a name and a voice that suit the world.
- A campaign lets players make their own character, with a creation flow on the character type, and can open with a short prelude (flows).
- Files the GM must never read are hidden: author's notes, planning documents, anything out of the game (visibility).
Pictures and maps
When the world should look finished, it needs pictures. Every file's picture is its face on cards, in play and on the project page.
- Store the art direction before the first picture, and write each prompt as the subject only. The style is added for you. A type that needs its own look (portraits, item icons) can add its own style (images).
- Build each prompt from the file's own description.
- Give pictures in this order: the project cover, then main characters, signature places and anything that sets the tone. Ten kinds of arrow can go without.
- Say how many pictures you plan before a batch: each one costs energy.
When moving around matters, the world needs maps: a root map with a picture, its important places drawn and linked to their files, and a real scale (maps). Places the party moves between should be joined, by exits on a map or by linked locations where no map draws them, so the GM knows what is inside what and how to get from one to the next.
Cleaning up
Leftovers hurt a world's credibility, and the GM can find and use any visible file.
A world made from scratch starts with these example files:
Characters: "Example Character"
Locations: "Example Location"
Equipment: "Longbow", "Leather Armor", "Explorer's Pack", "Quiver of Arrows"
Game Starts: "Tavern Start"
Starter types. The Character type starts with D&D-style ability scores and Equipment with D&D gear. In any other game, reshape them to the world's own stats and gear rather than building on them, and keep the parts that still fit (a character's inventory).
Starter files. Rewrite each one into real content, or delete it once real files do its job. The starter game start's opening is template filler.
:::orbit When real files replace a starter file (an example pirate, the tavern start), offer in that turn to delete it and any folder left empty. :::
Scratch files. Delete every test and experiment ("Test Ritual", "asdf", "Repro Note").
Final checklist
- Every important file has a real description, the GM's truth and at least one link where it makes sense.
- Every mechanic has a rule, a home for its state, a way for players to see it, and a script where its steps are exact.
- The rules are written where the GM reads them, and refer to the real world, not template text.
- For a world meant to be played now, one game start is complete, with finished characters on offer (or none, when players make their own) and an opening in the world's voice.
- The Game Master has a name and voice. A creation flow is the guided way to make a character; without one, players fill in the sheet's form.
- The project page is dressed: cover, tags, headline, body and a gallery of the best art, with the art direction stored.
- The key files have pictures, if art was wanted.
- If moving around matters, the root map exists and the places the party travels between are joined.
- No scratch files are left, and starter files are reworked or removed.
- A version is published, so new games get the finished world.
To check the world for contradictions and rules that disagree, see auditing a world.
A world you start opens with a First Steps checklist for its first moves. When the world is ready, click Create Version at the top right of the workspace so new games get it.
Mistakes
- Building two hundred files before checking three. A schema problem found late means redoing everything. Finish a few examples first.
- A lore archive when a game was asked for. Content with no game start, rules or state is a wiki.
- Template text left in. "Tavern Start", "Welcome to the game" and example characters mark a world as unfinished.
- A style phrase pasted into every prompt instead of stored once as the art direction. The next picture made elsewhere won't match.
- Files for what the GM does itself. Session logs, memory files and a "campaign state" file fight the GM's own memory and scene.
- A rule with nowhere to keep its state, or state no rule ever updates. Either one is only documentation.
- Forgetting to publish. Once a world has a published version, new games start from the latest one, not from your draft.