Wiring the Game Master

Rules don't run themselves. Game Master Instructions/ is the part of the project the GM executes, built on a separation worth keeping: Rules/ is the reference; instructions are the runtime.

The always-on set

Four standing files define how the GM operates every minute of play, and they are deliberately short — context is a budget, and anything the GM can look up on demand belongs in Rules/.

• @Missing file — the resolution engine on one page: the universal formula, the four degrees, the DC tables, the Remaster line.
• @Missing file — the field map. It names every camelCase field and instructs the GM to read totals, never raw values, and never to re-apply a bonus a linked file already granted.
• @Missing file — makes spell slots, Focus Points, Hero Points, and consumables real instead of narrative.
• @Missing file — what the players must not see: stat blocks, hidden DCs, secret-trait rolls.

The triggered set

Ten instructions fire on events, each named as its trigger — the filename is the contract. @Missing file routes uncertainty into a proper check with a real DC. @Missing file and @Missing file run encounters off the sheet's printed lines, including the multiple attack penalty and the dying ladder. @Missing file handles slots, heightening, and the manipulate trait. @Missing file applies condition files — with the explicit warning that the sheet already applies their penalties, so never apply them twice. @Missing file, @Missing file, @Missing file, @Missing file, and @Missing file cover the rest.

Two hard limits, and the headroom you have

The platform caps a project at 20 narrative triggers. This project uses 10, which is unusual — most of the library's systems run at or near the cap. You have ten free slots for whatever your world needs, which is the single most valuable thing you inherited here.

A trigger body must stay under 500 characters or the server rejects the push. Write tight, name each instruction as its trigger condition ("When the party enters the Bramblewater"), and reference exact camelCase fields (focusPointsCurrent, dyingValue, mainHandAttackBonus). An instruction that says "their focus points" invites the GM to invent bookkeeping.

The pattern for a new subsystem

Durable state in a schema, reference text in Rules/, a triggered instruction that makes it happen — all three, every time. A rule with no instruction doesn't exist at the table; an instruction with no stored state resets every session.

The voice

The GM persona lives in project settings, separate from all of the above: fair, rules-forward, reads computed totals, announces public DCs and keeps private ones, narrates degrees of success as story beats, and rewards flanking, @Missing file, Demoralize, and a well-timed @Missing file. Instructions define what the GM does; the persona defines how it sounds. Reskin the world and retune the voice to match.