Craft

Starting a world

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.

This guide takes a new project to a first playable world: a premise, a character sheet that fits it, a handful of places and people that point at each other, rules the GM can run, and a game start that opens in a scene. It uses Craft's features as it goes, so the world doesn't need an audit to catch up later. For what "finished" means in a big build, and for expanding a world that already exists, see building a world.

1. See what you are starting from

Read before you ask anything. The project is one of three:

  • Blank. Only Craft's starter files: the Character type with D&D-style stats, Equipment, an example place and the Tavern Start game start (- Characters: "Example Character"
  • Locations: "Example Location"
  • Equipment: "Longbow", "Leather Armor", "Explorer's Pack", "Quiver of Arrows"
  • Game Starts: "Tavern Start"). You build everything, starting from the rules.
  • From a game system. The project has a game system's name, and its types and files came with it: classes, abilities, items, creatures, rules, often a character creation flow. The rules are done. You build a setting on top: places, people, a premise and a game start. Don't reshape the system's types or rewrite its rules unless the creator asks.
  • Already built. The world has places, people or rules of its own beyond what it started with, or a game start that isn't the starter's. Stop here: this guide would build over the creator's work. Say in two lines what the world already has, and offer what fits instead: a Craft feature audit for what it isn't using yet, an audit of its instructions, maps or file types, or adding the one thing they asked for.

2. Agree the premise

Ask once, and only what changes what you build. At most three questions, each with the answer you recommend, so "go with your recommendations" is a full reply:

  • The premise. Where it is set, what the story is about, an original world or one based on a book or game.
  • How it plays. Light and story-led, or rules-heavy with numbers on the sheet. A world from a game system already answers this.
  • What players play. Characters you make for them to pick, or their own through a creation flow.

The creator's message may answer some of these: don't ask those again, and when it answers all of them, go straight to the plan. "Go with your recommendations" accepts every recommendation you made, the stat names you suggested included: that is the creator naming them, so plan with them and don't ask again.

3. Agree the plan

Before you build anything, write the plan and wait for the creator to agree to it. It shows them what you understood and what will change in their world, while changing it is still free. Write it in plain words, in this order:

  • What you heard: their request and their answers, in a sentence or two.
  • What the world has now: what you found in step 1, with counts ("only Craft's starter files", or "the system's 12 classes, 340 items and its character creation flow").
  • The opening: one idea for the game start, in two or three sentences: where the players begin, what is happening there, and what pulls them in. Plan everything else from it.
  • What you'll make for it, file by file. Name every file and give it a line on what it is and why the opening needs it: "three nearby places" or "four to eight people" is not a plan, "Wyrm's Rest, the inn where the party meets the courier" is. Decide the number; don't give a range.
    • the places: the root map (a town, a city, a region or the whole world, whichever holds the opening), where the players begin, and the three to six places the first sessions lead to, with which connect to which;
    • the people: four to eight, those met at the start and those the opening points toward, each with the place they are in;
    • the characters players pick, by name and in a line each, or the creation flow;
    • the rules, trackers and procedures the opening's play needs, each with the moment it is for ("a Suspicion tracker for the smuggling plot").
  • What you'll change: each thing already there that you'll replace, rename or remove, such as the starter Character type's stats or the Tavern Start.
  • What you'll leave out, and why, when the premise doesn't need a feature.
  • The art direction: the image style you'll set, in a line or two (medium, palette, light, mood), in the creator's words where they gave them, and otherwise drawn from the premise: a world based on a book, show or game takes its look from that source. Never copy a doc's example (art direction). It is set before any file or picture is made, since every picture follows it, so agree it here, with what each type's own style will say: framing only, such as a headshot for characters or a black background for items. A world from a game system often has the system's look in its types' styles: say which you'll rewrite (setting a world's image style).

End by asking whether to build it. Build when they agree; when they change something, say what changed in a line and build that.

Keep it to what fits

The world this guide builds (a handful of places, people and rules) is a size that can be done well in one go. Some requests aren't, and doing them badly costs the creator more than saying so:

  • Hundreds or thousands of files at once, such as a whole continent of places or a bestiary of every creature in a game.
  • Turning a whole book into a world, such as translating a long rulebook or a PDF into files.

