Files
TeslaRel410/restoration/source410/BT/BTCNSL.NOTES.md
T
CydandClaude Fable 5 63312e07f9 source410: literal 4.10 source reconstruction + BC++ 4.52 fleet toolchain archived
- BORLAND/: Borland C++ 4.52 (chosen over 4.5 by byte-match: CODE/RP/CW32.LIB
  is identical to 4.52's install lib). BCC32/TLINK32/TLIB/MAKE run natively on
  Win11; CODE/BT/OPT.MAK is the shipped BTL4OPT.EXE's exact flag recipe
  (extender = Borland PowerPack DPMI32, not Phar Lap TNT).
- restoration/source410/: the literal 1995-form reconstruction of the missing
  BT game source (never mixed into CODE/). Round 1-3 state:
  * 6 of 10 surviving original TUs COMPILE CLEAN under the period toolchain
    (BTMSSN, BTCNSL, BTSCNRL, BTTEAM, BTL4MODE, BTL4ARND) - first builds
    since 1996.
  * BT_L4/BTL4APP.CPP pilot reconstruction: 12/12 functions, Fail() lands on
    its binary-recorded line 400 exactly.
  * BT/BTCNSL.HPP: console wire IDs recovered from the binary's ctors
    (Killed=9, Damaged=10, ScoreUpdate=13, DeathWithoutHonor=15 [T1];
    TeamScore=12 flagged [T4]).
  * MUNGA/: 8 engine-header backfills back-dated from the BT412 WinTesla tree
    (VDATA numbering decomp-verified; AUDREND's OpenAL-era virtual removed -
    the period compiler is the drift detector).
  * Tooling: backdate.py (WinTesla->1995 header transform), compile410.sh
    (per-TU verification sweep under authentic OPT.MAK flags).
  * README: corrected roadmap - MECH.HPP is the capstone grown with the mech
    TU reconstructions; BTREG.CPP green = the header-family milestone.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-19 07:33:26 -05:00

1.9 KiB

BTCNSL.HPP — reconstruction notes (2026-07-19)

The header for the SURVIVING BTCNSL.CPP (whose own banner is the stale clone "cnslmsgs.cpp" — the HPP banner mirrors it). Class shapes/member order recovered from BTCNSL.CPP itself; layout cross-checked against the binary's ctors.

THE WIRE IDs ARE BINARY-PROVEN [T1] — a discovery with cross-project value (the TeslaSuite console port spec still lists BT's in-match message set as "confirm"):

message ID evidence
ConsolePlayerMechKilled 9 ctor @4c18f4 ([1]=9, size 0x14, 2 HostID fields) [T1 value / T3 name-pairing by source order]
ConsolePlayerMechDamaged 10 ctor @4c1944 ([1]=10, size 0x28, the unique 7-field payload; field ORDER = player, damager, loss, pointsTransfered, zoneIndex, zoneDestroyed, weaponIndex — decomp param mapping matches the CPP's member order) [T1]
ConsoleBTTeamScoreUpdate 12 ⚠ [T4 GUESS] ctor NOT FOUND in the image (gap 4c19a0-4c19fc holds an unrelated helper); 12 fills the gap pattern around the engine-reserved IDs (CONSOLE.HPP: 0,1,7,11,14) — VERIFY against a live console session or the original Mac console binary before trusting on the wire
ConsolePlayerMechScoreUpdate 13 ctor @4c191c ([1]=0xd, size 0x14) [T1 value / T3 pairing]
ConsolePlayerMechDeathWithoutHonor 15 ctor @4c198c ([1]=0xf, size 0x10, single HostID) [T1]

The 9↔13 pairing (Killed vs ScoreUpdate — both 2-int payloads) follows binary emission order = source order [T3]; a live console decode would upgrade it. NetworkClient::Message header = {length, messageID, flags(1=Reliable)} = 12 bytes before payload [T1].

Compile-proven: BTCNSL.CPP (original) and BTTEAM.CPP (original, constructs ConsoleBTTeamScoreUpdateMessage — signature validated by a surviving consumer) both build against this header. The port headers' ...VTV... typedef aliases are port-only accommodations and are intentionally ABSENT here.