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.
initmenu: clears its state, picks the tip, calls 0x41CF (battle set-up), then runs the wait below.- Tip choice: a saved counter (0x20AE) is read, forced into 0..9, and stored back + 1 (so tips cycle in order, ten per group, across sessions); a progress value (0x3173) picks the group: ≤ 1 → tips 0–9, ≤ 5 → 10–19, else 20–29. The 30 entries are static data in the script (a picture name and a text each); the picture is loaded through 0x2050 / 0x2051.
- Draw (the
draw_callback, every frame): full-screen rectangle (0, 0, 640, 480) in 0xff424038; two framed panel items of type 2 and style 0x8000: one at (218, 85) sized 333 × 254 and one at (88, 85) sized 127 × 254; the tip picture at (88, 85); a title bar rectangle (218, 85, 334, 25) in 0xff000000 with the tip title at (220, 87) in 0xffa5492a; a rule (218, 331, 334, 10) in 0xff000000; the text field (218, 110, 334, 220) in 0xff36362a with the tip text at (222, 114) in 0xff7c765d, line step 24, wrap width 330; a band (0, 374, 640, 104) in 0x80000000 at the bottom. Text scale 8 / 16, glyph spacing 0. A loading label is set once at start through the state built-in 0x2098(1, …). - Wait and exit: fade in (0x2055(1), wait 0x2056(1)); then repeat each tick until 0x41CC says every player is loaded and ready; then a fade out (0x2055 with 0x5502, wait 0x2056(2)) and 0x2040(1) (go to “no menu”) closes the menu system. There is no camera fly-in or “ready / go” art in this script.
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:
- task: no focus item, fade in (0x2055(2) / 0x2056(2)), music built-in 0x1014(15, 0);
- tick, stage 0: starts banner A = 0x801E(slot 0, set −2, sprite, 50, 3, 0) and banner B = 0x8028(slot 0, set −2, sprite, 255, 3, 0), stops the music (0x1011) and starts a music track (0x1010: track 37 or 38 by scene; corrected by the menus run, it is not a sound cue). Win uses sprites 85 (A) and 83 (B) of the battle HUD set (set −2);
- then a tick counter runs down; at 0 it starts the prompt blink 0x803C(slot 0, 0x00ffa516, …, 30, 0) and the scene waits for the confirm button; the confirm goes to the results scene;
- win / loss draw (corrected 11-12: the draw scene has banner B only, at (320, 150)): banner A at (127, 150) (0x801F), then banner B at (513, 150) (0x8029), and once the prompt is on, a centred line at (320, 412) through 0x803D (the confirm prompt from the system strings).
Banner objects
(result-banner object at
[0x140533450]):
- A (records of 0x68 from +0x48; draw 0x14022f500): the sprite is drawn repeatedly, centred on its point: a grey level v starts at the record’s value (50 at the start) and a height starts at the sprite’s height; each pass draws the sprite stretched to that height in colour (v, v, v), then v −= 3 and height += 3, until v ≤ 0: about 17 stacked, vertically stretched copies, a vertical glow streak behind the logo (the blend state set before it is additive: M).
- B (records of 0x70 from +0x1E8; draw 0x14022f670): the sprite once, centred on its point at its own size, colour 0x00ffffff with alpha = the record’s value; the tick 0x14022f630 first counts a delay down, then adds the step (3) per tick up to the target (255): a fade-in over 85 ticks.
- C (0x8032 / 0x8033, records of 0x78 from +0x3A8) and the timed text D (0x803C / 0x803D, records of 0x80 from +0xB70): used by the story scenes and the prompt; not followed.
Results list scene (online and system link only; corrected 11-12: the versus scenes close on the confirm):
- Order: the four slots sorted by place (an insertion sort in the script over a place built-in; an empty slot sorts last as place 4).
- Item 4, type 1, at (48, 51) sized 544 × 153:
caption = the list title; a header row; four
rows. A row is one rich-text line: the
name in a 200 px column, a
team letter centred in 40 px
(
A+ team in team modes, blank otherwise), then three columns centred in 80 px each: knockouts made (two digits), times knocked out (two digits) and money earned (four digits and a unit). An empty slot shows dashes. The header’s three labels sit over the three 80 px columns after a 240 px indent. The local player’s row is drawn in 0xfffbe92c; the first-place row gets marker sprite 177 of the battle HUD set at (row x − 12, row y + 3). - Item 2, type 1, at (101, 238) sized 427 × 81: the message box (which message: menu variable 4, set from the kind and result: plain result, wager won / lost, funds line).
- Item 3, type 2, at (101, 322) sized 427 × 81: the choice list (two entries; play again / leave in versus), item 5, type 9, at (203, 252): a small panel; a line at (212, 412) for the button help.
- Tick: on the confirm button (0x1025 bit 0x100) with a row of another player selected it plays a cue and opens that player’s profile (online); otherwise it goes on to the last scene, which shows only the list and the help line and ends the menu.
- What it computes: nothing beyond the sort; knockouts, deaths and money come from the game (the KO tally 0x1404bc970 and per-player words).
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
- 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).
- 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 withssbdump.py battleend_<lang>.ssb, functionsavslo…/avsdr…). - 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.
- Result code: treat 1 / 3 as win, 2 / 4 / 5 as loss, 6 as draw when choosing the scene.