pilot: escort-weighted targeting (DEFEND), plus the capital-ship keep-out it needed
While the asset is losing hull, target what is pressing IT — ranked by distance to the asset minus credit for closing on it — instead of what is nearest to us. Trigger and ranking both read the live hull (pos+0x154), so nothing is inferred. DEFEND engaged 1.9 s after the asset's first hit and held 54% of a 330 s run. It did NOT measurably save the asset: over the window two runs share, the policies are equal to within noise (t=239: 23218 vs 23038). Two reasons, both recorded rather than papered over: the runs are not comparable past that window (spawn timing differs and the hostile count GREW 134->166 in one, fell 147->118 in the other), and the real bottleneck is lethality — the guns are on for 12% of combat frames because the target is outside the 9 deg cone the rest of the time. Also corrects a single-run claim in the previous commit: the asset is NOT reliably safe for the first ~170 s. A second run had first damage at t=70 s. The stage does not replay identically; only 'the loss is slow' survives. Fixes a fatal bug the new mode exposed: DEFEND flies at the asset, which sits inside the friendly formation, and the first escort run went hull 1500 -> DEAD in one tick at 2026 units/s, 0.6 s from a friendly destroyer that avoidance thought it would clear by 365 units — the ship's radius is 2000. Keep-out applied only to hostile turrets. Every entity above BIG_RADIUS now gets its own radius + 800 of physical keep-out with braking inside it, whatever its faction.
This commit is contained in:
330
docs/re/captures/mission-state-stage02-escort-weighted.jsonl
Normal file
330
docs/re/captures/mission-state-stage02-escort-weighted.jsonl
Normal file
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user