3bae68d7f2
Watching [ScriptMission+40] and the three phase-1 objective squadrons together: all of ADN110/111/112 flip state 1 -> 2 at ~143s, while records in state 2 climb 24 -> 35 over four minutes. So state 1 means 'not yet deployed' for these, not 'gone'. The built-in table's '1/3/4 = gone/dead/invalid' shorthand is incomplete, and reading state != 2 as destroyed would have been wrong exactly as flagged last iteration. This also answers a much older question: mission-arrival-watch.md and the wave work recorded '0 confirmed arrivals' across many runs by watching the CRAFT population. The script's own unit table shows arrivals plainly -- eleven records enter state 2 within four minutes. The old negative measured the wrong structure; craft counts conflate deployment with attrition, the per-unit state field does not. Both attempts froze (at ~70s and ~253s), so no phase advance was reached. The freeze witness caught both immediately, which is why the truncation is visible instead of a silently flat line. New harness tools/re-capture/phase_watch.py.
14 lines
921 B
Plaintext
14 lines
921 B
Plaintext
file base 0xAB860010 ScriptMission 0xBC79C960
|
|
[ 1.8s] phase=1 finished=0 active= 24 ADN110:1 ADN111:1 ADN112:1
|
|
[ 58.2s] phase=1 finished=0 active= 27 ADN110:1 ADN111:1 ADN112:1
|
|
[ 90.7s] phase=1 finished=0 active= 30 ADN110:1 ADN111:1 ADN112:1
|
|
[ 120.8s] phase=1 finished=0 active= 29 ADN110:1 ADN111:1 ADN112:1
|
|
[ 143.4s] phase=1 finished=0 active= 32 ADN110:2 ADN111:2 ADN112:2
|
|
[ 188.4s] phase=1 finished=0 active= 34 ADN110:2 ADN111:2 ADN112:2
|
|
[ 223.3s] phase=1 finished=0 active= 35 ADN110:2 ADN111:2 ADN112:2
|
|
[ 253.4s] *** GUEST FROZEN -- readings below are about a dead world ***
|
|
[ 315.6s] *** GUEST FROZEN -- readings below are about a dead world ***
|
|
[ 377.7s] *** GUEST FROZEN -- readings below are about a dead world ***
|
|
[ 439.9s] *** GUEST FROZEN -- readings below are about a dead world ***
|
|
[ 502.1s] *** GUEST FROZEN -- readings below are about a dead world ***
|