BT411

Files

T

Joe DiPrimaandClaude Fable 5 f450f9cce0 Oracle-return verification pass, both CONTRADICTS run to ground against the binary same night: #176 the seek-gear square law is the Emitter ctor's OWN calibration (@004bb120 EC = E/(0.5 seekV[rec]^2) [T1]) and the authored table (LLaser {6000,7000,8000,9900}/10000, rec=8000) yields the REAL ladder 56/77/100/153 -- seek 3 IS the published calibration point exactly as Oracle said, seek 4 is an unclamped OVERCHARGE gear (logged 5.80 > authored 5.0 proves it), and the guide's 'half-charge = quarter' example was the wrong part (master guide corrected with the real ladder + the downshift-for-rate / seek-4-alpha doctrine). #177 the BTPlayer ctor stamp table read verbatim (@004c0bc8: +0x260 = level>=2 -> heat at veteran AND expert in 4.10 [T1]; +0x274 = the raw level; +0x26c = standard|veteran) -- the port is faithful; Oracle + the 4.0 manual describe the earlier machine (a genuine 4.0->4.10 balance change); ticket premise corrected (the KB already carried the stamp values -- 'writer never read' was another check-own-history strike). experience-levels.md upgraded to the writer address; #176 open residue: per-weapon gear-fraction variance.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bw71WVsccjwW7uKRg4aWD

2026-08-13 23:03:32 -05:00

feedback

Oracle's weapons-guide return ingested -- the file-edit feedback loop WORKS (first curated .txt return, staged to docs/feedback/ + diffed against the distributed bb4094f copy). Fourteen answers: two CONTRADICTS filed (#176 seek-gear damage swing -- the authored seekVoltage gear table has never been read and may reconcile both; #177 veteran heat -- witness + 4.0 manual say expert-only and the player+0x260 writer is unread [T4]). Confirmed by witness: the out-of-range damage cliff, gear-wrap safety + downshift-for-rate doctrine, charge persistence across generator reassignment (port audit item), splash, SRM 800 pip (450/800 CLOSED), single-tap jam eject, missile speed-drop pre-endorsed. New era gifts: the PPC MFD collapse-to-vertical-line reference photo (ARCHIVED before the Discord link expires -- the visual target for Cyd's ppc-sync pass), PPC auto-mode generator-flip color, AFC no-visible-projectile memory (needs corroboration -- our tracer code is real, its VISIBILITY on the shipped machine is now an era question), the Gauss carrier's variant name (Mischief), and two YouTube videos with the real incoming alarm audible (#83 ear-A/B references).

2026-08-13 22:53:08 -05:00

ASSET_PIPELINE.md

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

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

AUDIO_FIDELITY.md

KB: #83 paperwork -- gotcha 33 (a fix wired into a blocked transcription: compiles, reads faithfully, never runs; rules: fixes land in the LIVE path, inert transcriptions get an explicit banner, a doc-header FIXED is a claim not evidence, the bench must fail first). decomp-reference section 5 gains the recovered alarm rule (@004bf5b4 ctor socket-registration into target+0x418, @004a9b5c first-member read, death-path list empty, reset 0/FLT_MAX) + env rows BT_INCOMING_LOG / BT_DESIGNATE. AUDIO_FIDELITY F7 corrected: the July fix was dead code; the true fix + bench numbers recorded, field-verify Friday. Tracker #83 comment 1786.

2026-08-13 22:28:22 -05:00

BGF_FORMAT.md

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

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

BT_SOURCE_STATUS.md

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

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

CONTROLS.html

keylight: unship it -- opt-in (BT_KEYLIGHT=1), gone from all player docs

2026-07-26 17:06:00 -05:00

CONTROLS.md

keylight: unship it -- opt-in (BT_KEYLIGHT=1), gone from all player docs

2026-07-26 17:06:00 -05:00

CREDITS.md

CREDITS: the printed credits page (via VGL Lynx) -- definitive roster

2026-07-21 23:38:25 -05:00

DIST_LAYOUT_PLAN.md

Proposal: ship the authentic single-folder dist layout (docs only, NOT implemented)

2026-07-26 02:49:30 -05:00

GAUGE_COMPOSITE.md

sec-surface phantoms: #48 wrap lit idx-254 art in live armor colors

2026-08-11 20:29:20 -05:00

GEN_WARNING_AUDIT_20260811.md

