Builder's Manual · Chapter 3

Writing Classes and Talents

Classes and talents are the system's character-facing vocabulary. They are plain data — no computed fields — which means their quality lives entirely in the writing. Here is what good entries look like and why.

Class anatomy

A class file has nine fields: name, description, coreIdentity, primaryAttributes, level1Features, signatureFeatures, progression, capstone, image.

  • description is the one-liner for the picker ("Hacking, cyberwarfare, the ghost in the machine"). coreIdentity is the design contract — the mechanical territory only this class owns. If a new class's coreIdentity overlaps an existing one, one of them is wrong.
  • primaryAttributes names the two attributes the class leans on. This drives feature design and the sheet's expectations — a class leaning on attributes its players won't raise is a trap.
  • level1Features is exactly two features. One is a static edge (a bonus, an option swap), one is a reusable action economy trick. The Malware Specialist pattern — Intrusion Protocol (+2, attribute substitution) and Quick Hack (a hack as a Minor Action) — is the template: both are usable in the first five minutes of the first fight.
  • signatureFeatures is an array of {name, level, description}. The level cadence this system uses is roughly 3 / 6 / 10 / 14 / 17 — a feature every three-ish levels, each changing how the class plays, not just its numbers. Neural Spike adds a rider; System Override adds a control tool; Cascade Failure adds chain economy. Scale up consequence, never just magnitude.
  • capstone is {name, level: 20, description} and must be the class moment: once-per-combat, table-visible, and impossible for any other class. God in the Wires shuts down every electronic system in 30 meters — nobody else can do that at any level.
  • progression records the advancement hooks: minorTalentLevels (evens 2–18), asiOrMajorTalentChoice + asiOrMajorTalentLevels (5/9/13/17). Copy this block verbatim into every new class. It must match the global ladder in the GM Instructions exactly — a class with its own leveling rhythm is a fork of the system, not a member of it.

Talent anatomy

Six fields: name, tier, category, effect, description, image. Only two carry real design weight.

Tier is a balance contract. Minor talents arrive at every even level — nine per career — so each one is small: a flat +2 to a narrow check, a once-per-scene reroll, a single condition fix. Major talents arrive at 5/9/13/17 instead of an ASI, so each one competes with +2/+1 attribute raises: it changes how a fight or a job works (Bullet Time, Neural Fortress, Master Hacker's reroll-and-rider). If a Minor talent would make a player skip the ASI, it's a Major. If a Major could be taken nine times without breaking the game, it's a Minor.

effect is the whole rule. It must be mechanically self-contained — dice, DCs, durations, targets — because the game master loads it in play without this file open. Compare the house style:

  • Good: "Immune to neural hacking; hackers take 2d6 feedback damage."
  • Good: "Once per combat, shut down one electronic system for 1d4 rounds."
  • Bad: "You are a master of the digital shadows." (Nothing to roll. Nothing to run.)

Flavor lives in description, one sentence, optional. If the effect needs the flavor to make sense, the effect is unfinished.

category organizes the browser (Combat, Tech, Social, Cyberware, Survival) — use an existing value unless the talent genuinely opens a new lane.

The pairing test

Before shipping either, run the pairing test: pick two existing talents and your new one, and ask whether one character could take all three and trivialize the +10 cap or a core loop. Stacking +2s to one roll is the system's known failure mode — three narrow bonuses at the same roll from different sources is a build, five is a bug. When in doubt, make the new talent narrower instead of weaker.

Manual updated Nov 13, 2026.