Asking what an AmmoBin does with the gun heat alarm that 5.3.132 brought
to life turned up an entire mechanic that has never run here, dead for
two independent reasons: the watch link was unbound so the mirrored
alarm never left NormalHeat, and our AmmoBin has no Performance at all
where the binary installs one.
The trigger: when the gun a bin feeds goes into HEAT FAILURE, the bin
latches a randomised countdown. Heat clearing cancels it; expiry
destroys the bin and detonates it. The damage is authored per round and
scaled by rounds remaining, so a full bin guts the mech and a nearly
empty one barely coughs. The blast is then SHARED -- divided by the
number of targets, not applied whole to each -- and every victim is
announced with the authentic string "ammo explosion damaging <name>",
which is what confirmed the whole reading.
One identity is deliberately left unpinned: what the collector iterates
and what its 0x4e filter selects. It is not a classID, and the
per-victim reads look more like damage zones than subsystems. Guessing
would produce a plausible mechanic that damages the wrong things --
precisely the failure this project keeps catching -- so the collector
gets read first and the whole thing lands in one piece.
Worth noting the shape: two dead systems in series were hiding a third.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CydandClaude Fable 5
f760d16558