diff --git a/context/pod-hardware.md b/context/pod-hardware.md index 4da12ee..3f83c74 100644 --- a/context/pod-hardware.md +++ b/context/pod-hardware.md @@ -208,6 +208,21 @@ every checked control behavior: side button columns + **EJECT button** beside the joystick + per-mech COOLANT LOOP tables (weapons+generators per loop 1-6) and stat sheets (tonnage/armor/reservoir liters/heat sinks/top speeds incl. "Super Charged"). +- **MYOMER SEEK / "SUPER CHARGE" — a documented 4.0→4.10 DRIFT (2026-07-31) [T1 both sides].** + Manual p20/p22: seek "translates to a lower or higher top speed", gear 4 is named + **Supercharge** (screenshot caption "Seek Level Is Set to Supercharge"), expert-only ("in + standard simulation mode, you are not able to supercharge"), and "overheated myomers can + reduce your 'Mech's speed to zero". Stat sheets print THREE top speeds (Loki/Thor: Normal + 143 / **Super Charged 182** / **Gimped 40** kph). The 4.10 BINARY dropped the runtime + coupling entirely: the mapper demand @004afd10 has no myomer/seek term, `AvailableOutput` + has exactly two callers (assembly cap + graph), and the SpeedEffect attribute string has one + reference (its own table row). Even the printed ratio disagrees with 4.10's authored gears + (182/143 = 1.27 vs 0.9999/0.7 = 1.43) — the gear table and the assembly cap are vestiges. + In 4.10 the seek dial's live effects are heat (ratio² ≥ 1), the generator brown-out + threshold (whose real stake is TORSO TWIST — see [[subsystems]] WAVE 6), and the ENG graph. + "Top Speed Gimped 40" also confirms the limp-gait speed cap as an authored spec. The port + follows the BINARY (house rule); resurrecting manual-4.0 supercharge would be an opt-in + deviation for the operator to decide. NEW LEADS (manual describes, port lacks input/UI): **CROUCH** (button by the secondary screen; `Mech::duckState` attr 0x37 + SQUAT clips exist, nothing drives them), **EJECT** (sounds exist: EjectButton01_z*.wav), hot-box viewscreen framing (the deferred PNAME marker chain). Per-mech