Builder's Manual · Chapter 1

How GLASS Is Built

This manual is for someone extending GLASS — adding a class, a weapon line, a whole district, or porting the engine to another city. It states intent and constraints, not flavor. The Player's Handbook covers play; this covers construction.

The architecture

GLASS separates three layers, and keeping them separate is the whole trick:

Data lives in file types. Thirteen types hold everything: Character, Class, Talent, Weapon, Armor, Gear, Neural Cyberware, Somatic Cyberware, Hostile, Cover, Location, Game Start, and World — the file that binds a setting to the engine (see The World File). Each type has one schema (what fields exist), one rendered layout (how the file displays), and one creation flow (how a new file gets built). Files live in folders named after their type.

Rules live in GM Instructions — not in the schemas. The dice math, DC ladder, combat procedure, healing, XP economy: all of it is instructions the game master loads during play, organized as always (core resolution — loaded every turn), situational (loaded when their trigger fires, ≤1000 characters), and procedure (loaded whole when their moment comes, ≤10,000 characters). A rule that lives in a schema field instead of an instruction is a bug.

Presentation lives in layouts. No field exists to make another field look nice. If a file needs a label, a glyph, or a computed display string, it goes in the type's layout, never in the data.

The design pillars

Four decisions explain almost every number in the system. Break one and you break the balance quietly:

  1. 2d12, bonus capped at +10. Two d12s make the distribution spiky and the edges meaningful — natural 2 always fails, natural 24 always succeeds and critically hits. The +10 cap means attributes, skills, talents, and cyberware bonuses compete for the same budget. A new feature that adds +2 to a roll is spending from that budget; a feature that adds +5 is spending a character's entire career.
  2. The fixed DC ladder never scales. DC 7/10/13/17/21/25/28 at every level. Characters grow by adding bonus, not by inflating DCs — which is why a DC 13 door is trivial to a level 10 hacker and still a real obstacle to a mook.
  3. The sheet computes everything derivable. AR, HP, Defense, skill totals, XP thresholds: all computed fields with expressions. Stored values are inputs (scores, ranks, worn items); computed values are outputs. Never hand-enter what the sheet can calculate — see The Character Sheet.
  4. One XP economy prices everything. Hostiles have a threat tier (Mook 15 / Standard 40 / Elite 100 / Boss 250 / Legendary 600), tasks have fixed values, totals scale by party level and split evenly. Any new content that awards or consumes XP plugs into that table — it does not invent its own.

What building means here

Three altitudes, in order of preference:

Content — a new talent, weapon, hostile, district. Stay inside the existing schemas and conventions; this manual's middle chapters are the conventions. Most building is this, and it's the cheapest.

Structure — a new file type (a Faction, a Vehicle, a Net Program) or a new field on an existing one. Read the schema conventions in The Character Sheet first: classify every field before adding it, never store what can be computed, collections over numbered slots.

Rules — a new subsystem (netrunning, vehicle combat). This is GM Instructions work plus a Player's Handbook chapter to match. The pair must ship together: the instructions tell the game master how to run it, the handbook tells the player what to expect. See Extending the Rules.

Before you change anything

Two habits keep the system coherent:

  • Read three existing examples before writing your first one. The talents folder has 78 files that define what a talent sounds like; the weapons folder defines every damage band you'll need. Copy the conventions, then vary.
  • When you change a rule, change it everywhere. A rule lives in the GM Instruction, the Player's Handbook chapter, and sometimes a computed expression on the sheet. If those drift apart, the game master runs one rule and the players read another — the worst failure a system can have.
Manual updated Nov 13, 2026.