Craft

Designations

A designation tells Craft that a type's files are people, places, game openings or scripts, and turns on the features built for them. It is not a tag or a category: there are only the values below, and any other is refused. Most types have none. A spell, quest, faction or item type needs no designation, and its name already says what it is.

A world can have more than one type with the same designation, such as a Character type and a Creature type both designated character.

Two designations are fixed types: Craft sets their name, content type and schema, and they have no layout. Some designations keep data beside a file's content, such as a place's map or a game start's opening. That data is not part of the schema, and it is edited with its own feature.

Designations

character

The type's files are people: the characters players pick to play and the people the GM puts in scenes. The type gets a built-in voice field, and the GM looks up its files when a name comes up.

Value "character"
Fixed type no: you choose its name, content type, schema and layout
Data beside the content playable
Built-in field voice
  • Players play files of a character type. A player who makes their own character in a world with several character types first picks which type.
  • Making the type in the app or from a workspace, or saving it in the app, adds a voice field to the schema; leave it there. Empty means the GM's voice. A type Orbit writes has one only if it adds it.
  • The app's type settings add a creation flow, the steps a player goes through to make a character (flows), and expressions, the faces a portrait can show (expressions).
  • The GM treats these files as people: it finds them by name, and keeps who they are and how they look in mind.
  • playable is kept on a file for older worlds, and nothing in play reads it. Which characters players can pick is set on each game start.

location

The type's files are places. Each one can have a map, exits to other places and links to the places it is inside or next to, and the GM moves the party along them.

Value "location"
Fixed type no: you choose its name, content type, schema and layout
Data beside the content map, transport, relations
  • A location can have a map, with areas, pins, tokens and exits (maps), and links to the places it is inside or connected to (linked locations).
  • transport marks a place that carries people, like a ship or a caravan.
  • The GM moves the party from place to place along these, and shows the map in play.

gm_instructions

Deprecated (GM Harness V1): each file was a rule for the GM. The GM no longer reads these files: its rules are GM Instructions, kept on the world.

Value "gm_instructions"
Fixed type no: you choose its name, content type, schema and layout
Data beside the content gmInstruction

The GM doesn't read these files, so don't make new ones: write the rules as GM Instructions instead (GM instructions).

game_start

A fixed type for the openings a player picks when starting a game. A file's content is only its card; the starting place, characters and opening are kept beside the content.

Value "game_start"
Fixed type yes: named "Game Start", json content, the base fields only, no layout, searchable visibility
Data beside the content gameStart

A game start's file holds only the card a player sees when picking it: name, description and picture. Its starting place, characters, opening lines and opening state are its designation data (game starts). Its name is fixed, so a world has at most one Game Start type.

script

A fixed type for JavaScript the GM runs during play: each file is one script, named by its file name. Only in a world where scripts are on.

Value "script"
Fixed type yes: named "Script", javascript content, the base fields only, no layout, hidden visibility
Data beside the content script

The Script type can be made only in a world where scripts are on, and never in a game. Its files are hidden from the GM's context: the GM runs a script, it never reads its code (scripts).