Death at zero, and a case brief that answers the useful questions
R-223: nothing happened at 0 hit points. An agent was marked down and lay there forever; the only mention of death in the system was flavour text on a destroyed head. Zero now starts a clock whose length is the agent's own Major Wound threshold, ticked from the same hook that charges blood loss. First Aid or Medicine stabilises and stops the count; healing above zero clears it; heal() refuses the dead. On death, Coherence decides what the record says — from a proper death in service down to not being recorded as dead at all. Case generator: four phases instead of five (the arc drew two interchangeable middles that read as padding). The brief now leads with Where / When / Classification / Phases, states the opposition in full, and has a "How you get back" section. place and duration were generated and never printed. The same facts are on the case file itself. 300 seeds checked for object leaks; one found and fixed (group taboo/desire are objects with .text). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
a360d77b83
commit
89ce557355
@@ -3799,3 +3799,64 @@ floor the old ramp produced.
|
||||
**R-222 confirmed across the board.** Every agent came out of this case with ticks —
|
||||
Dodge, First Aid, Firearm (Pistol), Firearm (Rifle), Navigate — where before the fix
|
||||
a case produced none at all from phase work.
|
||||
|
||||
## Zero hit points now means something
|
||||
|
||||
**R-223 · nothing happened at zero.** An agent reduced to 0 hit points was marked down
|
||||
and then lay there indefinitely. Bleeding deliberately stops at zero, no rule advanced
|
||||
anything, and the only mention of death in the entire system was flavour text on a
|
||||
destroyed head location. A game with hit locations, Major Wounds and bleeding had no
|
||||
way for anyone to die.
|
||||
|
||||
Hit points are not taken below zero — every damage path clamps there and unpicking
|
||||
that would touch everything. Zero starts a clock instead:
|
||||
|
||||
above 2 up
|
||||
2 or below DOWN — out of the fight, still conscious, still yours
|
||||
0 DYING — unconscious, no actions, no defences, the count begins
|
||||
count met DEAD
|
||||
|
||||
The count is the agent's own **Major Wound threshold**, so the number that already
|
||||
decides how much damage they take standing up also decides how long they have on the
|
||||
floor, with a floor of two rounds. It ticks from the same end-of-round hook that
|
||||
charges blood loss, so nobody has to remember it — which is exactly why bleeding
|
||||
worked and dying did not exist.
|
||||
|
||||
**Stabilising** takes First Aid or Medicine and stops the count. It does not put
|
||||
anyone back on their feet: still zero, still unconscious, until somebody heals them
|
||||
above it, which clears the count automatically. A FUMBLED attempt over a dying agent
|
||||
costs them a round they do not have. `heal()` now refuses the dead, which is the one
|
||||
place that had to say so because every medical path routes through it.
|
||||
|
||||
**The last entry.** A Custodian's death is a filing question. How well filed they were
|
||||
decides what the record says: at Coherence 7+ a death in service with a form and a
|
||||
pension; at 4–6 two dates of death on file and Registry asking which is correct; at
|
||||
1–3 a file that will not close, with correspondence still arriving and being answered;
|
||||
at 0 they are not recorded as dead at all but filed as transferred, to a section the
|
||||
department cannot produce an address for.
|
||||
|
||||
Four rules, ten spot-checks, on the sheet as a banner in all three states, and
|
||||
documented in the rulebook. 44 rules, 148 formulas.
|
||||
|
||||
## The case generator, simplified and made to say the useful things
|
||||
|
||||
**Four phases, not five.** The arc drew TWO interchangeable middle phases, which read
|
||||
as padding — two seeds in a row produced "The search" then "Inside" with nothing to
|
||||
tell them apart. One middle phase: Approach, the thing in the way, the job, and out.
|
||||
|
||||
**The brief now answers the operational questions first.** It opened on a
|
||||
classification note and never stated where the site was, how long the team had, what
|
||||
was likely to be in the way, or how they were getting out — all of which the generator
|
||||
already knew and threw away. `place` and `duration` were generated and never printed.
|
||||
The brief now leads with a table of Where / When / Classification / Phases, then the
|
||||
job, then what is reported, then a full section on the opposition — numbers, tier,
|
||||
motive, tactics, and what might work instead of shooting — then **How you get back**:
|
||||
the extraction ground, the Transposition roll, the classification modifier, and the
|
||||
warning that a bad crossing is the only way an Art is ever acquired.
|
||||
|
||||
The same four facts are now on the CASE FILE ITSELF, so a GM does not have to open the
|
||||
journal to answer "where are we and how long have we got".
|
||||
|
||||
Checked across 300 seeds for `[object Object]`, `undefined` and `NaN` in every
|
||||
generated page: clean. One real leak found and fixed on the way — the group's taboo
|
||||
and desire are objects with a `.text`, and the brief was printing the object.
|
||||
|
||||
Reference in New Issue
Block a user