context-system housekeeping: the 2026-08-11 wave lands in the digests -- router Current-front refreshed + the four audit ledgers listed + the docs/ AI-vs-human split labeled; test-harness gains the standing bench-suite table (kd4/kd8/proj_ttl/gen_edge/xfire + rig notes: clone-the-pilot-page pattern, only map-defined dropzones are valid); multiplayer gains the K/D authority + #45 mirror section with the 4/8-node stress record; combat-damage gains the synchronous-death-transition section (gotcha 25 pointer, tripwire semantics); open-questions replicant-delivery entry gains the 0-of-35-deaths bench datapoint (needs field conditions); the #154 multi-agent audit lanes preserved from session temp as docs/GEN_WARNING_AUDIT_20260811.md (with the no-speech retraction lens noted). checkctx: CLEAN.

2026-08-11 18:37:59 -05:00

GHOST_MECH_ANALYSIS.md

#81 follow-ups: peer warp must not stomp the POV vortex; panel draw probe; mech3 ghost symbols

2026-07-30 10:10:29 -05:00

GLASS_COCKPIT.md

port-layer papercuts for the playtest: #69 Denkou rename, #71 plasma X=minimize, #157 round-end UX (foreground handoff + lastrun clean-exit markers + bat sign-off rewording); tester-facing open-issues handout (docs/) + field-log anatomy notes

2026-08-10 11:29:01 -05:00

HANDOFF.md

handoff: fold in the orphan investigation, the launcher fix, and what it means for the release

2026-07-27 16:08:10 -05:00

HARD_PROBLEMS.md

P7: subsystem-tree alarm unification -- the whole PoweredSubsystem weapon/power subtree is byte-exact

2026-07-07 11:49:58 -05:00

INPUT_PATH_AUDIT.md

KB housekeeping sweep: end-of-arc staleness purge (2026-08-06)

2026-08-06 10:22:50 -05:00

KD_CHAIN_AUDIT_20260811.md

KB expansion from the #162 audit: full five-agent evidence record preserved (docs/KD_CHAIN_AUDIT_20260811.md), decomp-reference gains the audit's hard addresses (VehicleDead arm internals, the +0x290 never-set byte-scan, the DropZoneReply clear pair, the 2|9 vs 9|10 latch asymmetry), the stale 'inflicted-only' claim swept (mech.cpp), cross-links + KD plan marked historical

2026-08-11 00:27:47 -05:00

KD_SCOREBOARD_PLAN.md

2026-08-11 00:27:47 -05:00

MISSION_END_AUDIT_20260811.md

#163 round-end freeze + hang-on-exit FIXED: bare ExitProcess ran DLL detach with live Steam threads (no SteamAPI_Shutdown existed anywhere) and intermittently deadlocked -- the dead process's fullscreen frame squatted on screen while its menu child hung in SteamAPI_Init against the wedged sibling (field-captured, ZEUS 22:12:38). Ordered exit everywhere: flush forensics, BTSteamNet_ShutdownAll BEFORE the child spawns, hide our windows, TerminateProcess (detach skipped, deadlock structurally unreachable). Audit ledger: docs/MISSION_END_AUDIT_20260811.md (also yields #156 's fade root cause). Bench: relaunch_bench.sh -- old pids dead, menu children clean

2026-08-11 01:58:23 -05:00

MOUSELOOK_PLAN.md

Mouse buttons are bindable; mouse LOOK scoped (not built)

2026-07-26 09:06:58 -05:00

OPEN_ISSUES_FOR_TESTERS.txt

#172 corrected same day (user challenge upheld): the 6px-strip-was-invisible framing RETRACTED -- [lampblink] receipts prove the surround paints the flash at a metronomic 125ms (code-identical loop in 913), and Elengil's layout receipts show the stock surround with the lamp on screen. The real mechanism is EXPECTATION: a generator leak lights the button BY THE RADAR (authentically the only place -- no MFD carries a generator-leak indicator) while testers watch the MFDs. Ships: handout WHERE-TO-LOOK entry (#172 ) + the refined #136 voice-loop wording; the alert ring is GATED OFF by default (BT_ALERT_RING=1 keeps it available if Friday proves testers miss the lamp even knowing its location); [lampblink] shade-transition receipt added (BT_LAMP_LOG). Era question posted for Oracle: how prominent was the pod's physical generator button light?

