Net rematch: what follows an online match

Read from the online menu scripts (Menu/battleend_<lang>.ssb, livelobbyres_<lang>.ssb, livelobby_<lang>.ssb, with ssbdump.py) and the built-in handlers in PDUWP.exe, checked against the capture timing in “Versus network messages” (after the knockout: battle packets ~2 s, then wrapper type 4, lobby types 10, 8, 7, 3, and ~9 s later the next type 2). No game text is quoted; menu rows are named by role. Grades: H read and consistent with the capture, M read in code, L guess.

Order (M, capture H for the packet side):

  1. Knockout → battle phases END and RESULTS; the battle packets run on ~2 s. The session itself never closes: the lobby phase returns from 7 to 1 (0x140187b70, which also reopens the session for joins and lets the host draw a new stage variant), and the lobby exchange starts again on its own (type 7 / 8 until each member’s info and completion are in again, then type 3).
  2. Each side goes through its own result screens: battleend with game kind 1 (online) plays the win / loss / draw banner scene, its confirm goes to the results-list scene and then to a last scene that ends the menu (fade out, 0x2041). Then livelobbyres (54): it stops the music, loads its texture set once (0x42A2 / 0x42A3) and goes straight on to livelobby (44). Nothing on these screens talks to the other side.
  3. In livelobby each side sees the lobby again. Host (local slot 0, 0x4238 = 0): its main tick counts up a counter while 0x4239 holds and resets it otherwise; 0x4239 (0x140213b40) is 1 on a client and, on the host (flag bit 2 of 0x1405277cc), the all-complete check 0x140191910: at least two members (0x140527a34 ≥ 2) and every member’s info in. While the counter is ≤ 20 the host’s help line is the “locked out” one; once it is > 20 a fresh A or Start (pad bits 0x10 | 0x1000) runs 0x4237 (0x140213b20 → the start routine 0x140187e80: draws the start order, clears the clock-sync state, sends lobby type 2, lobby phase 2). Client: no start of its own; its help line is the client one.
  4. Every side’s lobby tick checks 0x4236 (0x140213b10: lobby phase 0x140527920 == 1); when it is no longer 1 (the host’s type 2 arrived and moved the phase to 2) the script goes to the battle start (fade, then the loading screen). The match is a full new battle start (H from the capture: new start table with a new order group, tick and every message sequence from 0, the same tick-0 burst: capsules, status slots, message 22).
  5. While waiting the lobby takes, on both sides: X = an options list (character, arsenal; the host also stage, kick, open / close the session; the client leave), B = leave the session (a confirm dialog), a third button on the host = 0x4356 (L: a player card). So arsenal and character can change between matches on both sides and the stage on the host (M, from the rows; not exercised).
  6. Leave: the session leave (FORMATS “Session control”, 0x140126aa0) sends wrapper type 6 to every member. A lobby whose built-in 0x4234(0) turns false (0x140213a80 reads the session’s member table; read as “member 0 gone”, L) shows the “session closed” message and leaves the lobby; a host whose client left keeps its lobby with one member, so 0x4239 is 0 and it cannot start until someone joins (M). A silent member is dropped after the 150-tick silence rule.
  7. Timeouts: none in the flow itself: no automatic rematch, no limit on the result or lobby screens (none found in the three scripts, M). Only the session’s silence drop (150 session ticks) and the 20-count hold before the host’s start. The lobby script’s count rate (its phase tick 0x140187460, a script command) is L (not measured; the lobby packets go out every 3rd count, 10 per second in the capture, which suggests 30 counts per second).

Open (L): whether battleend’s online scenes can be skipped by a start from the host while a client is still on them (0x4239 checks the info table, not the client’s menu); the meaning of the X list’s two middle rows (name card, voice mute by the look of the menu, not checked).

Implementation notes for the rebuild

  1. A rematch is a host decision taken in the lobby: the client signals only that it is there; the host’s start needs everyone present and a short hold.
  2. The rematch is a full new battle start (deal, health, positions, sequences), not a resume.
  3. Leaving at any point between the matches uses the normal session leave.