Craft

Triggers

A trigger says when an instruction applies. Twice a turn a check reads the moment and suggests to the GM what may apply: the situational instructions and procedures whose trigger fits, and the scripts and tracker starts whose moment has come. Trackers' triggers are covered with trackers, scripts' with scripts.

The trigger check

A quick check runs at two moments in every turn, and asks of each trigger whether its moment has come:

  1. Before the GM answers, against the player's message. It covers situational instructions, procedures, tracker starts and the scripts' beforeNarrationTrigger.
  2. After the GM narrates, against the reply it just wrote. It covers situational instructions, procedures and the scripts' afterNarrationTrigger that the turn didn't run. What fits here goes to the GM's follow-up step, where it records what changed, so a rule about the consequences of what was just told (a wound, a broken promise) still lands this turn.
  • What it reads: the player's move, the end of the GM's last reply, whether a fight is under way, and the start of the world's always-on instructions; after the GM narrates, its whole reply too. It does not read character sheets, trackers or hidden values.
  • What it judges by: each instruction's trigger and the first 240 characters of its text; a script's name, what it does and its beforeNarrationTrigger or afterNarrationTrigger.
  • What the GM gets: a short list headed as suggestions, right beside the player's message (or in the follow-up step), likeliest first: up to 5 situational instructions and up to 3 procedures.
    • A situational instruction comes in full the first time it fits since the game's story was last summarized, with its trigger and text. After that it is named by its title, since its text is still in what the GM has read. An edited instruction counts as new and comes in full again.
    • A procedure is always named by its title only. The GM reads it if it fits and isn't already in front of it.
  • What it covers: the world's situational instructions and procedures, Craft's, and those of every picked choice: at most 100 situational instructions in a game.

Limits: the trigger is up to 120 characters; the text up to 1,000.

See also: Procedures, the format.

Writing a trigger

Describe a moment someone could see happen in the story, starting with "When…".

Works Unreliable Why
"When the player tries to lie to or persuade someone" "When the player's Heat is above 5" The check can't see trackers or sheets
"When a character drops to 0 HP" "When HP changes" Name the moment that needs the rule
"When someone grapples or is grappled" "When anything happens in combat" A broad trigger matches most turns
"In a game's opening scenes" as an always-on rule "When it is the first session" The check can't see how far along a game is

Example:

{
  "when": "situational",
  "trigger": "When a character drops to 0 HP",
  "body": "They fall unconscious and make a death save at the start of each of their turns: roll 2d6, and 7 or higher is a success. Three successes and they stabilize; three failures and they die."
}

Keep triggers specific

A trigger that matches most turns takes one of the 5 places every turn from an instruction that was needed. If a rule truly applies to every turn, it is always on, not situational.

Split what can't happen together, merge what fires together

Split moments that never come up at once: separate melee, ranged and spell attacks rather than one "When someone attacks". But when one moment would bring in several instructions together ("A feat is used", "A character uses a Mana Feat", "A feat needs a saving throw"), make them one ("When someone uses a feat"). Apart, they take three places and can disagree.

The ruling first

The check sees only the start of an instruction's text, and the GM reads it in the middle of a turn. Put the ruling in the first sentence, then any detail. Keep each instruction to one moment: a long "Combat rules" block becomes "When a character drops to 0 HP", "When someone grapples" and so on, with how a fight's rounds run as a procedure.

A procedure's trigger

A procedure's trigger is "Use it when…": the GM sees it beside the procedure's title in its list and decides for itself when to read the procedure. No check picks it. Write it the same way, as a moment in the story ("When the ship fights another ship").

See also: Procedures.

Testing triggers

The Instruction tester in the Game Master place takes a player's move and shows which situational instructions, tracker starts and player option instructions it would bring in, each with how sure the check is. It asks about every choice of every option, whatever is picked, and shows when more came up than a turn is given. Leave the move blank to try an example. It never asks about procedures.