Character Creation and Playability

The default Character creation flow asks for concept, stat spread, Drive, and one sample Archetype. A quick reskin that keeps the default stats and Archetypes can leave this flow untouched.

If you change the System Profile's stat labels, keys, or starting spread, update Character creation before writing pregens. The profile owns the rules; the flow owns player input. If they disagree, creation produces invalid characters. StoryRig's Core Moves are stat-key agnostic, so after a key change you only need to review world-specific Moves with a Default Rating Key and retained Archetypes whose suggested ratings use old keys.

If you remove Archetypes, remove or replace the Archetype choice in the flow. Do not leave a dead choice screen pointing at deleted examples.

Pregens

Ship at least one or two pregens that demonstrate how your world plays. Their descriptions should sell a play fantasy and method, not waste the selection card repeating visible portrait details.

Game Starts

A Game Start should open inside a specific situation and leave the method open. State what is happening, what matters, and the details the player can act on. Do not script a mandatory sequence of scenes or hide the only valid solution behind a specific Move.

The StoryRig demo uses one closing departure because the same situation supports technical, social, and improvisational approaches. Replace it when your world has a better first promise.

Context visibility

For a finished Craft world, apply context visibility intentionally in the app. A strong default is:

• Pinned: one concise world/core GM instruction and only truly current state that needs every turn.
• Partial: situational mechanics the GM should know exist.
• Searchable: Moves, Conditions, inactive Progress Tracks, Threat libraries, gear catalogs, deep rules, and lore.

Do not force the GM to re-read files every turn. Progressive disclosure improves reliability as well as context efficiency.

Before you publish

Check the World as a creator would receive it after cloning:

• the active System Profile uses your World's language rather than StoryRig placeholder language;
• sample Archetypes, Conditions, Equipment, Threats, and the Last Platform demo are either intentionally retained or removed;
• custom character creation and any pregens produce valid Characters against the active stat keys;
• the first Game Start demonstrates the World's actual promise instead of only explaining its lore;
• context visibility is set in the app so Core rules are standing context and libraries are demand-loaded;
• a focused GM regression covers at least a strong hit, mixed hit, setback, canonical capability lookup, and one state-change boundary.

A small, coherent World is a better launch package than a large library of examples the creator has not tested in play.