Recommend against these in the plan, plainly, and offer what works instead: build a first slice to play (one region, one chapter, the ten creatures the opening needs), then grow it in batches once it plays well (bulk work).

4. Build in this order

Each step names the Craft feature it uses. Finish a step before the next: later steps link to what earlier ones made. Once the plan is agreed, make steps 1 to 6 in this turn without stopping to ask again. If you must stop early, say which steps are done and which are left.

  1. The project. Its name and description, the art direction agreed in the plan and then each type's style, set before any file or picture (setting a world's image style), the Game Master's name and voice, and the game system's name (project settings).

  2. The rules' core (blank only). How an uncertain action is decided (dice), the character sheet's stats in the world's own terms, and the starter's D&D stats removed. Mark the few fields the GM needs on every turn as key fields (file types). For anything bigger than a core roll and a handful of stats, follow designing a game system.

  3. The places. Build the maps as a tree (scene and travel maps), from the top down:

    • The root map first. One travel map that holds everything the opening uses, sized to the world: a town map (about 1 mi) for a story in one town, a city map (about 4 mi) for one city, a regional map (20 to 200 mi) for a valley, coast or kingdom the party crosses, a world map for a story that spans continents. Make it the world's root map (maps).
    • Every place under it. Each of the three to six places the story uses is pinned (or drawn as an area) on the root map, or on a place pinned there, so every place hangs from the root. A place no picture draws is linked as inside its parent instead (linked locations).
    • The start is a scene. The starting place, and each place a scene opens in, is a scene map with a square grid, nested in the tree: the inn inside the town, the town on the region. Interiors the party goes into are places of their own with scene maps.

    Give every map a real scale (maps), in feet and miles (5 ft squares) unless the user writes in metres, and join places the party moves between with exits (exits) or, where no map draws the way, linked locations.

    :::orbit Set the root map yourself, as soon as its place exists: update /project.json with settings.rootMapFileReferenceId set to the place's handle. Don't leave it to the user. :::

  4. The people. Four to eight people the story needs, each in the place they belong, with the GM's truth (a secret, a want, a lie) that points at another file. Then the characters players pick, finished records, or a creation flow (flows). A system's character type can have a hundred fields: read one of its example characters and fill what that example fills, no more. Put each person's token on their place's map (putting characters on maps).

  5. The rules the GM runs. In the world's GM instructions:

    • the premise and tone, always on;
    • a situational rule for each moment the world plays often (triggers);
    • a procedure for the main thing that takes several turns, such as an investigation, a fight or a heist (procedures);
    • a tracker for each count the story keeps and the player should see: clues found, suspicion, a countdown, supplies (trackers);
    • a player option where players would pick differently, such as difficulty or how dark it gets;
    • a script for each roll or table that must come out the same every time, when the world has scripts (scripts).

    Leave out what doesn't fit the premise, and say so in the reply.

  6. The game start. Replace the Tavern Start with one of the world's own: its starting place, the characters on offer, an opening in the world's voice, the opening current state (who is in the scene, its purpose, the first objective, the trackers' starting values) and opening notes (game starts).

  7. Pictures the files don't have yet, if images are on: the world's cover, the root map, the characters on offer, then the people they meet first (images).

  8. Clean up. Offer to delete each starter file a real one has replaced (cleaning up).

Each file is written to the standard in what a finished file has: a real description, the GM's truth, and links to the files it touches. For more than a handful of files at once, see bulk work.

5. Check before you say it's ready

Run the world check again. Every feature in its features list that fits the premise is used, no starter file is left that you didn't offer to delete, and the game start is complete. Fix what isn't, or say why you left it.

Then tell the creator, in a few lines: what you made, with counts; what you left out on purpose; and what to do next. A world needs a published version before new games start from it (publishing). End on one offer: pictures if there are none, or a test game.

Mistakes

  • Building on the starter stats. Strength and Dexterity in a world that never rolls them.
  • People with nowhere to be. A person who isn't in a place, on a map or in a game start doesn't show up in play.
  • Rules with nowhere to keep their state. A rule that counts clues needs a tracker that holds them.
  • Maps without a scale or a way out. The GM can't measure travel or leave the room.
  • Leaving the Tavern Start. Players see it in the lobby beside the real one.