THE SALVO DAMAGE (#95). Players measured an LRM 15 landing "3ish points". The logs agreed: [projectile] IMPACT damage=3.33333 (Oracle, LRM15) and 3.5 (Rajel, LRM10). Those are right PER MISSILE -- 50/15 and 35/10 -- and the bench shows why the salvo still under-delivers: each launcher pushes N rounds of which exactly ONE carries damage. Two individually-correct changes composed into an N-fold shortfall: * The ctor does what the binary's MissileLauncher ctor does (@0x3ac/@0x3d4): damageData.burstCount = missileCount; damageData.damageAmount /= missileCount; The record holds the PER-MISSILE amount plus the count; the arcade reconstitutes amount x burstCount when it applies the hit. * Task #62 then correctly stopped the port applying the hit once per visual round (that was ~missileCount-x too lethal) by damaging only the lead round -- but handed it the already-divided amount. Our DamageZone::TakeDamage is `damageLevel += amount * scale` and drops burstCount, so the salvo delivered amount/missileCount. Since the port collapses the cluster to one damaging round, multiply the count back in there. Bench: an SRM6 salvo now lands amt=35 (the authored total) taking a zone 0 -> 0.556, where it previously landed 5.83. THE DOUBLE EXPLOSION (#84). Oracle: "missile appear to register hit explosions twice, once where target was and again where the target is." There are two spawn sites: BTSpawnRoundDetonation at the round's own impact point, and the message manager's bundled explosion at the CONSOLIDATED point a frame later. The duplicate was known and thought harmless -- "among a rippled volley it is invisible" -- which held only while a salvo landed N detonations. A projectile now marks its weapon (MarkRoundDetonated) and the consolidation skips queueing a second blast for it; direct-fire weapons never mark, so lasers/AC keep the bundled explosion they rely on. Bench: 4 missile impacts -> 4 SKIPPED, while 11 direct-fire hits still queue normally. SWEPT CONTACT (#84 tail). Contact was a 10-unit sphere sampled only at the END of each step. With the authored thruster live (#84) field rounds arrive at v=955 -- a ~16 unit step at 60fps, larger than the radius -- so samples can straddle the target. (Pre-#84 rounds flew ~100-300 = a 1.7-5 unit step and could never skip it: the velocity fix exposed this, it did not cause it.) Now tests the whole segment travelled and bursts at the point of NEAREST APPROACH, which also stops the detonation being flung past the target at speed. RETRACTION: I posted tunnelling as the leading explanation for the lost salvo. The bench disproves it -- zero fizzles, and the "missing" rounds are the dmg=0 visual rounds of the cluster, which never registered damage by design. The sweep is kept as speed-independent robustness, not as the #95 fix. Bench: scratchpad/night8/salvo.sh (BT_PROJ_LOG + BT_FIRE_LOG). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
33 lines
1.3 KiB
Python
33 lines
1.3 KiB
Python
"""Split a player log into per-session blocks and report what each session was.
|
|
|
|
Night-8 triage: Oracle ran 4.11.659 for the first half of the evening and only
|
|
switched to 4.11.674 at 21:27, so every claim from his log has to be attributed
|
|
to the right build before it means anything.
|
|
"""
|
|
import re
|
|
import sys
|
|
import os
|
|
|
|
path = sys.argv[1]
|
|
want_build = sys.argv[2] if len(sys.argv) > 2 else None
|
|
|
|
data = open(path, "r", encoding="latin-1", errors="replace").read()
|
|
hdr = re.compile(r"===== BT411 SESSION\s+build=(\S+)\s+\(\S+\)\s+machine=(\S+)\s+user=(\S+).*?local=(\S+ \S+)")
|
|
|
|
marks = [(m.start(), m.group(1), m.group(2), m.group(3), m.group(4))
|
|
for m in hdr.finditer(data)]
|
|
print("%s: %d session(s)" % (os.path.basename(path), len(marks)))
|
|
|
|
for i, (pos, build, mach, user, when) in enumerate(marks):
|
|
end = marks[i + 1][0] if i + 1 < len(marks) else len(data)
|
|
block = data[pos:end]
|
|
if want_build and build != want_build:
|
|
continue
|
|
# what actually happened in this session
|
|
mech = set(re.findall(r"vehicle[= ]+([A-Za-z0-9_]+)", block))
|
|
kills = len(re.findall(r"\bkill\b", block, re.I))
|
|
leaks = len(re.findall(r"\[cool\]|leak", block, re.I))
|
|
print(" #%-2d %s %s len=%-9d mech=%-22s lines=%d"
|
|
% (i + 1, build, when, len(block),
|
|
",".join(sorted(mech))[:22] or "-", block.count("\n")))
|