re: SHAB is the per-stage record table -- record 0 is Stage 01, and c is its best time
EXTRAS -> MISSION SELECT renders per-stage records and they match the table. Stage 01 shows "High Score 4612 P EASY / Best Time 05:24.77 EASY" while SHAB[0] is (2, 4101, 324773, FILETIME): 324773 ms IS 5m24.773s, the displayed best time. Sixteen records, sixteen story stages -> the table is indexed by stage, and record 0 is Stage 01, the only stage this save has cleared. a = 2 difficulty of the record (both entries tagged EASY) b = 4101 NOT the displayed high score 4612; equals GHAD +24/+28 c = 324773 best clear time in ms -- confirmed against the screen d,e FILETIME This also explains the probe that filled SHAB[1] and changed nothing: the table holds stage RECORDS, not progress, and Stage 02 has never been cleared so its record is legitimately empty. Promotes the earlier "per-stage result record" guess to confirmed for the layout. Route: title -> EXTRAS -> MISSION SELECT. Only cleared stages are selectable (16 d-pad presses never left Stage 01) and the screen has its own difficulty selector (Y). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
BIN
docs/re/captures/mission-select-stage01-record.png
Normal file
BIN
docs/re/captures/mission-select-stage01-record.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.2 MiB |
Reference in New Issue
Block a user