Decoded/disassembled finding from the TeslaRel410 side, verified against a live DOSBox BTL4OPT pod driven by this console: the post-mission egress window is a compiled ~3 s (stage-1 timer), not ~30 s, and byte-identical across all four BTL4OPT builds. Marked won't-fix -- the floor egress lamps no longer exist on any surviving cockpit. Console takeaway unchanged: send StopMission promptly at timer end; the pod handles its own (short) close, no egress delay to implement. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
battletech-port — hand-off package
Everything needed to add BattleTech support to the modernized TeslaConsole
(in the TeslaSuite repo), mirroring its existing Red Planet implementation.
Assembled in the TeslaRel410 repo from the Mac 4.10 console decompilation + the
game's own data. Transplant this whole folder into the TeslaSuite repo and
implement from the spec there (that repo can build the .NET solution).
BATTLETECH-PORT-SPEC.md— start here. The full port spec: shared Munga/1501 spine, the BattleTech egg format + the BT-vs-RP field diff, the RedPlanet→BattleTech class map, the shell de-hardcoding, theBTConfig.xmlcatalog + data sources, open questions, and verification.reference/cavern.egg— console-generated BattleTech egg (golden field reference).reference/TESTARN.EGG— 2nd BT egg (shows multiple[Role::*]blocks).reference/RPConfig.xml.template— the RP catalog XML to mirror asBTConfig.xml.reference/L4PLASMA.HPP— the pod plasma-display class the egg bitmaps target.
Context: ../CONSOLE-4.10-DECOMP.md (the Mac console decompilation this builds on).