arcattackandClaude Opus 4.8 cc6639d952 projweap: correct the msg-2 jam claim (it CAUSES jams, decomp-verified) ...

HandleMessage @004bcabc: message 2 -> SetLevel(weaponAlarm, 5) -- a
malfunction INDUCER, not an unjam; the state-machine comment had it
backwards.  There is NO in-mission unjam in the binary (jams clear only
at ResetToInitialState = mission reset/respawn), and the EJECT cycle is
the anti-cook-off ammo jettison (DumpAmmo -> NoAmmo), not an unjam.
The old 'unjam delay' follow-up suggestion is retired as unauthentic.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-23 10:33:37 -05:00

..

fwd

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

glass

Walk-up callsign/mech request: join menu -> relay -> the session egg

2026-07-22 13:58:51 -05:00

original

SeekVoltageGraph: full reconstruction -- the eng-page POWER graph + top-box eraser (Gitea #11)

2026-07-19 20:27:39 -05:00

reconstructed

projweap: correct the msg-2 jam claim (it CAUSES jams, decomp-verified)

2026-07-23 10:33:37 -05:00

btl4main.cpp

Connection audit: every connect/disconnect scenario handled + verified

2026-07-23 09:23:23 -05:00