d2c81249cd
My enumeration sourced entities from moving(), which requires a position to CHANGE between two samples. A capital ship holding station changes by exactly zero, so it can never appear -- which is also why lo=0 and the whole-map scan did not help, and why parked ArrowHead wingmen were missing. The filter was the problem, not the range, and not the game. navigator.py already does it right and says so in its header: search for the DEFINITION POINTER and take position = hit - 0x130, "which finds every entity whether it is moving or not". The existing mission_state.py scan on Stage 02 returns 149 entities with hull(+0x154) == definition HP for 129 of them: UN_f101_TCAF_Acropolis (+5000, +0, +0) hull=25000.0 HP=25000.0 frac=1.000 UN_e105_ADAN_Cruiser hull=30000.0 HP=30000.0 UN_e106_ADAN_Destroyer hull= 9150.0 HP=10000.0 (under fire) So "an autopilot that must protect the Acropolis cannot locate it through the +0x130 method at all" is withdrawn outright -- it can, and INDEX.md had already recorded the Acropolis falling 25000 -> 23038 over 240s. What survives: the two enumerations are still different structures in different regions (0/116 vtable instances lie in the +0x130 region). What does not survive is any claim that the +0x130 model covers only four types.