2026-08-13 02:14:13 -05:00

OPERATOR_GUIDE.md

sweep the knowledge base up to this session: log day, crash symbolization, a misnamed accessor

2026-07-28 19:23:29 -05:00

P3_LOCOMOTION.md

the visible limp (#78 ): there was never a jump-jet clip set -- the 'Airborne' drivers ARE the gimp gait machines

2026-07-29 15:49:39 -05:00

PROGRESS_LOG.md

context-system: complete migration -> CLAUDE.md is now a 160-line router (zero context lost)

2026-07-07 22:19:50 -05:00

RAM_LEAK_AUDIT_20260811.md

#128 terrain-ram instant coolant leak FIXED at the eligibility tag: GUID 0x50e590 is the AGGREGATE BANK's node (0xBBE), not the HeatSink base family -- the family-wide reading made every coolant-bearing subsystem (myomers, condensers, reservoirs...) rattle-eligible, so one over-floor ram sub-hit sprang an instant leak (field: Michael's 3 rams all 'Myomers condition 2 SET' -- a subsystem 1995 can never select). Authentic set {HeatSinkBank .30, Gyroscope .35, Torso .25}; scrapes remain free via the byte-anchored 0.5-pt floor (the 30k-lines/night [crashdmg] spam now sampled). Audit: docs/RAM_LEAK_AUDIT_20260811.md. Bench ram_bench.sh: 20 rattles, zero ineligible strikes

2026-08-11 02:33:14 -05:00

RECONCILE.md

KB sweep: retire the three claims that WERE the scoring bugs

2026-08-07 11:22:47 -05:00

RESOURCE_AUDIT.md

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

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

RESPAWN_REARM_PLAN.md

KB housekeeping sweep: end-of-arc staleness purge (2026-08-06)

2026-08-06 10:22:50 -05:00

REVOLVING_DOOR_PLAN.md

Revolving-door mode: feasibility findings + two-phase implementation plan (docs only)

2026-07-24 15:05:06 -05:00

STEAM_TEST.md

KB: step-4 closeout -- Steam wire documented, live-test procedure, router

2026-07-18 00:05:51 -05:00

SUBSYS_PLAN.md

myomer system COMPLETE -- the 'WAVE 6 mover cutover' was a phantom built on

2026-07-31 09:17:31 -05:00

VEHICLE_SUBSYSTEMS.md

Gauges: trigger-config joystick is LIVE -- @004c6ee0 is LinkToEntity, not SetColor

2026-07-21 08:49:58 -05:00

WAVE_PLAN.md

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

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

WEAPONS_DRIFT_AUDIT.md

KB: #175 paperwork -- drift-audit row 12 gains the static-world addendum (solid-tree sweep landed, 345 struct-class bench bursts, owner dispatch, the [T3 minor] fuze-vs-world same-frame ordering note); env-gate table gains BT_WORLDHIT + the BT_DESIGNATE HUD-ring clarification. Tracker #175 comment 1793.

2026-08-13 22:45:44 -05:00

WEAPONS_FIELD_GUIDE.txt

Oracle-return verification pass, both CONTRADICTS run to ground against the binary same night: #176 the seek-gear square law is the Emitter ctor's OWN calibration (@004bb120 EC = E/(0.5 seekV[rec]^2) [T1]) and the authored table (LLaser {6000,7000,8000,9900}/10000, rec=8000) yields the REAL ladder 56/77/100/153 -- seek 3 IS the published calibration point exactly as Oracle said, seek 4 is an unclamped OVERCHARGE gear (logged 5.80 > authored 5.0 proves it), and the guide's 'half-charge = quarter' example was the wrong part (master guide corrected with the real ladder + the downshift-for-rate / seek-4-alpha doctrine). #177 the BTPlayer ctor stamp table read verbatim (@004c0bc8: +0x260 = level>=2 -> heat at veteran AND expert in 4.10 [T1]; +0x274 = the raw level; +0x26c = standard|veteran) -- the port is faithful; Oracle + the 4.0 manual describe the earlier machine (a genuine 4.0->4.10 balance change); ticket premise corrected (the KB already carried the stamp values -- 'writer never read' was another check-own-history strike). experience-levels.md upgraded to the writer address; #176 open residue: per-weapon gear-fraction variance.

2026-08-13 23:03:32 -05:00