Searched RAM for HP 25000 (200+ hits, too common), for the rare float AttackVesselPoint 0.08 (64 hits, no window holds the unit's other values, one hit is a code constant), and for the ID string itself (two copies, each pointed at from -0x10, but the surrounding 256 words hold none of the numbers because that region is the IDXD string pool where values are ASCII). Hypothesis recorded as 🟡: IDXD is reflective and the engine likely reads values from the pool by key on demand, caching only the per-frame ones -- which is exactly what the 0x820af844 object contains at any dump depth. If so, a defaulted field has no value anywhere in data and the default is applied by code at read time, so Route B for the Ratio/Count family needs the read path or the static DuckDB route, not more scanning. The 13 Size_Y values worked because Size_Y is one of the cached fields. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
861 B
861 B