0536e287b5
The question was why S25 is absent from the DefTables +-path families. The premise is withdrawn: it was an artifact of listing DISTINCT values of LodEnumTable. S25 is not missing anything - it shares EnumLODSet_test.tbl with the sixteen story stages, and test is in the list. Counting distinct values hides who uses them; join per user. The per-stage join: EnumLODSet_test.tbl / EnumGameModel_test.tbl serve 17 stages - all of S01-S16 plus S25. The five challenge stages S24, S26, S27, S28, S29 have bespoke tables. Hangar.xpr has no pair at all. 17 + 5 + 1 = 23 objects carrying a StageResource. So the test-named table is the live LOD and model table for the whole story campaign - the strongest case yet of "a test_-named table can be live", serving 17 of the 22 missions. Eight shipped tables that nothing references: the family covers only 11 tags (S01, S02, S16, S24, S26-S29, Tutorial, test, Test) and is NOT per stage - S03-S15, S17-S23 and S25 have none. Seven tags are referenced; S01, S02, S16 and Test are present in DefTables.pak with zero references disc-wide, i.e. 8 orphan tables. "Early per-stage LOD sets, abandoned when the campaign was pointed at the shared test table" is a reading, not a measurement. Scope note recorded so the family is not mistaken for a stage one: EnumLODSet/EnumGameModel is overwhelmingly an EQUIPMENT family - 116 of the 130 referenced values are bare Equip_EnumGameModel_wep_NN.tbl names reached from PlayerLOD, WingmanLOD, PlayerMotion and WingmanMotion (58 distinct each); only the 14 stage-tagged values use the + path form. All fifteen artefacts byte-identical.