Project settings
A project is a world or a system you build in Craft. Most of it is files, but some things belong to the whole project: its name and tags, the page people see before they play, the art direction every picture follows, the GM's name (the Game Master's), portrait and voice, and a few pointers into the rest of the world (the root map, the prelude, the handbooks). These live together in one settings document. Set them early: the art direction and the Game Master shape everything built after them, and the project page is what a stranger judges the world by.
How it is used
- Players see the project page (cover, headline, body, gallery, tags) on Discover and before they start a game.
- Every image generated for the project has the art direction added to its prompt, whoever makes it: a person in the app, an agent, or the GM during play.
- A game copies the settings when it starts, from the project's latest published version (or from the live project if it has none). Changing a setting later reaches new games once a new version is published. A game already running keeps its copy until its owner pulls the update.
- Discover groups and filters projects by their tags.
- People who start a world get a First Steps checklist the first time they open it: the one its system wrote, or a default list.
Some keys in the settings document belong to other features. Each is covered there:
gameOptions, the rules the GM runs the world by: GM instructions.preludeFlow, the cinematic opening played before the lobby: Flows.playerHandbookandbuilderManual: Handbooks.rootMapFileReferenceId, the world's front-door map: Maps.- Visibility and cloning, which decide who can see and copy the project: Publishing.
Changing settings
Every key is listed, with its type and limits, in the settings reference.
Most settings are in the project's Settings: Project (cover, icon, name, description, attribution, visibility, cloning), Image Generation, Game Master (its own place in the workspace) and First Steps. The headline, body, author's notes and gallery are edited on the project's home page: click Edit. The app has no tag picker: ask Orbit to set tags.
Art direction
The art direction (settings.imageStyleInstructions) is one short paragraph on how
the world looks: medium, palette, light, mood, rendering style. Craft adds
it to every image generated for the project, so you write each prompt as
the subject only.
Muted watercolor with ink outlines; cold northern light, weathered
surfaces, desaturated greens and greys. No photorealism, no text.
- Set it before the first picture, so the art matches from the start.
- Say what the images should look like, not what they show. "A cold, muted palette" belongs here; "a dragon over the city" belongs in a prompt.
- Keep it to a few sentences. It is added to every prompt, and text past 5,000 characters is cut.
- A file type can add its own style on top, for what its pictures show, such as plain backgrounds for item icons. How the two work together: setting a world's image style.
The Game Master
The gm setting gives the Game Master a name, a portrait and a narration
voice. Leave the name and portrait empty for a faceless narrator. How the
GM runs the game is not set here: that is its instructions
(GM instructions). gmToolSettings turns optional
GM tools on and off, such as the dice roller and multiple-choice questions.
The project page
The page people see first is made of the cover image (image), the
headline and its headlineLabel, the body, the author's notes, the
rules system's name, the tags and the gallery ("Glimpses").
- The headline is the hook. One or two lines that make someone want to play: a place, a conflict, a promise.
- The body is a short pitch, in Markdown: what the world is, who the player is, what play feels like. Long rules belong in the handbooks.
- Tags come from Craft's tag list, at most 3. Pick what someone would filter by: a genre, a tone, a kind of play. Anything else is dropped. When you publish, Craft also tags the world from the same list so Discover can find it (Publishing).
- The gallery shows a few of the world's best pictures. Its items, layouts and rules are in the gallery reference.
First Steps
First Steps is the checklist that greets someone the first time they open
a world they started. A system's author writes it (in firstSteps) for the
worlds built on the system. A world whose system wrote none, or one started
from scratch, gets a default list: add cover art, create a character and a
location or map (when the world has those file types), read the Builder's
Manual if there is one, and ask Orbit. The system's own workspace always
shows a fixed list of its own.
Each step is either an action (a button that opens something) or an info note. Steps point at things by names that survive copying, never by ids: a file type's slug, a folder path, a file name, a handbook chapter's id. The shape and the action types are in the settings reference.
Working with others
A project has one owner. The owner can invite up to 4 editors to build it with them, pending invites included. Editors work on the same live project, not a copy: what one changes, the others see.
Inviting. The owner invites by Craft username, in the Editors tab of the Share button at the top right of the workspace. The person gets a notification with Accept and Decline, and the owner is told when they accept. Until then the invite shows as pending, and the owner can revoke it. An accepted project shows in the editor's projects, under Shared with me. One account can send 50 invites in 24 hours (Limits). When someone accepts a project that is already full, the invite stays pending until a place opens.
What editors can do. Editors create and change files, file types and folders, generate images, upload to the gallery, import a zip, install, update and uninstall packages, and change the project's settings: the art direction, the Game Master and the GM instructions among them. The Editors tab shows who is in the workspace now and which file each has open.
What only the owner can do:
- Invite, revoke invites and remove editors.
- Change visibility, cloning and the project type. In the app, the Project tab of Settings is the owner's alone.
- Create versions, and restore, promote or delete them (Versions). Push a game's changes back into the project.
- Create and edit packages (Packages).
- Export the project (Import and export).
- Move the project to the trash.
Leaving. The owner removes an editor with the remove button beside their name. An editor leaves with Leave on their own row. The owner can't leave their own project.
Who pays. Each person pays for their own work: the images an editor generates and their Orbit messages come from the editor's own energy or credits, not the owner's. Creator earnings go to the owner (Energy and credits).
Doing it well
- Set the art direction and the Game Master first. Both shape everything made after them, and changing the art direction late leaves earlier pictures in the old style.
- Write the page last. Once the world exists, the headline, body and gallery can show what is really there.
- Edit only the keys you mean to change. The handbooks, the prelude and the GM instructions are long work someone wrote by hand, kept in the same document.
- Leave the theme alone. Colors and fonts are made in the app's theme editor.
- Curate, don't fill. A few strong, captioned gallery items beat twelve similar ones. Pick a layout that fits how many you have.
Mistakes
- A style phrase copied into every prompt instead of stored once as the art direction. The next picture made elsewhere won't match.
- A gallery URL that was never generated or uploaded. It saves, and shows as a broken tile on the project's front page.
- A tag that isn't on the list. It is dropped, often without a word.
- Rules prose in the body. The project page is a pitch; long rules go in the Player's Handbook.
- Expecting running games to change. A game keeps the settings it started with.
Reference
- The project gallery: The Glimpses showcase on the project page, its item fields and its four layouts.
- Project settings reference: Every key of the project settings document, with its type, limits and what it does.