# 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.