Match, menu and footstep sounds
Our reading of the executable and of the menu scripts (bytecode read with the sibling HUD text run’s script dump). All cues here are in the common bank (slot 0), volume and pitch 1.0, no position unless said.
There is no announcer. No voice bank or cue belongs to the match flow; the countdown is two common cues and four HUD sprites (H):
The ready phase (5) handler 0x14012ade0 creates the countdown object (class handle
pdvkBattle, constructor 0x140219ec0, pointer 0x140532f50). Its tick 0x14021a060 counts its own ticks:Tick Cue HUD sprite (manager 0x140533450) Sprite life (ticks) 0 632 (0x278) 0x50 40 30 632 0x4F 40 60 632 0x4E 40 90 633 (0x279) 0x54, in two sprite slots 50 Correction to “Match flow”: the two ids 0x2BC / 0x2BD at the first battle start (0x14012adaa, 0x14012adb4) are not sound cues. They go to the effect spawner 0x14018d280: effect files 700 and 701 (
Effect/eft0700,eft0701; both exist).Results: music tracks 37 / 38 (“Music”); the battle-end menu script plays cues 200 and 0 through the menu sound native.
Menu sound native 0x102b (group-1 native table 0x1403fafe0, function 0x140261750): plays the common cue given as its argument. The menu scripts use cues 0, 1, 2, 3 (the four menu beeps: options, lobby, pause menu), 37, and 200 (battle end). The window manager code (class handle
pdWinManager, sites 0x140248a0e..0x14024b25b) plays the same cues 0–3 (M). Group-1 natives 0x1010–0x1013 are the music calls (“Music”); 0x1014 (0x14019d110) and 0x1015 (0x14019d1b0) were not followed.KO, time-up, win and lose: no dedicated cue was identified in this run; the phase handlers were not searched exhaustively, so a cue among the leads below is possible (L).
Battle cue sites not yet tied to an
event (leads, L;
enclosing function → cue): character code
0x1402528d0 → 0x24; 0x140254780 → 0x26;
0x1402549e0 → 0x43; 0x140254b30 → 0x4C;
0x140254c80 → 0x52; 0x14025c41d → 0x51;
0x140261a00 → 0x56 (slot card routine);
0x14026d368 → 0x0E; 0x14026dbd0 → 0x63;
0x14026f9f1 → 0x5B; 0x140271590 and 0x1402738d0
→ 0x61 (status routines); 0x1402517d8 → 2 (a
refused pickup); 0x14022bbd0 → 0x54; 0x140231660
→ 0x53. HUD class
(CBattle2DMenuClass): 0x140153716 →
4; 0x14015868a and 0x14015c310 → 3; 0x14017b94a
→ 0x57; 0x14017ba52 → 0x5E; 0x14017bd49 → 0x5D.
Audio run: the lock-on cue is
0x140153716 → 4 and the refused press is cue 2
(section “Battle UI cues” below); the character
code sites 0x1402528d0 (0x24 or 0x40 by
character id), 0x140254780, 0x1402549e0 (called
from the landing / reaction code 0x14025a1ba),
0x140254b30 and 0x140254c80 are movement and
landing sounds, not lock-on (the earlier
position-only guess is withdrawn).
Footsteps (M: read in code, the table checked as data, not against footage). The display-side player routine 0x140230d60(player, ground attribute), only in match phase 6:
Each foot has a record; a step fires when that foot’s contact field turns on and its cooldown is ≤ 0, then the cooldown is 10 ticks. Played at the foot joint’s position.
Cue = table 0x1402f6270[ground attribute][column] + foot (0 left / 1 right); 33 rows of two s32; −1 = silent; attributes ≥ 33 are silent. Column 0 when the character state (C + 0x12fc4) is 7..11, else column 1 (states 12..16 go through the twin routine 0x1402311e0 with the same table). Which states those are was not followed; two columns per surface fit “walk” and “run” (INFERRED).
Ground attribute column 0 column 1 0, 1, 14–20, 31 — — 2, 3, 5 28 30 4, 6 24 26 7, 8, 9 32 34 10 44 46 11 56 58 12 36 38 13 52 54 21..30 101 + 4 × (attribute − 21) 103 + 4 × (attribute − 21) 32 48 50 So each surface has four cues (two feet × two columns), cues 24–58 and 101–139 of the common bank. The attribute is the floor triangle’s attribute (“Collision attributes”); who passes it in was not followed.
Characters whose model flag (table 0x1404c0244 + model × 0xA0) is zero use another routine (0x140231490, not followed).
Implementation notes for the rebuild
- Countdown: at ready-phase ticks 0 / 30 / 60 play cue 632, at 90 cue 633, with the sprites above; drop any announcer placeholder.
- At the first battle start spawn effects 700 and 701 instead of playing sounds.
- Menus: cues 0–3 are the cursor / confirm / cancel / error beeps (which is which: listen, or read the scripts’ use sites); 200 at battle end.
- Footsteps: needs the foot-contact signal from the animation (not decoded) or a foot-height test as a placeholder; the cue table above is final.