THROUGH TRAIN publishes "MEASURED, 400 runs each" and a 24% wipe rate; the starter
publishes its own table. Nothing in this repository could produce either number, so both
were claims rather than results and neither could be re-checked after a rule moved.
The harness knows no rules of its own. Everything comes out of rules.mjs, because a
harness with its own copy of the combat loop measures a game nobody is playing and
drifts silently the first time a rule changes. Two things had to move for that to be
possible:
applyDifficulty, resolveBands and gradeRoll -> rules.mjs. The whole of d100 resolution
lived in ringbrp.mjs, which node cannot import. All three are pure, so they moved and
the engine re-exports them; no caller changes. check-rules then refused them for having
no spot-check, so they now have fifteen, covering the 1% floor, the 96-99 rule and
00-always-fumbles. They had none in their entire life inside the engine.
expandFromRegister -> tools/expand-spec.mjs. A roster agent is written as a job and a
rank and carries no skills or kit; everything it can do is derived at build time by a
function locked inside build-packs.mjs, which cannot be imported because importing it
runs the build. A simulated agent expanded by a second copy of that logic is not the
agent that gets packed. Moved verbatim; both sides import one copy.
Deterministic throughout: same creature, party and seed, same numbers, which is what
lets a published table be verified rather than remembered.
What it finds: for the Act Three standoff the seed barely matters (0.5-2.8% wipe across
five seeds, eight rounds throughout) and party composition dominates everything. Four
support agents against the six miners wipe 92.8% of the time; swap in the heavy and the
warden and it is 0.3%. The published 24% is not a property of the encounter, and no
single figure can be.
Models Reaction re-rolled each round, banding, graded defences, the stacking defence
penalty, damage by band, major wounds and the dying clock. Does NOT yet model hit
locations, bleeding, panic, cover, range bands or fire modes, all of which make a losing
fight worse. Read the output as a floor, never a ceiling.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Reversed experience. A skill is marked when it FAILS - failure or fumble - and
never when it works, and the improvement roll is the same reversal: roll OVER
your rating and the skill goes up 1d6. Nobody learns anything from the lock that
opened first time.
The two halves pull against each other on purpose, so ratings converge instead of
running away. Simulated over 2000 campaigns: a 10% and an 85% skill start 75
points apart and are 11 apart after 60 cases.
- rules.mjs owns it: DEVELOPMENT, developmentMarksOn, developmentImproves,
developmentCeiling, developmentGainFor
- trainingCap has been on the skill schema and the item sheet since it was
written and nothing has ever read it. Development reads it now: a skill stops
at its own cap, and everything else stops at DEVELOPMENT.ceiling, because a
d6 gain could otherwise push a 98% skill past 100
- GM opens the phase from a GM-only toggle in the token controls; it posts a
card naming every agent and their marked count, and puts a Development button
on each sheet. Players press their own
- the toggle re-reads the setting on change, since getSceneControlButtons only
fires at load and the button would otherwise lie if the phase were opened by
the API or a second GM
- rules journal and player primer rewritten from the tables; the old text
described the pre-reversal rule on both halves
- 7 spot-checks, 4 behaviour tests; verified end to end in a running Foundry
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ran THE HOLLOW ROAD with five agents — approach, crossing, contact, the thing on
the road, extraction, debrief — with panic and Coherence both live. It ran clean
and it found one thing that mattered.
ANOMALY LORE 0. Marta Holloway, Field Lead, Senior Field Officer, could not roll
the department's signature skill. Nor could Okonkwo. Induction was gated to
TRADES on the reasoning that a career posting is itself the agency training —
but 17 of the 25 postings do not list anomaly lore, its printed base is 0 on
purpose, and nothing else supplies it. So the people who joined the department
straight out of school were the only ones who never received its basic training,
which is exactly backwards.
Induction is a FLOOR for everybody now, posting or trade, in the live generator
and the pack builder both. It never demotes: Bhattacharya keeps Registry's 63,
Holloway goes 0 → 43, Okonkwo 0 → 33. All twenty built agents verified non-zero.
Two GM tools the case showed were missing, both found by feeling the friction
rather than by reading anything:
- clearPanic(actors). Panic clears when the scene does — one line in the book
and, until now, five sheets edited by hand while the table waited. It leaves
Coherence alone, which is the whole point of having two tracks.
- partyState(). Everybody's hit points, panic and Coherence in one card. With
five agents the alternative is asking "what are you on?" five times a scene,
which is friction a table absorbs silently and then blames on the game.
And the player-facing gap: the primer never mentioned panic. Players got a
one-page aide-memoire for a track they now meet in the first scene. It has a
page of its own and a row on the cheat sheet, both generated from the same
tables as the rules.
One thing I reported as a bug and withdraw: Okonkwo's "Firearm (Pistol) 5%" was
me rolling the wrong weapon. He carries a marksman rifle at 53%. check-kits was
right.
Version 1.2.0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ran the east corridor again with fresh dice and every relief attempt routed
through easePanic, fumbles included.
The rule did not fire this time. All three attempts failed cleanly — Psychology
58 against 40, and two POW×5 rolls at 66 and 76 — so nobody was punished for
trying. That is worth reporting as loudly as a hit would have been: two
play-throughs in and a fumbled relief has come up once, which is about right for
something meant to be a memorable disaster rather than a tax.
Braithwaite still broke at 5 on "it said your name" and fled. Marrow went down
in a single round to a special with the entry bar — 19 through armour — against
the 4.5-round average the thirty-run tuning gave, so that was dice, not balance.
Then the question the rule actually raises. Relief rolls are made at your own
panic penalty, so the worse you are the worse your odds AND the wider your fumble
range — and now a fumble adds a point. That is a feedback loop, so I measured it
rather than trusting it, 300 runs per row:
from 2, POW×5 60% 280 calm · 0 broke
from 3, POW×5 60% 227 calm · 2 broke
from 4, POW×5 60% 138 calm · 31 broke
from 4, POW×5 50% 96 calm · 35 broke
from 4, POW×5 85% 267 calm · 5 broke
Recovery dominates everywhere. The worst case — overwhelmed, weak POW, no help —
spirals into breaking about one time in eight, which is a bad night rather than a
trap. No change needed.
Also: panicReliefFor and panicAfter were missing from the API, which I only
noticed because measuring the loop needed them and the alternative was
re-implementing the rule in the test — the exact duplication check-rules exists
to forbid. Both exposed.
Version 1.1.3.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Trying to steady somebody and making it worse is the most familiar thing on that
list, and until now it was the only outcome that cost nothing.
Done as a NEGATIVE relief rather than a second code path: panicReliefFor returns
-1 on a fumble, and easePanic already subtracts what it is given, so subtracting
a negative raises the track. One number, one direction, no branch that could
drift from the other. The clamp still holds — fumbling at 5 stays at 5.
The chat card had to be told, because otherwise it prints the word "Psychology"
over a number that has just gone UP and the table reads that as a bug rather than
as the rule. It now leads with a red FUMBLED tag.
Guarded three ways: a spot-check in check-rules for the -1 itself, and two
behaviour tests — one that the sign survives easePanic's subtraction and
actually raises the track, one that it cannot push past the top. A test on the
constant alone would have passed even if easePanic had healed on a fumble.
Verified live: 2 → fumble → 3 → success → 2 → special → 0, and a fumble at 5
staying at 5, with the cards reading correctly.
Version 1.1.2.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
From the first game's list. The three skills are not decoration — they are the
levers on the new track, which is why they arrived together.
PANIC, 0 to 5, up. It is the other half of Coherence and the rules page says so
in the first line, because a table that confuses them will make the wrong call
at the worst moment:
Coherence what knowing has cost you weeks 10-0, down
Panic what is happening to you NOW minutes 0-5, up
A trigger gives a point with NO ROLL. Asking for a die to find out whether you
are frightened slows the scene and tells the player how to feel; the die is for
getting rid of it, which is the interesting direction.
0 steady · 1 rattled · 2 shaken -5% · 3 losing it -10%
4 overwhelmed -20% · 5 broken
The first point is free on purpose, so the opening shock of a scene costs the
table nothing. At 5 you break — freeze, flee or fixate, choose fast — and come
back at 3, not at 0, because breaking is not a rest.
Relief is where the skills come in. A success takes one point, a special takes
two. Psychology is the only thing that steadies somebody who is NOT you.
Religion steadies you alone and does not care whether you are right. Occult is
the odd one: naming a thing correctly, out loud, helps everybody who can hear —
the department's actual work, and the only relief that reaches a room. Plus
POW×5 to steady yourself, and your anchor object once per case, which is what
that briefing scene was for.
The three skills are placed in six registers rather than left floating: Occult
to the professor and to Registry, Psychology to the doctor and to Interview,
Religion to Antiquities and Pathology.
Guards, because a track nothing reads is this project's oldest failure: the five
new rules carry spot-checks in check-rules, and check-behaviour gains nine tests
— the free first point, monotonic penalties, only 5 breaking, clamping at both
ends, breaking not clearing the track, special taking two, every band/trigger/
relief having a label, and every relief naming a skill the catalogue actually
has.
Verified in a live game: penalty reaches the roll (58 → 58 → 53 → 48 → 38 for
panic 0-4, criticals and specials recomputed with it), the full arc runs 0 → 2 →
4 → eased to 2 → pushed to 5 → breaks → 3 with no errors, the sheet shows the
band, and the rules journal has a Panic page generated from the same tables.
Version 1.1.0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deleted: the seven PNGs in dice/, tools/make-dice-textures.mjs, the `npm run
dice` script, the RB_DICE colourset and texture tables, diceSetFor, the
diceSoNiceReady hook, and rbDressDice — which was tagging ten roll sites with
coloursets that no longer existed. 99 lines of module, plus the assets.
README and DEPLOY updated; they still advertised all of it.
Recoverable with `git revert` if it is ever wanted back.
This also explains the 01-that-was-12. The RESULT was never wrong: skillRoll
rolls one 1d100 and grades on roll.total, and the chat card derives the tens and
units it prints from that same total. Checked all 100 values of percentileFaces
and 60 live rolls — the printed faces reconstruct the graded number every time,
with no mismatches.
What disagreed was the ANIMATION. The custom addDicePreset labels registered for
d100 and d10 remapped which physical face means what, so Dice So Nice could land
showing 01 while the roll behind it was 12. Nothing downstream ever read the
animated faces, so no roll was ever adjudicated on the wrong number — but a
table watching the dice had every reason to believe otherwise, which is its own
kind of wrong. Disabling the skins in 1.0.6 already removed it; deleting them
makes it permanent.
Verified in a running Foundry after removal: skill roll, weapon damage, hit
location, major wound and Coherence all resolve and post their cards, no errors,
and game.ringbrp.diceSetFor is gone from the API.
Version 1.0.7.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Registering them with "preferred" made them the default for everybody in the
world, which overrides whatever dice a player had already chosen — the system
helping itself to a setting that belongs to the user. Off at the author's
request.
One named constant rather than a settings API: this codebase registers no game
settings at all, and adding that surface, its lang keys and its UI to switch one
feature off is more machinery than the job needs. Flip RB_DICE_ENABLED to true
and everything below it still works.
The textures in dice/ and the generator behind `npm run dice` are left alone.
Nothing reads them while this is false, and deleting work in order to turn a
feature off is a poor trade.
Verified in a running Foundry with Dice So Nice active: "custodians" is no
longer among the registered systems, and preferredSystem has gone back to
"standard" rather than ours.
Version 1.0.6.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Opened all of it this time, rather than driving the system through its API.
Two more defects of the same family as the NPC sheet, and in the same place —
the types added last:
- Talent and Art had no TYPES.Item.* label, so their sheets printed the raw
key "TYPES.Item.talent" under the name.
- Neither had a branch in item-sheet.hbs or an isTalent/isPower flag, so the
Detail tab rendered EMPTY over a document holding category, rule, uses per
case, Coherence cost, push cost and origin. Eleven of thirteen types were
handled, which is exactly the shape an eye skips.
Both now have a header statline and a full Detail section, and a guard walks
template.json: every declared type must have a label, a flag set in ringbrp.mjs,
and an {{#if isX}} section in the sheet.
One hardening fix: loseCoherence applies the cost and THEN announces it, so
anything that throws in between leaves the actor quietly poorer with no message.
localize() throws on a non-string, which an unrecognised reason key is.
Everything else came back clean, and it is worth recording what was checked so
the next audit knows what "checked" meant: 13 item types opened, all render; the
expedition sheet (4 tabs); all 7 chat cards driven through their real entry
points — roll, coherence, reaction via Combat.rollAll, hit location, weapon
damage, major wound, and contact through a case file that actually has a group;
all 3 dialogs opened by clicking the controls a player clicks. No errors, no raw
localisation keys anywhere.
Also: Culland Hall as a playable Scene. Drawn as SVG rather than generated,
because a room count, a door position and a label are all load-bearing here and
a generator cannot be trusted with any of them — three label-collision passes in
the browser before it was clean, which is the documented cost of doing it this
way. 2800x2000 at 100px to the square so the Foundry grid lands on the grid
drawn into the image; 5ft squares; no walls, because half-done walls are worse
than none and a GM who wants vision can add them in ten minutes.
Verified in Foundry: the scene imports, activates, and draws.
Version 1.0.2.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ten pages a player reads before session one, in their own compendium at OBSERVER
ownership: nine of setting, one cheat sheet.
The draft called the organisation "the Bureau"; everything else in the game calls it
the department or the agency, so that is what it is called. Thin areas filled rather
than padded: the seven character principles as a list, the real Coherence band table
instead of a paragraph describing one, and "what continuity is not" pulled out of the
middle of a page because it is the most important sentence for a new player.
The cheat sheet's numbers are computed from rules.mjs and lang/en.json at build time.
A hand-typed one would have been the sixth time this project shipped a number that
disagreed with the code, and the one the players were holding.
R-250: the design tokens were never on :root. Journals rendered as default parchment,
and four things were wrong in sequence — v14's hook is renderJournalEntrySheet; its
`element` is the node, so `[0]` returns the first CHILD and put the class on a header
button; there is no .journal-page-content in v14; and then the real one: with the
selector matching, font-size, line-height and padding all applied while every colour
did not, because the palette is declared on .ringbrp-sheet/.ringbrp-chat/.ringbrp-window
and never on :root. A journal inherited no tokens, so every var() silently became
nothing. A rule that HALF applies is not a specificity problem — I spent three attempts
treating it as one, including a version bump on a cache theory that was wrong.
Branded: primer, rulebook, starter GM text and handouts. Scoped by flag, so other
modules' journals are untouched. Version 0.9.0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Four real defects, each verified against the source before acting on it.
Trade expertise was coupled to agency rank. A probationary burglar came out at 35-50%
and a veteran at 65-80%, as though fifteen years of picking locks were something the
department conferred. TRADE_BANDS is now fixed at 50-65/30-50 at every rank, and
INDUCTION scales with service instead (20-32 probationary to 45-60 veteran) because
that half genuinely is the department's. The two axes were the wrong way round. This
is the thing I flagged myself after PAPER HARBOUR and then left alone — flagging a
defect is not the same as fixing it.
Bonus points were sprayed across every skill in the game. grantFullSkillList runs
immediately before the loop and puts all fifty-nine skills on the sheet, and the loop
picked from actor.items, so a veteran's ninety points landed anywhere. The comment two
hundred lines above has always said "over the core skills"; the code never did.
"Random species" passed "baseline" into generators that support random perfectly well.
No behavioural tests. The strongest point in the review: the three guards are static
and none of them can tell whether a rule is READ, which is the only kind of defect this
project has ever shipped. tools/check-behaviour.mjs now runs 28 deterministic tests,
gated into the build, covering R-231/232/243/245/246, graded defences and the lamp
rule. Proved it bites by re-breaking R-246.
The register moved to postings.mjs, a Foundry-neutral module the engine, rulebook,
guards and tests all import normally — they were previously pulled out of the engine
with a regex and eval, which worked and was a trap. My first version of that used
`export … from`, which re-exports without local bindings, so ROLES was undefined and
the system threw on init: node --check passes that, loading it in Foundry does not.
Also: the contact doc comment still said "only OFFER moves standing"; check-kits
accepted mas/app, which are the DISPLAY names of siz/cha, so a posting declaring one
would have passed and produced an undefined characteristic; package.json disagreed with
the manifest; README counts were three revisions stale and are now generated at build.
Deferred with reasons: splitting the 6,700-line engine into modules. Right, and a
multi-session refactor whose risk is exactly the silent breakage demonstrated above.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A pier that closed in 1974, a beacon still transmitting, and a probationer recruited
out of a city with a caution the department has quietly lost. The generator's gap —
somebody uses that agent's name before it is given — landed on him in phase 2, and he
held it on Fast Talk 14 against 48 while the Field Lead missed the read.
The case turned on a warrant card: the keepers of the ground want relieving by somebody
official enough to take the duty on, and every agent carries exactly that. Bargain 27,
favourable, rolled 33 — impression -1 to +1. The one unambiguously his moment was the
log the first team locked in behind them: 11 against Sleight of Hand 50.
R-246: a fumbled greeting cost nothing. contactOutcomes has said fumble/signal -1 since
the social pillar was built, and impression was adjusted only inside the `offer` branch
— so the -1 was computed on every botched greeting and thrown away. Impression now
falls on a fumble at any stage and still only rises on an offer; the narrower fix
matters because read's delta counts FACTS LEARNED, not standing, so applying the delta
always would have paid the team impression for doing research.
Also logged: a probationary criminal is out-sneaked by a career Field Lead (47 to 60)
because trade skills use the agency tier bands — defensible, flagged, not changed. And
one invented step of my own: I rolled Transposition to get them home after the
extraction phase had already put them out.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
TRADES: ten ordinary jobs the department recruits from — construction worker, doctor,
professor, engineer, law enforcement, IT specialist, scientist, linguist, entertainer,
criminal. They are not postings. A posting is what the department made of you; a trade
is what you were before any of it.
A trade character is built in two halves. The trade is genuine expertise on the same
bands a posting's skills use — a doctor is a proper doctor. INDUCTION goes on top at
25-40%: Tradecraft, Anomaly Lore, First Aid, Firearm (Pistol), Dodge, plus a sidearm, a
vest, cordon kit, a cover identity and a ward. The band is low on purpose; six weeks is
not a career, and that gap is most of what it feels like to play one.
Induction never demotes: a former police officer keeps pistol 58 from the trade rather
than being re-taught it at 26.
The creation dialog gains a "Recruited as" switch with its own trade list and card
(which shows both halves), and check-kits now holds trades and induction to the same
standard as postings — both new guard paths verified by breaking them.
Rolling them yourself: a tickbox that walks the eight characteristics one at a time,
each roll announced to chat so the dice actually fall, "Take them" locked until all
eight are down. A hand-rolled character is taken exactly as it fell — no best-of-three
on the key stat, no species shift. Verified both ways.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both postings draw a riot shield, and both are trained to use it — issuing one without
the skill would have been R-212 again with a different item, the Antiquities Officer
who drew a flintlock and rolled 5% with it.
melee_weapon:shield is SWAPPED into each support list rather than added, so five core
and five support are preserved and the shield arrives without a free power bump.
Containment drops stealth (a posting whose job is being the thing in the doorway was
always the least stealthy in the department); the Night Warden drops navigate (they sit
with one site all night).
check-kits now requires the Shield skill for an issued shield, the same way it has
always required training for an issued weapon. Verified by removing the skill and
watching the build refuse.
Four generated agents: shield skill at 25-30%, nobody encumbered, though a Containment
officer lands at 32.9 of 33 kg. The shield ships slung — raising it is the choice, and
for the Warden it is the difference between 2 points of armour and 5.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A shield is the one piece of armour you hold, and it protects you exactly as much as
you are currently holding it up. Raised, its points apply to what it covers and it can
parry on a new Shield skill. Lowered, it is weight. The price of keeping it up is that
it occupies a hand and you are shooting around it: -20% to your own ranged attacks,
printed on the card like everything else. Only one shield goes up at a time.
Seven of them, 2-point buckler to 6-point ballistic shield; the pavise and barrier
plate cover legs too because they are walls you carry.
`degradation` finally does something — it has been on every armour item since the packs
were first built and was read by nothing. A blow costs the shield a point of wear for
every step it stood above an ordinary success, so an ordinary hit costs nothing, a
special 1 and a critical 2. At its limit it comes apart, drops, and will not be raised
again.
Two defects found by driving the real functions rather than reading the diff, both
introduced by this change:
- Every shield defence quietly rolled DODGE. "shield" passed through
defenceTypeAllowed unchanged, so neither parry branch matched and it fell through.
Invisible in the card; it showed up as eight rolls at a supposed 85% returning six
failures. Taking a blow on the shield IS a parry, so it is now a flag on a parry
rather than a defence type of its own.
- The wear rule was unreachable: it fired only on a clean stop, but under graded
defences only a critical fully stops a critical, so a shield would never have taken
a scratch. Wear is for what the shield ABSORBED — dragging a critical down to a
special is exactly when shields splinter.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Asking for the type of armour per location turned out not to be a display request.
Every equipped piece added its points to EVERY location, so a Brodie helmet protected
your shins and a cuirass protected your skull — with a catalogue containing sallets,
lobster-tail helmets and three cuirasses, that could not be printed without the sheet
saying something visibly false.
Armour now declares coverage as a named set rather than a list of locations, because a
piece has to fit whatever body wears it: all, torso, torsoArms, torsoLimbs, head. The
sets expand to location KINDS, so a cuirass covers a baseline torso and a vesh trunk
and ridge without either knowing the other exists. Unstated coverage is `all`, so
anything that does not declare behaves as everything did before. Eighteen of the
twenty-five catalogue pieces are not whole-body and now say so.
The trap was double counting: hitLocationRoll subtracted the global worn total PLUS
the body's own armour at that location, which was right while armour was global and
becomes a double count the moment a location knows its own pieces. It reads the
location's total and nothing else, verified by firing fourteen hits of 10 damage
across every location and asserting damage applied == 10 - that location's armour.
A single ARMOUR number no longer exists, so the header shows the torso with "0-8 by
location" beside it when the rest of you is not that. This is a real difficulty
change: limbs are frequently bare and limbs are 12 of 20 on the melee table.
Coherence moves out of the derived strip into the vitals at hit-point size, with its
band under it and the box reddening as it falls.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was no way to ready a weapon. The strip under the characteristics reads
`equipped`, and the only toggle-equipped control on the sheet was on the ARMOUR list —
a weapon could only be readied by opening its item sheet and finding the tickbox
there. The weapons table now carries the same toggle, the row is tinted when readied,
and a line above the table says what the control does.
The tab runs in the order it is used: weapons, armour, defend, reaction, body last.
Weapons lead with 40px art and a display-face name, having previously sat below two
screens of anatomy and reaction arithmetic.
The figure is a partial, drawn in three places — header thumbnail, combat tab, anatomy
tab. Three inline copies would have been the template-layer version of the defect
check-rules exists to prevent: a location present in one drawing and missing from
another.
The header carries a 34px figure and every location with its damage and the armour
over it, so "how much armour is on the part that just got hit" is answered on the main
page without changing tab.
Also fixed: `.ringbrp-sheet a` outranks a bare `.rb-equip`, so an unequipped toggle was
painted white and read as lit — true of the armour toggle too, since it was added.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The goods yard fight made the case: three agents inside the same pool of light shot at
-50% while the fourth, four metres away, shot at -10%.
A lamp now has a reach, per item rather than global, because a weapon lamp and a
vehicle searchlight are not the same offer — 4 m for cold light strips, 6 m for a
weapon lamp, 10 m for the issue field lamp, 30 m for a roof searchlight. Anyone inside
it is in the light and the card names whose lamp it is, so both halves of the rule
travel together: the pool is one position and the whole group is standing in it.
Measured from the tokens. The shot that started this — no lamp of her own, four metres
from somebody else's, in pitch dark — goes from 20% to 60%, while an agent
twenty-five metres out still eats the full -50%.
An UNKNOWN distance is explicitly not lit: Number(null) is 0, so an unmeasured
distance would otherwise have read as standing on top of the lamp and lit any scene
with no tokens placed. The dialog carries a tick instead, pre-set when the canvas could
measure it and the GM's answer when it could not.
Note: template.json is read when Foundry loads the system, so a deployed server needs
a restart and not just a pull before the migration can stamp the new field.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ammunition was charged once before the shot loop rather than once per shot, so the
Webley put two rounds out and the cylinder went down by one. That is the exact
dishonesty the burst rules exist to avoid, and it landed on the mode that is supposed
to cost the most. Charged per shot now, and the loop stops when the weapon runs dry
part way through the action.
Found by playing the four modes side by side in the goods yard — one agent per mode,
all four at 60%, so the fight read the mode and not the shooter. Full log in
docs/REVIEW_LOG.md, including two findings left open: burst options are close to
unselectable once the light is bad, and a lamp currently lights only its carrier while
three agents stand in the same pool of it at -50%.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Selectable fire, with the modifiers on the choice
Every weapon has carried a fireMode since the packs were first built and nothing
read it: a musket could rip a ten-round burst and "rapid" bought a weapon nothing.
FIRE_MODE now gates the burst rules and carries its own attack modifier — slow +10%
and then you work for the next one, fast a second shot at -20% to both, rapid
bursts, beam +5% and it can be held on the target for damage instead of hits. The
gate lives in burstAttack too, so no macro can route round it. `fast` was on five
catalogue weapons and was not in the system's list of modes at all, so re-saving one
of them silently blanked it; the list is derived from the rule now.
burstAttack shipped complete and was reachable from nothing. It is the resolution
path the selector chooses, and takes the dialog's whole stack rather than charging
the player twice for the same burst.
Sights and lamps that apply themselves
A sight is graded by range band, so a telescopic sight is a -10% liability inside
ten metres and worth +20% at extreme, and it only counts if it fits. The band is
already known when the modifier is wanted, so nothing is selected and nothing is
forgotten. The dark costs something now; a carried lamp buys it back to dim, never
to daylight, and the card says it shows them exactly where you are. A migration
fits gear that predates the fields, matched on the stamped key rather than by name.
The damage card
The last card still wearing Foundry's stock dice styling — it posted a bare Roll and
let the core template dress it. It renders through the module's own card now, with
the Roll still on the message so dice stay inspectable.
A rail instead of a strip
Eight tabs across an 820px sheet compressed to 11px type. They run down the side
now, one line each, with counts as badges; the sheet is 152px wider to pay for it.
Also fixed: any weapon with a Coherence cost could not be attacked with AT ALL — the
handler re-read the weapon after an await, when currentTarget is already null, and the
attack died on a TypeError with nothing shown. And the duplicate-rule guard failed an
honest table because FIRE_MODE and speedBands share two key names; it wants a majority
now, and prints partial overlaps rather than swallowing them.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
R-228: Ambidextrous was a compulsory build. 0/-20 gave a full-strength main hand
AND a cheap second attack. It now buys consistency, not a free attack: -20 in both
hands against -20/-40 untrained.
R-229: full auto was a firing squad. Ten independent hits off one critical, each
with its own damage, location and Major Wound check. Hits capped at 3/5/7, and a
burst is ONE wounding event however many rounds connect.
R-230: Engines deleted the pressure it existed to create. Guns +2 and Helm +1
against a vent of 3 made a fighting round heat-neutral, so Heat only mattered when
the engineer failed. Venting is now 2/3/4.
Also: falling halving no longer stacks (soft + controlled quartered the drop);
blast has one formula floored once, so the answer no longer depends on call order.
And the structural note — "giving everyone a roll is not the same as giving
everyone a decision". Sensors, Damage Control and Medical now have mutually
exclusive modes that bite in the engine: mark/spoof/read, patch/brace,
restore/steady.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Stress test first: 150 characters across every posting, tier and species against
fourteen invariants each, then the edges (characteristics at 1/3/21, every
location destroyed, twelve pikes carried, hp set to -99).
R-227: a destroyed head was a nap. The printed effect has always read "For
anything that keeps its brain there, this is death" and the code set unconscious
and stopped. destructionOutcomeFor() now says what destruction means.
THE WORLD: falling (a die per 3 m, armour does not apply), drowning (CON rounds
then a point a round, straight past the Major Wound threshold), fire (a condition
with a size; armour helps on the round you catch and never after), explosives
(one roll at the centre, shared by band, cover beats armour).
AUTOMATIC FIRE: one roll, the success level says how much of the burst arrived,
and the rounds are spent either way. TWO WEAPONS: -20/-40, or 0/-20 with the new
Ambidextrous talent; the off hand takes the lighter weapon and nothing over 2 kg.
BESTIARY: 21 entries in three families — folklore, horror, and what comes back
from further along — each with characteristics, natural armour, tactics and a
POWER written as a rule with a cost.
SPACE: eight stations, each on a skill somebody already has, so the Physician has
a chair. Range is a band; the helm moves one a round, in or out. Heat is the
pressure and took two rounds of playtest tuning to stop being a countdown.
64 rules, 198 spot-checked formulas, a 12-page rulebook in reading order.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
My own R-221 fix overshot. A Containment Officer whose Tradecraft had caught a
stray bonus point sat at 12% against a base of 5 — technically trained — and led
every phase ahead of a Rigging Officer on 53% Navigate. Tradecraft still wins ties
and wins when genuinely better; it no longer wins when plainly worse. The
Containment phase went 6% -> 26% on the same team.
Found playing GLASS LANTERN with the historical gear: salvaged polearms and
slings correctly arrive at 5% because nobody trains them, and maille over
brigandine (AR 8) reduced four utility-knife hits to zero damage each.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The generator was already writing the timeline, the cast and the texture and
filing all of it behind the GM screen. New PLAYERS page: a read-aloud opening,
what it is like there, what is known so far, who is there and what they want —
but never what they lie about. Page ownership is now declared by the page rather
than guessed from its index, which would have hidden any second player page.
Historical range: 38 weapons (from 6) and 14 armours (from 2), each with its
period stated, from arming swords and longbows through matchlocks and Brown Bess
to the Lee-Enfield and a trench club. Five new skills to hang them on, including
Firearm (Muzzle-loader), because a muzzle-loader is not a rifle.
275 icons; every weapon maps to a real skill and every item has art. Catalogue is
206 items across four eras.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Every case carries a "window closes" clock whose stated cost is THE WAY HOME and
whose steps are "the margin narrows / the return is Difficult / the return is
aimed at -30%". Nothing ever read it, so the phase whose job is getting out had
no consequence of its own and the GM had to invent one.
Extraction now advances that clock: failure and fumble narrow the window, a
critical opens it back up, and returnCrossing() applies the penalty alongside the
classification modifier and the Coherence band. 0/-10/-20/-30, Difficult from two
steps.
Also: legs now store their `kind`. The extraction check matched on the terrain
prose and worked only because the string begins "Extraction —".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Hit points clamp at zero, so further damage to somebody already there changed
nothing — and a STABILISED agent absorbed it forever, because the count was held
and there was nothing else left to move. You could empty a magazine into someone
bleeding out and the system would not notice.
Damage at zero now breaks the stabilisation and costs a round of the count, and
hitLocationRoll calls died() when that meets the limit.
Found by playing LOW VERGE until it killed somebody: two agents who were
medically stable died in the water on a failed tidal extraction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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>
The ramp made every phase after the first Difficult (halving the lead's skill) and
stacked a cumulative -5% on top. Separated in phaseRampFor() in rules.mjs:
difficulty belongs to the phase (only Containment is Difficult, and it does not
also ramp), the modifier is attrition (-5 a phase, capped at -15).
lead 55% was 55 -> 22 -> 17 -> 12 -> 7 now 55 -> 50 -> 45 -> 27 -> 40
Over 20,000 simulated cases with destitution modelled, phases passed roughly
double and destitution incidence roughly halves.
R-222: resolveLegDialog passed no skillFamilyId, so the choke point could not
resolve the skill item and leading a phase never earned a tick — Tradecraft, the
skill the job most uses, could never improve.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bestIn("tradecraft") ?? bestIn("navigate") never reached Navigate, because every
character carries every skill and skillRating() returns the printed base rather
than null — so the first lookup always found somebody. A team of postings that
train Navigate and not Tradecraft was led by whoever had the highest UNTRAINED
Tradecraft, which is 5%, putting phase three at 1%.
TRAINED now means above the printed base. Measured on a Pathology / Overwatch /
Warden / Materials team: lead 5% -> 34%.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Since 0.6.1:
- VEHICLES as their own Item type: crew, seats, cargo, hull, armour, range,
terrain and the skill that works them, with speed as a band. 14 of them, from
the pool car and the Custodian van to a sealed crawler and the carriage that is
already parked outside wherever you were going to go.
- STORES roughly doubled to 118 gear items across four eras — standing issue and
paperwork, transport stores, and the forward stores Registry will not hand a
probationary officer. Catalogue now 175 items, 231 icons.
- Agents leave creation properly equipped: standing issue, the posting's kit,
what seniority adds, and one personal effect that is theirs and not the
department's.
- All 25 postings now describe themselves in the creation dialog.
- BORROWED AUTHORITY, the access subsystem. No hacking skill and nothing to break
into: access is a named credential with a scope, a Trust that erodes, and red
flags describing how its real owner behaves. Inside scope there is no roll. Two
tiers beyond is impossible at any skill. Coherence widens a record, and pushing
one past what its Trust will carry merges your file with theirs.
- Defences graded by level, and damage now rolls at the level a blow landed at.
- Dodge's DEX x 2 base is finally evaluated; it read 0% for most postings.
- Brawl is a fallback rather than a peer of the weapon in hand.
- check-lang guard: one key that was both a value and a branch silently
un-localised the entire system.
- The case generator is reachable from the Actor Directory, and no longer puts
every character in the world on a new case.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A Foundry VTT game system: Basic Roleplaying d100 in a drab British agency that
deals with crossings, where reality keeps a record of what belongs where and can be
made to get it wrong.
Contents:
- rules.mjs as the single authority for every rule formula, with 40 rules and 132
spot-checked values. Nothing may restate a formula it defines.
- 25 postings, each with a key characteristic, trained skills, talents and its own
kit; a 175-item catalogue across four eras; 231 generated icons.
- Reaction Lanes initiative, re-rolled every round including the first.
- Coherence, and the Quiet Arts, which only ever arrive from a crossing gone wrong.
- Graded defences: only a critical stops a critical.
- Borrowed Authority — access as a record rather than a hacking roll.
- A case generator, and a rules journal generated from rules.mjs so the book cannot
drift from the code.
Built compendia are committed so a remote Foundry needs only the files.
node_modules is not; `npm install` restores it for rebuilding content.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
