Craft

Designing a game system

A game system is a set of decisions: how an action is resolved, what a character is made of, how a fight runs, how people get hurt, what they spend. Each decision needs a home the GM reads: a GM instruction, a field, a tracker or a script. This guide gives the order to make them in and where each one goes. Each feature's doc has the details.

Start from what players do

Name the three to five things players will do again and again: fight, sneak, talk their way past someone, cast, pilot, investigate. Every rule should serve one of them. Then decide how much crunch the world wants. Fewer moving parts play better: the GM follows a short, clear system closely, and a long one loosely.

A part of a system (just a skill system, just combat) follows the same order, starting at its own step. Read the world's current rules and its character type first, so the new part uses the stats and words already there.

The core roll

Most actions should resolve one way. Decide:

  • The dice: 1d20 + modifier, 2d6 + stat, a pool of d6s, d100 under a skill.
  • What is read off them: a total against a number to beat, a roll under a stat, successes counted in a pool, or bands (10+ clean, 7–9 with a cost).
  • Where the difficulty comes from. Craft's Rolls default tells the GM to roll when an attempt could fail, against a difficulty taken from the files when they set one. So put difficulties on files where they belong (a lock's DC, a guard's Notice), and say in the rule what to use when no file sets one.

Write it as one always-on instruction in the world's Game Master place (the crowned die on the workspace's left rail), with a worked example. Craft's defaults name no dice and no game system, so every world needs this rule, even one built on a well-known system: name it there and write only what differs. Never mention a d20 the world doesn't use. Notation, roll-under and pools are in Dice.

Stats and skills

Keep the stats few, and use each one in at least one rule. A stat no rule reads is decoration.

For skills, pick one of two shapes:

  • A map on the character. One object keyed by skill (ranks, or trained or not) and one computed list that joins it with the skill definitions for the sheet. Right when skills are a name and a number. A new skill is then one new key, not a schema change.
  • Their own file type, referenced from the character. Right when each skill or talent has rules text, prerequisites or ranks with their own effects, or the GM should look one up on its own.

Never one field per skill. Modifiers, totals and anything else worked out from a stat are computed fields, never stored. The patterns are in file types and improving file types.

Reshape the starter types

A world made from scratch starts with a Character type that has D&D ability scores (Strength to Charisma) and a carrying capacity worked out from Strength, and Equipment files of D&D gear. For any other system, replace the stats and the computed fields that read them with the world's own, and keep what still fits, such as the inventory of equipment references. Don't add a second stat block beside the D&D one: the GM and the sheet will read both. How to change a type that already has files is in changing a type.

Combat

Craft gives every world a fight: the Combat tracker, a turn order that shows each fighter's HP and Conditions, and the Running a fight procedure, which the GM reads as a fight starts. It covers turns (the GM plays every NPC's and ally's turn), melee reach, the stat shown under the tokens, and table talk. Pick one of three:

  1. Keep both, and write only the world's own rules for attacks, defense and damage. Right for most worlds.
  2. Reword them for a world whose fights differ in shape: zones instead of reach, Stress instead of hit points, morale that ends a fight early. Change Craft's text in place; don't write a second fight procedure that argues with it.
  3. Replace Combat with the world's own tracker under the same key, fight, with its own procedure, and scripts that start the fight, pass the turn and resolve an attack exactly.

Start with the first, and move on only when the world's fights don't fit it. Never keep two fight trackers: both would answer "a fight begins". How to reword or replace one of Craft's is in Craft's defaults, and the tracker side in trackers.

Damage, harm and conditions

  • Harm is a field on the sheet: hit points, stress, wounds, a condition track. Give it a minimum and a maximum, and computed maximums where it grows with the character.
  • Conditions are a list on the sheet, from a fixed set of values (an enum), so rules can name them and the GM can't invent new ones. Each condition a rule names exists in that set.
  • Going down and dying are a rule. Craft's defaults mark someone as down but don't say what follows, so say what happens at 0: out of the fight, a save, a scar, death. A rule for one moment like this is a situational instruction (see triggers).
  • Show it. Put harm and conditions where players look, in the type's layout.

Resources

  • What one character spends (spell slots, ammunition, Force points, stamina) is stored as what is left. The maximum is a computed field, read from the class or another file that owns it.
  • What belongs to no one sheet (the party's supplies, the crew's Heat, a doom clock) is a tracker, which keeps it on screen for the player and in front of the GM, with its rules for when it changes.
  • Spending with exact steps (pay the cost, roll the effect, apply it) is a script.

Classes and abilities

Rules live on the type that owns them. A class or archetype is its own file type holding what it grants: its resources, its features, its table of values by level. The character keeps a reference to its class and its own current values. Abilities with their own text and cost are files of their own type, referenced from the class or the character. A new class is then a new file, not a new character schema.

An ability with exact steps (spend 2 Focus, roll 2d6, push the target back) is a script, so it comes out the same every time. A player script can show a card with buttons to use it (see script cards).

Progression

Craft has no built-in leveling. Experience, levels and what each one unlocks are the world's own, built from fields, computed fields, trackers, procedures and scripts. See designing progression.

Where each part lives

Part Where it goes
The core roll, the stats it uses, the system's name An always-on GM instruction
A rule for one moment (dropping to 0, a called shot) A situational instruction
How a longer moment runs (a fight's rounds, a chase) A procedure
Math, rolls and bookkeeping done the same way every time A script
Numbers worked out from others (modifiers, maximums) A computed field
A count no one sheet holds A tracker
A variant players choose (lethality, difficulty) A player option's choices
Explaining the rules to players The Player's Handbook

The GM never reads the Player's Handbook. A rule written only there is a rule the GM never sees: write it where the GM reads it, then explain it to players in the handbook. The general table, beyond a system, is in working with AI.

Prove it with one example

Before building every class and every item, finish one character to the full standard and walk it through one check and one fight against the rules as written. Every number a rule asks for should be on the sheet, and every stat on the sheet should be read by a rule. Then play a fresh game: the Instruction tester shows which situational rules a move brings in, and only play shows whether the GM follows the core roll. To check a script, open the Test tab under the code, fill in the input and press Run (⌘/Ctrl+Enter). Write the handbook's rules chapter last, once the rules have settled.

Mistakes

  • A stat block no rule reads. A bag of numbers is not a system. Every stat is read by a rule, a computed field or a script.
  • A rule that names a stat no sheet has. The GM makes up a value.
  • D&D leftovers in another system: ability scores beside the world's stats, carrying capacity from Strength, a d20 named in a 2d6 game.
  • A second Combat tracker or fight procedure beside Craft's. Reword or replace Craft's instead.
  • Exact math left to the GM. Damage formulas, resource costs and table lookups belong in scripts and computed fields.
  • Rules only in the handbook. The GM never reads it.
  • One field per skill, or per anything in a family. Use one map.
  • Too many subsystems. Each one is something the GM must remember to apply. Cut the ones no player action needs.