Hostiles and the XP Economy
Hostiles are the system's friction. They are deliberately simpler than characters — no skills, no slots, no progression — because a game master reads six of them a scene and computes none of it. Build them to be read, not to be simulated.
Threat tiers are the load-bearing wall
threat_tier (Mook / Standard / Elite / Boss / Legendary) does three jobs at once: it sets the stat bands, it sets the default XP, and it tells the game master how to spend the hostile in a scene. The bands:
| Tier | HP | Defense | Saves | Attacks | XP |
|---|---|---|---|---|---|
| Mook | 8–15 | 12–14 | +1 to +2 | one, 1d6-ish | 15 |
| Standard | 20–35 | 14–16 | +2 to +3 | one strong, 2d6-ish | 40 |
| Elite | 40–60 | 16–18 | +3 to +4 | multiple or 3d6 | 100 |
| Boss | 80–120 | 18–20 | +4 to +5 | multiple + abilities | 250 |
| Legendary | 150+ | 20+ | +5 to +6 | the set piece | 600 |
The two existing hostiles anchor the bottom of this table: the Brute (HP 15, Def 13, machete +4, a Rush charge) and the Street Shooter (HP 12, Def 14, light pistol +5, a Take-Cover-and-kite loop). Both are Mooks with one idea each — and that's the design: one idea per hostile, executed reliably. A Mook is a behavior, not a build. Elites and Bosses earn a second idea; nobody needs a Mook with five.
Anatomy and conventions
hp,ar,defense,speed,save_fort/save_ref/save_willare stored numbers — hostile stats do not compute, by design. They map to the player math (Defense ≈ 10 + REF mod + Evasion) so the game master can sanity-check a hostile against a party, but they stay hand-set for reading speed.attacksis one line per attack: name, to-hit bonus, damage dice — "Machete +4, 2d6" — written to be read aloud, not parsed.special_abilitiesholds the hostile's idea. Phrase each as a reusable rule with its trigger and cost: "Rush: +2 to the attack after a 3-square straight-line move." "Take Cover: spends every Minor Action in cover; Def 16 until it moves." A special ability that needs a paragraph isn't special, it's a subsystem — cut it.lootis one item per line and should pay the fight: a weapon, a piece of armor, cash in the currency that fits the hostile's world (a corp goon drops ES-relevant evidence, a ganger drops CC).xpoverrides the tier default — set it only when a hostile is deliberately mispriced (an escort target worth zero, a swarm of one real boss split across five bodies). Otherwise leave 0 and let the tier table do its job.descriptionis the game master's first read: posture, tell, and how it fights. Two sentences. The portrait carries the rest.
Pricing a scene, not a monster
Because XP totals scale by party level and split evenly, the balancing unit is the encounter, not the hostile. A quick rule of thumb from the XP table: at any level, one Standard hostile is roughly a third of a level's worth of XP for a small party; a Boss plus two Mooks is most of a session. When adding content, ask what the scene should pay (in XP and in CC), then build the hostiles that make that scene honest — not the other way around.
Hostiles bypassed by stealth, deception, or negotiation pay half XP. Build at least one hostile per scene that rewards not fighting it — the economy is designed to pay the runner's path, and content that only pays the loud path quietly teaches players to ignore half the system.