arcattackandClaude Fable 5
5ae4410914
Field report (night 3): "two ammo bay fires and no death" (Cyd + RajelAran; one
purged, one left burning). Root cause = THREE independent kill-switches stacked
on the same path, all in ammobin.cpp:
1. `GameClock::Now() { return 0; }` -- `cookOffTime < Now()` was `0 < 0`, so
an ARMED bay fire never detonated.
2. `InjectHeat(void*) {}` -- the detonation body was a no-op.
3. The bin's Damage record was never stamped -- 0 damage of type 0 (which the
mech TakeDamage handler drops) even if 1+2 had fired.
THE FUSE (raw disasm, scratchpad/disammo.py): the old "RandomDelay" was a Ghidra
carve artifact -- FUN_004dcd94 is __ftol and the export DROPPED the caller's x87
expression. The real bytes @004bd450: fld 10.0 / fmul [ticksPerSecond] /
fadd 0.5 / __ftol -- a FIXED 10.0-SECOND fuse in clock ticks. New gotcha #19
(reconstruction-gotchas.md) documents the __ftol export blind spot.
THE DAMAGE RECORD: bin+0x1F0..0x21C is a real engine `Damage` (FUN_0041db7c IS
Damage::Damage(), byte-matched to T0 DAMAGE.cpp). The linked ProjectileWeapon's
ctor @004bc3fc stamps it from weapon->damageData @0x3A8 via
owner->roster[0x128][res+0x1C0] -- projweap.cpp's old comment called this "the
bin's HUD display block ... wired in the AmmoBin family"; both halves were wrong
and it was wired nowhere. Now stamped (before MissileLauncher's ctor divides by
missileCount -- a missile bin authentically holds the per-SALVO amount).
THE DETONATION (@004ac274 = MechSubsystem::DistributeCriticalHit -- the old
"HeatableSubsystem::InjectHeat" label was wrong, and the old reconstruction
iterated a stand-in CriticalChain whose First()/Next() returned 0):
statusAlarm pulse Exploding(2)->Destroyed(1) (slot 13 = the printSimulationState
state PRINT @004ac8c0, not an "explosion notify"), own private zone pinned
destroyed, then collect the mech DamageZones whose crit entries plug the bin
(the binary filters plug classID 0x4E = DamageZoneClassID -- VDATA.h idx 78,
cross-checked via idx 28 = AudioStateTrigger), split the amount evenly, and send
the OWNER one full Entity::TakeDamageMessage per zone: inflictingEntity = SELF,
damageZone = the zone index, inflictingSubsystemID = the bin (the message-
manager explosion-bundling key, ENTITY3.h's own NOTE), printing the binary's
exact "ammo explosion damaging <zoneName>" @0050df61.
Port shape: Mech::AmmoExplosionFanOut (mechdmg.cpp) behind a databinding bridge;
guarded deviation: zoneCount==0 warns instead of the binary's unguarded divide.
CriticalChain/CriticalEntry stand-ins DELETED from mechrecon.hpp.
VERIFIED LIVE (BT_BAYTEST hook = message 1, the crit-induced arm channel):
scratchpad/baytest.py : arm -> 10s -> "20 rounds x 35 = 700 (type 2)" ->
"ammo explosion damaging dz_ltorso" -> zone cascade -> mech DESTROYED
(authentic death list).
scratchpad/baypurge.py: arm -> eject-hold purge -> "bay fire EXTINGUISHED
(bin empty)", no detonation.
scratchpad/sim3.py : the HEAT route arms organically in combat (overheated
AFC100), detonates "11 x 25 = 275 (type 1)" split across dz_larm + dz_lgun.
BAYBOOM matchlog record added for MP field forensics.
FIX-OF-THE-FIX (caught by the sim3 regression, would have shipped a crash):
MechSubsystem's ReconDamageZone proxy puts structureLevel at OFFSET 0 -- which
ALIASES THE REAL DamageZone's VTABLE POINTER (the private zone is `new
DamageZone`, mechsub.cpp:154; mechsub.hpp:260 documents the alias). My first
DistributeCriticalHit kept the old body's `damageZone->structureLevel = 1.0f`
and OVERWROTE THE ZONE'S VPTR with 0x3F800000; the respawn sweep's virtual
SetGraphicState (vtable+0xC) then called through it -> AV at 0x3f80000c in
RespawnRepair, one frame after a bay-fire death. ALL EIGHT proxy-view sites in
mechsub.cpp swept to the engine view (((DamageZone*)damageZone)->damageLevel
@0x158) -- including two silently-wrong LIVE readers: GetStatusFlags (vptr as
float -> always "intact") and ApplyDamageAndMeasure (the crit cascade's
measure). Ruled out first by evidence: the weapon->bin stamps were all clean
(six stamps, all classID 0xbcb, logged).
#47 (half 1 -- the FIRE ICON): BallisticWeaponCluster::Execute @004c9a38 reads
bin+0x18C = cookOffArmed into the btefire.pcc TwoState, and while armed computes
(Now - cookOffTime)/ticksPerSecond -- the COOK-OFF COUNTDOWN -- into the numeric
beside it. The old reconstruction misread 0x18C as "the reload state" and
bridged the icon to BTAmmoBinFeeding, so it blinked on every feed and never lit
on a bay fire (RajelAran: "it doesn't"). Now driven by the
BTAmmoBinCookOffArmed/CookOffTime complete-type bridges. [T2 -- the data path
is rig-verified; the pixels await the next live session.]
#47 (half 2 -- the ENG-BUTTON FLASH): fully mapped, deliberately NOT built this
session. The authored data SHIPS (BTL4.RES carries exactly one type-31
GaugeAlarmStream); the chain is alarm SetLevel -> gauge-watcher socket ->
Renderer msg 7 -> GaugeAlarmManager::Activate @00448d00 (T0) -> the BTL4
override @004cc148..@004cc2fc (btl4galm.cpp's provenance note claiming "no
override body exists" is WRONG -- corrected in-file) -> LampManager::FindLamp
@00444c80 -> Lamp::SetAlertState @00444e64 (flash counter) -> the L4 flush
@00474e94 emitting flashFast states 0x37/0x13 (== T0 L4LAMP.cpp:234-239).
Missing: the override bodies, the gauge-watcher sender, the aux-button lamps.
3-piece plan in context/open-questions.md.
Also logged: HandleMessage is vtable slot 8/9 in the binary but NON-virtual
across 10 reconstruction classes (bit the BT_BAYTEST hook; typed call used, gap
documented in open-questions).
KB: combat-damage.md (the full cook-off section), decomp-reference.md (the
cluster addresses + the GaugeAlarm/lamp map + BT_BAYTEST env), gauges-hud.md
(the fire-icon correction), reconstruction-gotchas.md #19 (__ftol),
open-questions.md (2 entries), btl4galm.cpp provenance correction.
checkctx CLEAN. 40 LNK2019 unchanged (the two pre-existing families).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
66 lines
2.2 KiB
Python
66 lines
2.2 KiB
Python
"""Raw-disassemble the AmmoBin cook-off cluster from BTL4OPT.EXE (#46).
|
|
|
|
Ghidra's export dropped the float math around the FUN_004dcd94 (__ftol) calls --
|
|
the decomp shows `iVar2 = FUN_004dcd94();` with the random-delay expression
|
|
missing entirely. Recover:
|
|
@004bd394 AmmoBinSimulation (the arming expression: delay = f(?) )
|
|
@004bd5c4 AmmoBin ctor (who writes the Damage descriptor @+0x1F0/+0x1F4)
|
|
@004bdb94 HandleMessage(1) (same delay expression, crit-induced fire)
|
|
"""
|
|
import struct
|
|
from capstone import *
|
|
|
|
PATH = r"C:\git\bt411\content\BTL4OPT.EXE"
|
|
data = open(PATH, "rb").read()
|
|
e_lfanew = struct.unpack_from("<I", data, 0x3C)[0]
|
|
coff = e_lfanew + 4
|
|
num_sec = struct.unpack_from("<H", data, coff + 2)[0]
|
|
opt_size = struct.unpack_from("<H", data, coff + 16)[0]
|
|
opt = coff + 20
|
|
image_base = struct.unpack_from("<I", data, opt + 28)[0]
|
|
sec_tbl = opt + opt_size
|
|
secs = []
|
|
for i in range(num_sec):
|
|
off = sec_tbl + i * 40
|
|
vsize, va, rawsize, rawptr = struct.unpack_from("<IIII", data, off + 8)
|
|
secs.append((va, vsize, rawptr, rawsize))
|
|
|
|
|
|
def va_to_off(va):
|
|
rva = va - image_base
|
|
for sva, vsize, rawptr, rawsize in secs:
|
|
if sva <= rva < sva + max(vsize, rawsize):
|
|
return rawptr + (rva - sva)
|
|
return None
|
|
|
|
|
|
def dump_dword(va):
|
|
off = va_to_off(va)
|
|
return struct.unpack_from("<I", data, off)[0] if off is not None else None
|
|
|
|
|
|
def dump_float(va):
|
|
off = va_to_off(va)
|
|
return struct.unpack_from("<f", data, off)[0] if off is not None else None
|
|
|
|
|
|
md = Cs(CS_ARCH_X86, CS_MODE_32)
|
|
|
|
for name, va, length in (
|
|
("AmmoBinSimulation @004bd394", 0x004bd394, 0x160),
|
|
("AmmoBin ctor @004bd5c4", 0x004bd5c4, 0xec),
|
|
("HandleMessage @004bdb94", 0x004bdb94, 0x70),
|
|
):
|
|
off = va_to_off(va)
|
|
print("=" * 78)
|
|
print(name)
|
|
print("=" * 78)
|
|
for ins in md.disasm(data[off:off + length], va):
|
|
print(" %08x %-24s %s %s" % (ins.address, ins.bytes.hex(), ins.mnemonic, ins.op_str))
|
|
print()
|
|
|
|
# constants likely referenced by the delay math
|
|
for cva in (0x004bd4e8, 0x004bd4ec, 0x004bd4f0, 0x004bdb74, 0x004bdb78, 0x004bdb7c,
|
|
0x004e0f74, 0x004e0f78, 0x004e0f7c, 0x004e0f80, 0x004e0f84, 0x004e0f88):
|
|
print("DATA %08x: dword=%08x float=%r" % (cva, dump_dword(cva) or 0, dump_float(cva)))
|