25b5f60ea1
Refuted, and it was my own suggestion from last turn. Across all 166 .xpr
packages the _child suffix occurs in ONE file, Stage_S24.xpr, with exactly one
stem, stg24_04, 20 occurrences. Across the 105394 distinct parsed pak names -
record names, field names and string values - names ending _all or _child occur
ZERO times. So the pair is mesh-internal to a single model and never reaches the
data tables; the tables only ever name the bare stg24_04. n = 1 is not a
convention, and the multi-part mesh mechanism the corpus actually owns is
xbg7-mesh's grouped index/vertex pools, which is a different thing.
The orphan tables' five unique effects split three ways, chased through PARSED
names rather than .xpr bytes:
eff_n0071 LIVE - Generic.GameResourceID in DefTables.pak and
an Explosion record's ExplosionFxModel in all six
GP_MAIN_GAME_* archives (x6 = one user)
eff_e0033 a mesh in Base.xpr, but no data reference
eff_e0058/_e0059/_e0060 neither a mesh nor any reference
So one "abandoned" entry is not abandoned: the orphan LOD tables list an effect
the shipped _test table omits while the game still binds it elsewhere.
Control recorded so the negative has force: effect names bind through a whole
family of fields - Effect_Paralyze (2874 values), HitFxModel (738), ShellModel
(516), JetFxModel_000/001/002, MuzzleFlashFxModel_Loop - so a value that
resolves through none of them really is unreferenced, not merely missed by a
narrow search.
All fifteen artefacts byte-identical.