fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: the last 9 effects are genuinely unshipped; wep_85 accounts for two

Browse Source 
EF_IDX_ proved that prefixes exist, so the residual deserved the same treatment
across every package rather than one. Censusing prefixes over all 36
effect-carrying .xpr gives seven in use:

  EF_IDX_       223 names
  mdl_           45
  EF_IDX_mdl_    45
  VolumeLine_    10
  GN_            10
  GN__            6
  bare           the rest

Testing all nine unlocated names against all seven prefixes: 0 of 9 resolve.

That zero has force where the earlier disc-wide zero did not, and for the stated
reason - the control shows each prefix genuinely carries names the same search
reads (223, 45, 45, 10, 10, 6), so the instrument demonstrably works on the
population it is being asked about. The nine are bound by a datasheet field and
shipped in no package.

Two of them turn out to belong to one cut asset. eff_m010_wep_85 and
eff_m011_wep_85 name a weapon, and the weapon is real in the data:
Weapon_DSaber_P_wep_85_Beam with 24 uses, its Shell_, WeaponCannonName_ and
WeaponShellName_ siblings, and GameModel_eff_m010_wep_85 / _m011_ declaring the
two effects. But the weapon packages stop at 84 - hidden/resource3d/ holds 59
rou_f001_wep_NN.xpr files numbering 00 to 84 with gaps, and no wep_85. So wep_85
is a declared-but-unshipped weapon and its two effects go missing with it.

This does not contradict "every weapon is placed - 131 = 105+22+0+4". That
partition is declared x MOUNTED IN A LOADOUT, which is a different question from
whether a package ships.

Seven remain with no account: eff_e0044, eff_f0002, eff_f0002_barn, eff_h308,
eff_j002_e01, eff_j002_e02, eff_n0071. The .xpr route is now exhausted for them
under every prefix the disc uses; a different container or a runtime generator is
what is left.

All seventeen artefacts byte-identical.
This commit is contained in:
Sylpheed RE agent
2026-08-28 10:17:20 +00:00
parent 5ad6e9397c
commit 09b7ac7b7f
2 changed files with 75 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/re/BACKLOG.md
View File

@@ -6826,3 +6826,31 @@ outermost (`_e_root` 19, `_f_root` 18, `_break_root` 13, bare 30). Bare-parent
test: **`_ALL` 17/17**, `_root` 64/87, `_break` 15/30, and 🔑 **`_e`/`_f` 0 of
135** — asset-side confirmation that effects are authored per faction with no
faction-neutral original.
---
## ✅ 2026-08-28 — the last 9 effects are genuinely unshipped; `wep_85` explains two
Item (a). `EF_IDX_` proved prefixes exist, so the residual got the same treatment
across every carrier. Censusing prefixes over all 36 effect-carrying `.xpr` gives
**seven**: `EF_IDX_` 223 names, `mdl_` 45, `EF_IDX_mdl_` 45, `VolumeLine_` 10,
`GN_` 10, `GN__` 6, plus bare.
✅ **Testing all nine against all seven: 0 of 9 resolve.** ⚠️ This zero has force
where the earlier disc-wide zero did not — the control shows each prefix
genuinely carries names the same search reads (223/45/45/10/10/6), so the
instrument works on the population being asked about. The nine are **bound by a
datasheet field and shipped in no package**.
🔑 **Two of them belong to `wep_85`, a declared-but-unshipped weapon.**
`Weapon_DSaber_P_wep_85_Beam` is real in the data (24 uses, with `Shell_`,
`WeaponCannonName_`, `WeaponShellName_` siblings, and `GameModel_eff_m010_wep_85`
/ `_m011_` declaring the effects) — but **the weapon packages stop at 84**: 59
`rou_f001_wep_NN.xpr` files, 00–84 with gaps, no 85. One cut asset accounts for
two of the nine. ⚠️ No contradiction with "every weapon is placed — 131": that
partition is declared × *mounted*, not whether a package ships.
🟡 **Seven remain unaccounted**: `eff_e0044`, `eff_f0002`, `eff_f0002_barn`,
`eff_h308`, `eff_j002_e01`, `eff_j002_e02`, `eff_n0071`. ❔ The `.xpr` route is
exhausted under every prefix the disc uses; a different container or a runtime
generator is the remaining possibility.

47
docs/re/structures/unit-substructure-records.md
View File

@@ -517,3 +517,50 @@ parent of an existing node", and `_break` at 15 of 30 is likewise not a plain
🔑 **`_e`/`_f` never have a bare parent — 0 of 135.** That is independent,
asset-side confirmation of the faction law: an effect is authored per faction,
and there is no faction-neutral original for either side to derive from.
### ✅ The last 9 are genuinely unshipped — a controlled zero over seven prefixes
`EF_IDX_` proved prefixes exist, so the residual deserved the same treatment
across every package rather than one. Censusing prefixes over all 36
effect-carrying `.xpr` gives **seven** in use:
| prefix | names it carries |
|---|---|
| `EF_IDX_` | 223 |
| `mdl_` | 45 |
| `EF_IDX_mdl_` | 45 |
| `VolumeLine_` | 10 |
| `GN_` | 10 |
| `GN__` | 6 |
| *(bare)* | the rest |
Testing all nine unlocated names against all seven: **0 of 9 resolve.**
⚠️ **This zero has force where the earlier disc-wide zero did not**, and for the
stated reason: the control shows each prefix genuinely carries names the same
search reads — 223, 45, 45, 10, 10, 6. The instrument demonstrably works on the
population it is being asked about.
So the nine are **bound by a datasheet field and shipped in no package**:
`eff_e0044`, `eff_f0002`, `eff_f0002_barn`, `eff_h308`, `eff_j002_e01`,
`eff_j002_e02`, `eff_m010_wep_85`, `eff_m011_wep_85`, `eff_n0071`.
### 🔑 Two of the nine belong to `wep_85` — a declared weapon with no package
`eff_m010_wep_85` and `eff_m011_wep_85` name a weapon, and the weapon is real in
the data: **`Weapon_DSaber_P_wep_85_Beam` (24 uses)** with its
`Shell_`, `WeaponCannonName_` and `WeaponShellName_` siblings, plus
`GameModel_eff_m010_wep_85` / `_m011_` declaring the two effects.
But **the weapon packages stop at 84**. `hidden/resource3d/` holds **59**
`rou_f001_wep_NN.xpr` files numbering 00–84 with gaps, and **no `wep_85`**. So
`wep_85` is a **declared-but-unshipped weapon**, and its two effects go missing
with it — one cut asset explaining two of the nine.
⚠️ This does not contradict "every weapon is placed — 131 = 105+22+0+4"
([[weapon-struct-runtime]]): that partition is declared × *mounted in a loadout*,
which is a different question from whether a package ships.
🟡 **Seven remain with no account**: `eff_e0044`, `eff_f0002`, `eff_f0002_barn`,
`eff_h308`, `eff_j002_e01`, `eff_j002_e02`, `eff_n0071`. The `.xpr` route is now
exhausted for them under every prefix the disc uses.