Two wrong mechanisms in one sentence of my own v0.10 prose. The measured swing
of 40 is unaffected -- what was wrong was the explanation I gave for it, which
I wrote from intuition rather than from rules.mjs.
1. "every disable removes an attacker" -- it does not. locationEffectsFor
(rules.mjs:461) charges 30 points off physical for a ruined leg or
manipulation for a ruined arm, and simulate.mjs:305 applies the
manipulation penalty to melee and ranged attacks alike. A 40% attacker
disabled is a 10% attacker, not an absent one: still swinging, still
drawing attacks, still a target. A slope, not a cliff.
2. "both sides go down at half their maximum hit points" -- also wrong, and
this one nobody flagged. Half maximum hit points is majorWoundFor, the
MAJOR WOUND threshold, which feeds dyingLimitFor and decides how long a
dying character lasts. It has nothing to do with leaving the fight.
conditionFor (rules.mjs:1630) puts somebody down at 2 hit points or on a
destroyed head, and that is the only thing that stops them acting.
The paragraph now states the real loop and warns the GM off the wrong one,
because playing disables as removals gets the fight wrong in the party's
favour -- the direction that makes a party-ending encounter feel survivable.
Credit where due: the first error was caught by a peer session correcting
prose it had sent me twice. I found the second only because I verified the
first against rules.mjs instead of taking it on assertion.
npm run check: 14 guards, exit 0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
