re(units): six targeted harvests — 60 of 110 units, 6 071 defaulted values
S03, S06, S09, S13, S15, S16 (plus the earlier run): 21 -> 60 units, 963 -> 6 071 defaulted-on-disc values, 8 241 rows. Disc cross-checks agree with 0 disagreements throughout. - UN_e901_ADAN_Boss and UN_e910_core_ADAN_GeneratorCore are harvested (HP 10 000, Size_X 500, Size_Radius 250, MaximumVelocity 450) WITHOUT the boss ever being on screen: definitions are instantiated at stage load, so a unit only needs to be in the roster. That is far weaker than what the draw-capture work requires. - The extra stages are not reachable via the save's stage field: stage 27 boots to the title and then the emulator exits during the load, as do the other S24..S29 entries, while story stages 1-16 all load. The field addresses the story campaign only; EX/challenge rosters need the Challenge-mode menu path. Remaining 50 units are almost all EX variants in S24/S25/S27/S28/S29; the only story-stage stragglers are UN_mn500_ADAN_FloatingMine and UN_be005_ADAN_SpaceFortress in S08. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NptfmpjdpNCKEez6d2xvA9
This commit is contained in:
@@ -480,3 +480,30 @@ Cross-checks against the disc over the three snapshots: **1 052 agree, 0 disagre
|
||||
One more angle field turned up the same way as the last: `Through_AngleMaximum`
|
||||
(object `1.0472` = 60° in radians) carries neither an `AV_`/`AA_` token nor `Bank`, so
|
||||
the degrees↔radians rule covers **anything with `Angle` in the name** too.
|
||||
|
||||
### Harvest state: 60 of 110 units, and where the remaining 50 live (2026-08-13)
|
||||
|
||||
Six targeted missions (S03, S06, S09, S13, S15, S16, plus the earlier Night Ravens
|
||||
run) take the file to **60 units · 8 241 rows · 6 071 defaulted-on-disc values**,
|
||||
from 21 units / 963 values this morning. Cross-checks against the disc across every
|
||||
snapshot: **agree, 0 disagree** — the discipline never had to be relaxed.
|
||||
|
||||
Two results worth calling out:
|
||||
|
||||
* **`UN_e901_ADAN_Boss` and `UN_e910_core_ADAN_GeneratorCore` are harvested**
|
||||
(HP 10 000, `Size_X` 500, `Size_Radius` 250, `MaximumVelocity` 450) — **without the
|
||||
boss ever appearing on screen**. Definitions are instantiated when the stage loads,
|
||||
so a unit only has to be in the mission's roster, not in view. That is a much
|
||||
weaker requirement than the capture work needs, and it is why the same stage that
|
||||
could not give the `e901` geometry gave its stats immediately.
|
||||
* **The extra stages are not reachable this way.** Setting the save's stage field to
|
||||
**27** boots to the title and then the emulator exits during the load — likewise
|
||||
the other `S24…S29` entries. Story stages 1–16 all load normally. So the field
|
||||
addresses the **story campaign only**, and the EX/challenge rosters need whatever
|
||||
menu path Challenge mode uses.
|
||||
|
||||
That bounds the rest of the work: of the 50 units still unread, the roster ranking
|
||||
puts almost all of them in `S24/S25/S27/S28/S29` (`*_EX4`, `*_EX5`, `*EX` variants,
|
||||
`UN_f004_TCAF_DeltaSaber_A_Player`). The only story-stage stragglers are
|
||||
`UN_mn500_ADAN_FloatingMine` and `UN_be005_ADAN_SpaceFortress` in **S08**, which is
|
||||
one more ordinary run.
|
||||
|
||||
Reference in New Issue
Block a user