Builder's Manual · Chapter 6

Extending the Rules

Rules live in GM Instructions — the settings.gameOptions instruction list — not in schemas, not in the books. This chapter is how to add or change one without splitting the system in half.

The three shapes

Every instruction has a when that decides how it loads:

  • always — the core resolution layer: dice, DCs, attributes, skills, saves, derived stats. Loaded every turn. There are five; a new one is almost never warranted. If you're writing an always instruction, first ask whether the existing four can carry it.
  • procedure — a full sequence the game master loads whole when its moment comes (currently: running a fight). Budget is 10,000 characters. Use this for anything with phases, rounds, or a turn structure — netrunning, chases, a heist clock.
  • situational — everything else. Loaded when its trigger fires ("when a character heals", "when XP is awarded"). Budget is 1,000 characters. This is the workhorse: wounds, malfunctions, armor, economy, XP, healing all live here. If your rule doesn't fit in 1,000 characters, it's two rules — split it, or it's a procedure.

Every instruction also carries a section (Rules, and whatever new sections you add) and a trigger phrased as a moment, not a topic: "When a character reaches 0 HP or takes damage while Dying", not "Death rules."

Writing an instruction

House style, learned from the ones that work:

  1. Open with the decision, not the philosophy. "XP comes from defeated hostiles and completed tasks, awarded when the dust settles" — the game master can act on sentence one.
  2. Numbers inline, one format. DCs, dice, durations and currencies in the sentence that uses them. No tables the reader must cross-reference mid-scene.
  3. Mechanical, self-contained, and honest about edge cases. The instruction is read cold, mid-scene, without your design notes. Anything ambiguous will be adjudicated live and then drift forever.
  4. Name the bookkeeping. The best instructions end by saying what to update and when ("record the new HP in the same update as the hit") — because the game master is also the one maintaining the sheets.

The rule of three places

When a rule changes, it usually exists in three places, and all three must move together:

  1. The GM Instruction — how the game master runs it.
  2. The Player's Handbook chapter — what players expect to happen.
  3. A computed expression on the sheet — if the rule touches a derived stat (a new Strain source, a new Defense rider, a changed XP threshold).

Skipping the second produces a table where players are wrong about their own game; skipping the third produces a sheet that lies. This is the single most common way systems rot from the inside, and it's why How GLASS Is Built calls it out twice.

Porting GLASS to another setting

The engine and the chrome separate cleanly. Setting-bound (rename freely): GLASS and its surveillance fiction, ES/CC and the currency narrative, the megacity, faction names, item flavor. Structural (touch with care, change only deliberately): the 2d12 core and the +10 cap, the fixed DC ladder, the attribute/modifier ladder, HP and Wound Threshold formulas, the death save economy, the threat tiers and XP table, the combat procedure.

A port that keeps the structure and swaps the fiction is a weekend. A port that wants different math is a fork — write it as one, with its own manual, and say so in its first chapter.

Manual updated Nov 13, 2026.