Match-flow screens (Menu/battlestart_<lang>.ssb, Menu/battleend_<lang>.ssb)

Read with ssbdump.py from the English files of the 2017 PC build. Positions are in the 640 × 480 menu space. No text is quoted: strings are named by role.

battlestart: the loading screen (phases 1–3)

battlestart is not a countdown: it is the loading screen that covers the load (phase 1), the wait for all players (phase 2) and hands over in phase 3. The “menu object” phase 3 waits for (0x14052ad98) is this script ending.

battleend: result banner, then the results list (phase 9)

initmenu reads menu argument 0 = the game kind (0 story, 1 online, 2 system link, 3 versus) and the battle result code (0x41C4: 1 and 3 count as a win, 2, 4 and 5 as a loss, 6 as a draw, anything else as a loss with a flag set), starts one of twelve scenes (kind × 3 + outcome; the story kind has its own clear / fail scenes), fades in and waits. With menu argument 1 set it first loads the Japanese HUD texture set.

Versus banner scenes (win, loss, draw differ only in the two sprites), per scene:

Banner objects (result-banner object at [0x140533450]):

Results list scene (online and system link only; corrected 11-12: the versus scenes close on the confirm):

Countdown, KO and time-up art. Not in these two scripts. The 90-tick ready phase (5) and the end phases (7, 8, 10) have no script menu; no code that draws the start / result logo sprites 81, 82, 84, 86 was found from the HUD class in this run (two battle-object functions load handles 83 and 84: 0x140226420 and 0x140220a50, not followed). Lead only.

Heavy mode’s menu entry: not looked for (it lives in the liverulesel / vsmode scripts; with ssbdump.py those can now be read).

Confidence. Screen flows and coordinates H for what the scripts do (read from the disassembly, both scripts self-consistent), M for the meaning of each built-in and so for “what a panel looks like”; banner A / B drawing M (draw read, tick of A not read); the row format H (read from the format’s escapes; the strings themselves stay out of the docs).

Implementation notes for the rebuild

  1. Loading screen: only needed if we want the look; our scene loads before the match. If built: the rectangles, panels and text settings above, tip text and picture from the user’s files at run time (never converted into the repo).
  2. Result banner (pd_hud.gd _result()): win = sprite 85 as the streak (A) at centre (127, 150) under sprite 83 fading in over 85 ticks (B) at centre (513, 150); music track 37 / 38 (by scene) at the start; the loss and draw scenes use the same two calls with their own sprite pair (read the pair with ssbdump.py battleend_<lang>.ssb, functions avslo… / avsdr…).
  3. Results list: the 544 × 153 list at (48, 51), rows sorted by place, columns 200 / 40 / 80 / 80 / 80 px, local row colour 0xfffbe92c, first-place marker sprite 177; the choice box at (101, 322). Our RESULTS phase already has “again / leave”: map them to the two entries.
  4. Result code: treat 1 / 3 as win, 2 / 4 / 5 as loss, 6 as draw when choosing the scene.