Combat: AUTHENTIC weapon groups -- streamed per-mech button bindings + the real fire chain (task #5)
The recovered system: fire channels = LBE4ControlsManager buttonGroups (0x40/0x45/0x46/0x47); default groups = the per-mech type-6 controls-map resource in BTL4.RES, installed by the T0 CreateStreamedMappings the port already called -- it needed only the TriggerState attribute (id 0x13 PINNED to the binary value; fireImpulse@0x31C is the binary's TriggerState) and an input feed. Keyboard/harness now push press/release edges into the button groups; the gBT*Trigger bypasses, per-type keyboard split and 1,0 pulse hack are retired -- weapons sharing a button fire TOGETHER (madcat Trigger = 4 weapons). Myomers @4b9550/@4b95b8 misattribution corrected (they are MechWeapon ConfigureMappables/ChooseButton). Verified 2-node: kill through the authentic chain (12 hits vs ~36 pre-groups). Config-mode session (regrouping UI) = the remaining stage, KB-scoped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
4554ea543a
commit
8ed6184d65
@@ -464,9 +464,16 @@ void Myomers::ResetToInitialState(Logical powered)
|
||||
|
||||
|
||||
//***************************************************************************
|
||||
// Myomers::ConnectToMover @004b9550
|
||||
// Myomers::ConnectToMover (mislabeled)
|
||||
//***************************************************************************
|
||||
//
|
||||
// ⚠ MISATTRIBUTION (task #5 correction): @004b9550/@004b95b8 are NOT Myomers
|
||||
// functions -- the weapon message-table @0x511860 proves they are
|
||||
// MechWeapon::ConfigureMappables (id 9) / ChooseButton (id 10), the weapon->
|
||||
// button grouping handlers (the +0x31C coincidence: Myomers speedEffect vs
|
||||
// MechWeapon TriggerState). The bodies below are retained as the port's
|
||||
// Myomers stand-ins but carry no binary address.
|
||||
//
|
||||
// Attaches the live SpeedEffect output (@0x31C) into the Mech's JointedMover
|
||||
// roster (the mover at **(Mech[0xD0]+0x128)). Driven by a connect message
|
||||
// whose payload index is at message+0xC:
|
||||
|
||||
Reference in New Issue
Block a user