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):

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:

Implementation notes for the rebuild