fabi/Syplheed-Reborn
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re: the leaderboard screen, and a Detail_* prefix trap

Browse Source 
sub_8219E560 r11, censused against tables.pak exactly like the result screens.
444 instructions, one call site (sub_821A2A80), 100 % of its names are tables.pak
names.

The 18 names partition exactly: 13 record names + 5 field-only names.  The 13 are
the 12 Detail_* panel elements plus MISSIONS -- a 0-field record already owned by
isl-condition-builtins.md and challenge-mission-gate.md, so not new.  The five
field-only names are the screen's parameters: DETAIL_TITLE, one field in each of
six mode records (ScoreAttack, TimeAttack, Extra01..Extra04), and
Detail_Board_{Permanent,Monthly,Friend,Self}, four fields of CHIPS -- the board
scopes.

All 12 Detail_* record names are in the code block, zero residual -- the opposite
of the boss motions, where the block was a 25-of-55 subset.  The panel is Rank,
GamerTag, Main_{Time,Points}_{Self,Live}, Warships, Warplanes,
Weapon_{Nose,Main1,Main2,Main3}: your figure against the selected entry's, plus
that pilot's kills and four weapon slots.  _Live, GamerTag and the Friend/Monthly
boards make it the Xbox Live detail view.

The trap worth keeping: tables.pak has 12 Detail* RECORD names and 12 Detail*
FIELD names, and they are DISJOINT (0 overlap).  The fields are a different axis
-- 4 board scopes + 6 modes + Detail_Window_{Known,Unknown}.  A Detail_* name
means nothing until you say whether it is a record or a field.

Not settled: what Detail_Window_Known/_Unknown switch between, and whether
Extra01..04 map onto the four challenge missions.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE
This commit is contained in:
Claude (auto)
2026-08-27 23:58:13 +00:00
parent 24c3168768
commit aeec0dab8f
3 changed files with 100 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
docs/re/BACKLOG.md
View File

@@ -5460,3 +5460,40 @@ rather than five parameters.
🟡 Not settled: whether `attackC` is reachable by index rather than by name; what
`eff_s900_e_Charge` attaches to; and the other three shortlisted rows
(`sub_8219E560` leaderboard, `sub_825F2CF0`/`sub_825F2F88` post-processing).
---
## ✅ 2026-08-27 — the leaderboard screen, and a `Detail_*` prefix trap
Item (a): `sub_8219E560 r11`, censused against `tables.pak` exactly like the
result screens. New doc `docs/re/structures/leaderboard-screen.md`. Static only;
no artefact changed.
✅ **The 18 names partition exactly: 13 `tables.pak` record names + 5 field-only
names.** The 13 are the **12 `Detail_*` panel elements** plus **`MISSIONS`** — a
0-field record already owned by `isl-condition-builtins.md` and
`challenge-mission-gate.md`, so not new. 444 instructions, **one** call site
(`sub_821A2A80`), 100 % of the names are `tables.pak` names.
The five field-only names are the screen's parameters: **`DETAIL_TITLE`**, one
field in each of six **mode** records (`ScoreAttack`, `TimeAttack`,
`Extra01…Extra04`), and **`Detail_Board_{Permanent,Monthly,Friend,Self}`**, four
fields of `CHIPS` — the board **scopes**.
✅ **All 12 `Detail_*` record names are in the code block — zero residual**, the
opposite of the boss motions (a 25-of-55 subset). The panel is
`Rank`, `GamerTag`, `Main_{Time,Points}_{Self,Live}`, `Warships`, `Warplanes`,
`Weapon_{Nose,Main1,Main2,Main3}` — your figure against the selected entry's,
plus that pilot's kills and four weapon slots. `_Live`, `GamerTag` and the
Friend/Monthly boards make it the **Xbox Live** detail view.
🔑 **The trap worth keeping: `tables.pak` has 12 `Detail*` RECORD names and 12
`Detail*` FIELD names, and they are DISJOINT (0 overlap).** The fields are a
different axis — 4 board scopes + 6 modes + `Detail_Window_{Known,Unknown}`.
**A `Detail_*` name means nothing until you say whether it is a record or a
field**; counting "24 `Detail_*` things" would merge two unrelated tables.
🟡 Not settled: what `Detail_Window_Known`/`_Unknown` switch between; whether
`Extra01…04` map onto the four challenge missions the corpus knows. And the last
shortlisted row (`sub_825F2CF0`/`sub_825F2F88` post-processing, two functions on
one base) is still unopened.