Versus-mode systems map
A survey of every system the multiplayer
versus mode needs. Each entry says what is
decoded (and where it is
written up), what the rebuild does with its
own behaviour (the
PLACEHOLDERS.md rows), and the
leads for the rest: function
addresses, the data they read, and how sure we
are. Later decode runs start from here. Formats
are in FORMATS.md; this file holds
the map, not format details.
Executable: PDUWP.exe of the
Store build 1.3.25854.2. Addresses are virtual
addresses (image base 0x140000000). Functions
are named by what they do. “Branch X” means
decoded in that branch and not merged into main
when this was written (11-03). Survey tooling
(disassembly indexes, string/xref tables, class
vtables) is on the data machine
(q.py str|refs|callers|callees|show|fn).
Confidence: H read in the machine code and checked against data or footage; M read in the code, meaning inferred from what the code does; L a lead only (location found, behaviour not followed).
How the executable is laid out
The build keeps MSVC run-time type information, so the code splits into modules by class. The class names are developer identifiers, not game text; they are listed here only as handles for the code ranges. Methods of a class sit together, so the ranges below are where to start reading.
| Range (approx.) | What lives there | Conf. |
|---|---|---|
| 0x140015e00–0x140016600 | main loop frame limiter, timers | H |
| 0x1400c5000–0x140100000 | platform services: online sessions, matchmaking, friends, saves, gamepad wrapper (0x1400dd380–0x1400dda40) | M |
| 0x14010a000–0x14011f000 | effect particle functions | M |
| 0x140128000–0x14012c800 | battle flow: the match phase machine (writers of the phase global, see “Match flow”) | H |
| 0x14012ea00–0x140148800 | boss characters (story only) | M |
| 0x14014ee70–0x14014fa60 | battle start: capsule placement, deck shuffle (0x14014f910) | H |
| 0x1401501b0–0x140155400 | battle HUD (2-D battle menu class; capsule icons 0x140151bfa, clock 0x140154cc9, player status panel 0x140155310) | M |
| 0x14015b270–0x14015d500 | deck files (load/save), character select | M |
| 0x14015e700–0x140168400 | menus (main, mission, pause 0x1674b0, shared menu 0x167d00) | M |
| 0x14016bf60–0x14016e000 | arsenal editor screen (the “n/30” counter at 0x14016d5f0) | L |
| 0x1401631a0–0x140164e00 | collision control and stage collision callbacks (player shot, object attack, object jump, moving object, structure) | L |
| 0x14017c630–0x14018c000 | game control, lobby, setup-file loader (0x14017da00 area), quick decks (0x14017df00), effect cache | M |
| 0x14018f940–0x14018fe00 | remote player state (net position, fire requests) | M |
| 0x1401ad000–0x1401c3800 | story event system (out of scope) | M |
| 0x1401c8000–0x1401da400 | stage: sky, intro camera, stage set, stage collision load and world (0x1d3c80–0x1d8400, query 0x1d5860; see §9), ground (0x1d9a30), net stage sync (0x1d9f80) | L |
| 0x1401dc000–0x140202000 | stage objects: ~100 classes (breakables, crumbling, rolling, falling, doors, jump pads, chairs, triggers) | L |
| 0x14021a000–0x14024500 | battle objects: capsules (0x21b270…), camera shake (0x21af70…), crash/collapse/destroy effects, glow, positional shake sources (0x22bf80), sound, menu sprites | M |
| 0x14024cf10 | character object constructor (4 target records of 0xC0 at +0x40, 48 skill objects of 0x1F0 at +0x4A0) | M |
| 0x14024d000–0x140276000 | character and skill-object code (status, aura, deck, reactions, movement, evade, casting, hits) | H |
| 0x14027c080–0x14027d100 | network message senders and receivers (table at 0x1403fb4d0) | H |
Shared globals: local player index 0x1404bbe00; per-slot character objects 0x1404bc9d8[4]; per-player status pointers 0x1404bc608[]; match phase 0x1404bc950; match mode 0x1404bc5dc; skill table 0x1404bdc50 (record = id × 0x90); gsdata buffer 0x1404c5228; capsule/deck block 0x140584f80.
Systems
1. Simulation clock and tick rate
- Decoded (branch gamespeed): a fixed 30 Hz logic tick with catch-up. The per-frame game step 0x1401c85c0 (called from the main loop 0x1400087c0 each iteration) keeps its own QueryPerformanceCounter clock (period = frequency / 30, 0x1401c860e) and runs the tick 0x1401c7630 while the next-tick time has passed, at most 3 times per frame (tick counter 0x14052dd6c), then drops any remaining backlog; it draws (0x140021e70, 0x1401c8110) only when a tick ran. The present call 0x140015e00 limits to 30 fps on its own clock (0x140015e85, Sleep(1), resync after two periods; sync interval 0, or 2 when the flag 0x1404bad22 or 0x1400218a0 says so; frame parity 0x1405b1584). No delta time in gameplay. Animation player: frame += rate per tick (0x140257510; rate 1.0 set at play, 0x1402573e0), length = the slot’s first 0x5 chunk +8 (bound at 0x140256bef): 30 key frames/s. H
- Ours: Godot physics at 30 Hz with physics interpolation for drawing (FORMATS “Game loop and tick rate”), at most 3 physics steps per frame (Godot drops the rest, as the game does).
2. Match setup and flow (countdown, time limit, KO, results)
- Decoded (branch combatrules): mode table (health, aura start/max, minutes) in gsdata 0x33040; timer = minutes × 1800 ticks (timer global 0x1404bc638, on-flag 0x1404bbe0c, custom settings 0x1404bbed0 + 0x356); phase global 0x1404bc950 with one counter 0x1404bc8c0 (6 = battle; 5 is the 90-tick ready phase before a round, 0x14012ade0, not the end: corrected in branch matchflow); slot out when no status record has health > 0 (0x24e000), KO tally 0x1404bc970 (4 × 4). H
- Decoded (branch matchflow): the phase machine (FORMATS “Match flow”). Per-tick dispatcher 0x140129ac0 (called from game control 0x14017cd00; jump table 0x140129e34, phases 1–12): 1 load (→ 0x1401282f0), 2 wait for all loaded/ready (0x140129fb0 → set-up 0x14012a110, elapsed ticks 0x1404bc63c = 0), 3 intro (0x14012ab20 waits for the menu object at 0x14052ad98, then battle setup → 6, or 5 via 0x14012ade0), 4 restart 10 ticks, 5 ready 90 ticks (→ 6 with the clock 0x1404bc8c0 = time limit 0x1404bc638), 6 battle (0x14012b110 → end check 0x14012c510/0x14012c58e; clock and elapsed ticks in 0x14012bdc3), 7 next round / retry 90 (0x14012b280; also the pause menu 0x140166f12…), 8 20 ticks then 0x140128fc0 → 4, 9 results (0x14012b300; waits for the choice 0x14012e4f0), 10 20 ticks (0x14012b4f0), 11 10 ticks then back to the menus (0x14012b600, 0x14012b7a0), 12 online 60-tick wait (0x14012bb00 → 9). H for the table and counters, M for the meanings.
- End check and result (H): standing teams 0x1404bc890[4] and latest knockout per team 0x1404bbeb0[4] from 0x14012c440 (status record +0x28 = elapsed tick at the knockout, set by the health routine 0x14024d7a0; standing while alive or knocked out within 60 ticks of the smallest player tick +0x24, M for +0x24). End when ≤ 1 standing or the clock < 1 (on-flag 0x1404bbe0c). Winner 0x1404bbe04 from 0x14012c8c0: the one standing team, else the latest knockout (first maximum), else (≥ 2 standing) −1. Places 0x1404bc5c0[4]; rounds left 0x1404bc9b0, round number 0x1404bc5e0.
- Network: “ready to start”, “draw timer” (the clock) and “kill count” are their own messages (see 21), so the countdown start and the clock are synced events.
- Ours (branch matchflow):
match.gdruns phases 4–12 as decoded (no load/sync/intro phases: the scene loads before the match), the clock from the mode’s minutes, the KO grace, the decoded result, rematch through 7 → 8 → 4 → 5 → 6, results with A = again, Start = leave. Host-authoritative: the snapshot header carries phase, time left, winner. - Decoded (docs 11-10, FORMATS
“Match-flow screens”): the phase-3
“menu object” is the
battlestartscript, and it is the loading screen (tip panel, wait until every player is loaded and ready, fade out), not a countdown or camera intro (H for the script, M for “nothing else runs in phase 3”).battleend(phase 9): scene by game kind and result code (1 / 3 win, 2 / 4 / 5 loss, 6 draw), two banner sprites (glow streak + logo fading in over 85 ticks, music track 37 / 38 by scene), a prompt, then the results list: rows sorted by place with name, team letter, knockouts made, times knocked out, money; a message box and a two-entry choice box (H layout, M built-in meanings). - Not decoded: the countdown
/ KO / time-up art of phases 5, 7, 8, 10 (not in
the two scripts; lead L:
battle-object functions 0x140226420 and
0x140220a50 load HUD sprite handles 83 / 84);
the heavy mode’s menu entry in the script (heavy
= game rule 4 of the lobby, docs 11-10 rules
run, §18; the lobby passes its game rule as the
mode; rated rules 0–2; lead M:
read
liverulesel/vsmodewithconverter/ssbdump.py); (the two start “cues” 0x2BC/0x2BD are effects 700/701, and the ready countdown is common cues 632 / 633 with HUD sprites 0x50 / 0x4F / 0x4E / 0x54 from the countdown object’s tick 0x14021a060: docs 11-10 audio, FORMATS “Match, menu and footstep sounds”); the story-kind result scenes and banner kind C.
3. Capsules and the deck draw (RNG)
- Decoded: capsule slots, refill 420 ticks, appear 15, models and colours, placement at the CP00 extra points (FORMATS “Capsules”; branch combatrules for the draw). Deck: 30 cards per player at 0x140584f80 + p × 0x190, draw pointer +0xC80. H
- Shuffle: 0x14014f910 at
battle start: 50 passes, each swapping every
position with a random one, C runtime
rand()(FORMATS “Capsules”, deck). H - RNG:
rand()(IAT slot 0x1402d3938) from 467 sites in 154 functions, gameplay and effects alike.srandis IAT slot 0x1402d3930 (the earlier 0x1402d38d8 is the first import of the next DLL, api-ms-win-crt-string; its call sites are compares): called at 0x14028af0a and 0x140291fab, both at start-up from the clock. One global generator, no match seed: peers stay in step through capsule messages (0x14014fb30 / 0x14014fbe0: player, slot, card, timer). H - Ours: the decoded shuffle
and draw with the UCRT generator
(
pd_rand.gd), seeded by the host’s match seed; the host deals both decks and sends the capsules (SPAWN events). Slot k refills at its point k with the card drawn at the take. Not modelled: the status 0x22 refill bonus, the stage move condition, card-swap effects (ledger rows).
4. Aura gain and costs
- Decoded (branch combatrules): regen 0x24de30 with the school-count factor (gsdata 0x33034), cost check 0x2620e0, level changes, aura capsule raises the level. H
- Ours: on main a flat regen (ledger row; replaced in the branch).
5. Skill casting (all kinds)
- Decoded: cast animation profiles (gsdata 0x1B00C), dispatch by behaviour 0x7A / skill set 0x52, the shot kinds, defense, mine, explosion, melee, rain…, hit test, line of sight, defense check (FORMATS “Skill kinds”). Card power 0x272400, hit 0x26f870, guard test 0x26f530, hit-effect dispatch (52 cases) 0x272bc0, card erase 0x272510 (branch combatrules). Skill objects: 48 per character, 0x1F0 bytes each at character + 0x4A0. H
- Decoded (docs 11-12, FORMATS “Open questions settled from the files”): the blast tick (31 tests, list order, full value at any distance, wall blasts hit the caster) H in code; the explosion look’s scale reaches the meshes M; the multishot flight routine (re-aim during the arc, straight after) M; the lunge end step re-read H in code; environment capture leaves an aura card, owner allowed H in code.
- Decoded (docs 11-10, FORMATS “Skill casting leftovers”): the dispatch tables (skill set × 24 bytes at 0x1403fb190, behavior × 24 bytes at 0x1403fb240, {init, update, third}) H; the damage formula table (.rdata 0x1402dd0a0, 33 routines by 0x56) and every formula the data uses, with the card power routine’s set 1 / 2 / 0 branches M (0 and 31 H); the use condition 0x48 / 0x4A (0x140262470) H; the erase set (0x14026fcb0: it acts on field capsules; target search 0x14014f700, filter by 0x54, effect by 0x56) M; the special set (0x140270200, 10-way switch on 0x54: high jump, teleports, capsule move, levitate, the two evades) M; ricochet (bounce in the stage collision routine 0x14026ca50) M; the kinesis cast side (object pick 0x14012e160, the object’s virtual calls +0x98 / +0x90, lift, flight, draw handler) M; mine mode 2 = a remote mine set off by a second button press (0x140263100 → 0x14026efa0) M. Corrected: the strength used against defenses is the attack’s damage (formula 0 is the plain one; 31 means no damage), so a defense stops an attack only up to its durability.
- Decoded (docs 11-13, FORMATS “The last unplayed skill records”): the 68 records main does not play, by reason; the card eraser 0x140272510 (candidates 0x5C, order 0x5E, count 0x60) and the slot erase 0x140262fc0 (0x4E = 2 guarded, 0x4E = 1 pays instead) H; the pre-hit triggers 0x14026f530 (auto-shelter, and the erase guard of 0x46 = 1 cards) M; set 6 = cast the remembered attack (button press 0x140261e90, P + 0x61AC / 0x61B0) M; a 0-power hit runs the whole hit routine H in code; the can-pay test 0x1402620e0 (level cost, hold count) H; hit effect 45 = teleport to the attacker’s start position M, 42 has no reader M; the stances (states 0x15 / 0x16, tick 0x14025b5e0) M; fast rain in full M; the end routine’s slot per reason and “close-range hits spawn no slot 2” H / M.
- Not decoded: the deck view (state 0x18, 0x1401582f0); what ends a stance besides the stick; the reader of the reaction row’s sound (row + 6); the kinesis object side (topic stage objects) and its candidate filters; the auto-shelter’s pass list; the levitate hold in the movement code; the follow-up ids 0x32..0x44. The 52 hit effects (0x62) and the status effects are decoded one by one (docs 11-10, §6); left there: effect 18’s handler.
- Ours: most records play as shots (ledger “Skill kinds”); test skills.
- Leads: the rest of the two pointer runs is not skill data: .data 0x1403fafb0 = three {name hash, handler} records for character model nodes; .data 0x1403fafe0 = the character module’s script command table (commands 16..53, listed with its siblings at .rdata 0x1402ddd08; per-command meaning not followed) M; .rdata 0x1402dd078 slots 0..4 = step types of a scripted camera run by 0x14027547f, slots 38..42 not followed L.
6. Status effects
- Decoded (branch combatrules): 47 status entries × 12 bytes at status record + 0x61B8; a few are used by the formulas (speed bonus, cost halve/double, strength, regen bonus, hit immunity 0x21). M
- Decoded (branch defstatus): slot read 0x14024d4d0 (base + timed + environment, clamped to the cap table 0x1402dcf30), add 0x14024d5c0 / set 0x14024d650, countdown in the per-tick character update (0x14024d30b). Environment effect type = slot number (0x140271660), which gives the slots their meanings. Status set handler 0x140270a00 → effect switch 0x140270b00 (23 ids). Hit-effect slots from the switch 0x140272bc0. Defense add-ons 0x140271ed0. The auto-shelter is in the guard test 0x14026f530. Block 0x140271760 (clears the defender’s hit-mask bit at 0x140271cb1; the hit tests 0x14026c1c0/c340/c5b0/c730 check it). FORMATS “Status slots”, “Status set”, “Defense”. H for the routines, M for the slot meanings.
- Decoded (docs 11-10, FORMATS “Status slots, hit effects and environments in full”): the complete 47-slot table with writers and readers: 9 forced target, 12 pickups locked, 13..16 button locks, 23 / 24 / 26 / 27 / 28 skill-type bans, 40 school-0 ban; 7, 10 and 46 unused (H for the readers, M for the unused ones); the skill-allowed check 0x140262d80 and the pickup check 0x1402517d8; health costs of slots 6 / 17 / 18; slots 8, 11, 12 cleared on a hit; status reset 0x14020d220; the status net message (slots 0..3 only) and the 64-bit slot mask in the position message. Status effects 9, 11, 15, 16, 19..23 (M; 20 L). All 52 hit effects, one row each (H for those the data uses, M for the rest). Environments: one entry per player in the list 0x14058bd30, a cast while one is active stores nothing, the oldest counts (0x14017c4c0), ends by time, hit effect 38 / 39, capture (pickup kind 3, 15 units, after 0x56 ticks), owner gone; the three environment net messages (H for the list and cast, M for capture and messages). How a status shows: cue ids 0x57..0x62, character effects 518 / 519 / 521 (slots 8 / 11 / 33), HUD sprite tables 0x1402f1200 / 0x1402f1298, button flash 0x1401509f0 (M).
- Not decoded: hit effect 18’s handler; the reader of P + 0x61b4 (hit effect 42); what a button holds after an environment capture; action states 0x15 / 0x16 / 0x18 (stances, deck view) and the deck view routine 0x1401582f0; the float start 0x140257b90; the draw side of the HUD button flash; the remote use of the slot mask (0x14018f940).
- Leads: the draw countdown (global 0x1404bc94c, restart 0x14012a6c0, message 15) is restarted by health changes and environment events: match flow (2). Script built-ins 0x14020e880 / 0x140211080 read and add any slot. L
7. Hit reactions and invincibility
- Decoded (branch combatrules): reaction pick by running damage (3 s window), action table types 0/1/2/5/11, down 30 ticks, get-up invulnerability length + 45, respawn 90, death 0x24d7a0. Reaction dispatch 0x24fd80 → 0x258690. H
- Network: a “no-damage timer” message exists: invulnerability is synced explicitly.
- Decoded (branch hitreact): the per-type slot pick (direction quarters, front/back), the state machine 0x0e fall/timed, 0x0f fall, 0x11 thrown, 0x12 down, 0x13 get-up, 0x1b dead (switch at 0x140256f53), lying 60/62 → get-up 61/63, thrown landings 50–55 by drop (docs 11-13 hurt: drop thresholds 40 and 80; a thrown landing costs 0 / 1 / 2 health in versus, a jump or fall landing never does: FORMATS “Stage attack bodies and landings”, M), floor slide × 0.85, 60 ticks lying after a throw, standing death action 25 (player tick 0x14024ee87), wall bounce 0x259b30. H
- No-damage timer (branch matchflow, H): character +0x6434, set to 90 by the respawn (0x140251f80) and the pit return, and to get-up length + 45 (0x14025c447); the draw is skipped on odd values (0x14024f4a4): the blink.
- Ours: reactions play on the character with root motion (INFERRED); wall bounce, follow-up actions, netplay-client reactions and client prediction of push missing (ledger rows).
8. Lock-on and targeting
- Decoded (H, branch lockon): FORMATS “Lock-on and targeting”. The lock lives in the per-player camera object at character + 0x13f10 (tick 0x140252a20 / 0x1402531d0): an index into a 32-entry target table (0x1404bcb50) of body records; valid = alive, not self, not a teammate (option), status slots 8 / 9; no range, angle or line-of-sight test. Pick = first valid index from a start (0x140252f70); switch = from index + 1; toggle on the lock button; grades 1 / 2 / 3 at 80 / 300 units; the camera turns toward the target. Casts fetch table[index] at cast start (0x140258180), lunge skills only at grade 1; shots drop a KO’d target. Locked runs: forward / sideways / back by stick sector (0x14025b6fc). The CPU’s lock comes from its AI script (0x14017b220, built-in 0x14020e650).
- Decoded (docs 11-10, rules run): the table’s fill order (registration 0x14024d440: lowest free index per body record, at character set-up, so slot order; M for the order of the set-ups) and the pad mapping (FORMATS “Pad input: buttons to pad bits”: table 0x1403dc710, right trigger = 0x800 lock, left trigger = 0x400 switch, left stick click or left shoulder = 0x1000000, right stick click = 0x2000000; pad objects with held / pressed / repeat words, update 0x1401d1250; H). The sorted-switch key is the distance from the player to each entry (FORMATS “Play camera”, tick step 9).
- Decoded (docs 11-10, vaim; M): the vertical aim of a cast, FORMATS “Vertical aim of a cast”: the cast pitch (C + 0x12f8c) is the tilt of the body matrix (0x1402514c0) that the shot spawn receives; locked = straight line from the caster’s centre to the target record position, unlocked = camera aim pitch; straight / ricochet / untargeted multishot use it, parabola solves its arc, moving / kinesis take the heading only. Leads (L): which body point the target record position is; crawl; the parabola landing point without a target (0x14026e410); whether the model is drawn with the tilted matrix.
- Decoded (docs 11-15, lockring): the lock-on marker, FORMATS “Lock-on marker: range colours, sizes, distance gauge” (update 0x1401536e0, draw 0x140153a10). The marker shows the lock grade: orange large ring ≤ 80 u (lunge skills home), yellow middle ring with a dot ≤ 300 u (range class 0), green small ring beyond (range class 1); the range test 0x140273c80 uses the same 300 u, so HUD and skills share two numbers (H). Aim point = the target’s body record position, no offset (H). Around the ring: a left arc with a rotating needle, the distance as int((d − 10) × 100) riding a 65-point table, the target’s name; a 10-tick closing-in on a new target with common cue 4 at its end, a 5-tick ring swap on a grade change (H number and gauge, M animations). No marker for a lost / KO’d / invulnerable target (the lock tracks nothing and the marker hides).
- Not decoded: the marker’s two render states (blend), split-view layout 2, the needle’s turn direction; the sort direction of the distance-ordered switch (0x140252ff0); the options screen entries that write the three lock option bytes (0x14052dfb7..b9); what the right shoulder, Start, Back and the d-pad do in a battle; keyboard bindings.
- Ours: table order (by name) until implemented, no sideways/back run animations (ledger rows).
- Leads (L): readers of pad bits 0x200 / 0x1000 / 0x2000 / 0x1..0x8 in the character code (input block C + 0x1425c); the options menu natives near 0x1401cb070.
9. Movement and physics
- Decoded: walk/run speeds and hysteresis, gravity 0.12 u/tick², fall cap, jump routine (0x270b00), evade (branch evade: charaset skill, jump/dash subtypes; press check 0x140251a50), landing states, action table (FORMATS “Player movement”, “The evade”). Per-tick character code at 0x253000 onward. H
- Body push (docs 11-10, M): player class virtual method 0x140250780: vertical overlap of the two bodies (centres feet + h/2, half heights), horizontal distance < (w_a + w_b) / 2 (w = body width +0x12EA4); the overlap is split in half between two locally simulated bodies, taken whole by the own body against a network-driven one. Docs 11-12 (doc-body, H for the place): it is the first step of the movement step 0x140254590 of every locally simulated character (run from the tick 0x14024ecf0 after the movement state machine), before gravity and the collision response of the same tick; network-driven bodies run neither; no state gate. FORMATS “Movement collision response”.
- Body numbers and body point (docs 11-12, doc-body, H): per-character height / width / radius / centre height tabled from the character table (playable: 18 / 19 / 20 u high, 10 u wide, radius 5 u, centre 9 u); the five named model nodes behind C + 0x13db0.. (hands, torso root, a helper, head) and the camera node behind C + 0x13de0; the body point C + 0xe0 (target record + 0x60: lock, sight pair, locked aim, hit tests) is the torso root node’s posed world position, radius C + 0x130 = the table radius. FORMATS “Character table”, “Body point, sight point and aim point”. Not decoded: the standing height of the node under the stance animation (rest pose 11.1–12.1 u by model); readers of the helper and left-hand nodes; the touch list the movement step files at C + 0x4f0 (virtual slot 0x80, 0x140250cd0, L).
- Floor test (branch gamespeed,
H): per tick 0x140254590 (gravity, fall
cap,
y += vy, position +0x12E40, vy +0x12E84, g +0x12E80, on-ground flag +0x12E74, last floor height +0x12E78, peak +0x12E7C), floor routine 0x140255020 (triangle loop 0x1402556e1: point in triangle 0x140291e10, normal y > 0.1 / ground > 0.643, snap 7.5 + move when grounded), leave-ground drop 5 units (0x1402548ba), stay-put states (0x140254879). FORMATS “Floor test”. - Stage collision (branch collision,
H): the stage file’s own collision set,
not the render meshes (FORMATS “Stage collision
(stNN.dat)”):
.datheader slot 0x94 = the arena’s shape list (small triangle meshes with one attribute each + one vertex record), slot 0x90 = per-kind entries whose words 0x18–0x20 are each object kind’s per-state lists. Load: 0x1402039fc → 0x1401d4070 (one world object per record, group 0x1000 / hits 0x4; attribute query bits ORed into the flags). Collision world: query 0x1401d5860 over the dynamic (0x1405302f8) and static (0x140530298, added by 0x1401d4e90) object lists, pair routine 0x1401d5130 by shape type (table 0x1402dc2f0), mesh pairs 0x1401d7c80 / 0x1401d7fd0 make the triangle contacts (corners, normal, the mesh’s attribute and flags). Shapes are made by 0x1401d3c80 (type, attribute), world objects by 0x1401d3ef0 (list, owner, group, hits) and moved by 0x1401d4e10 (per-type transform table 0x1402dc2a0). Structures (0x1401fbbc0): group 0x100, hits 0x44, one object per state list. The character’s probe (0x140254530): a sphere, attribute 0x22, group 0x1, hits 0x1900. Its wall passes and floor pick skip attribute 31 always and attribute 20 in reaction states 5 and 7 (contact byte 2 is the mesh attribute: docs 11-10, H). Ours: Godot trimesh bodies per attribute built fromcollision.json(PdData.add_collision_list). - Collision response (docs 11-10, M: read in the code, not yet checked against footage): the floor routine 0x140255020 runs a long-move segment guard (> 12.5 u, 0x140163950) or a guard plus 2.5 u sub-steps (0x140255e00, 0x140195f30), the round-arena limit (stages x1, radius 150, 0x1402559f0), the face pass 0x1401959c0 (three spheres r = w/2 at 0, −d, +d, d = h/2 − w/2; floor faces lift by the penetration, wall faces push along the normal, faces and contacts lower than feet + 7.5 u are stepped over), the edge pass 0x140195580 and the floor pick; one pass each, no step-up of its own. FORMATS “Movement collision response”.
- Attributes, masks, casts (docs 11-10): full attribute table (H for the character and shot skips, M for sight), the contact record, the group/hits table of every world object and the eight shared probes of the collision control, the shot cast 0x140163680 (stage + the players’ barrier objects), the ground attribute’s source (the floor pick’s contact, 0x1402558cb) and its surface sound table. FORMATS “Collision attributes, groups and casts”.
- Movement parity (docs 11-14, movepar, M: read in the code, no recorded run yet): the movement machine’s state table (0x140256e80, jump table 0x140257290; M + 0x04 is the action state: 1 walk / run forward 0x14025ad50, 3 dash, 4 windup, 5 air 0x14025b0f0, 6 landing, 8 turn start 0x14025b270); per tick in state 1 the turn step (0x14024f8f0), then the slow-down factor from the angle left after the step, then the move along the facing of the previous tick (the body matrix is rebuilt after the movement step, 0x1402512c0); directions from a 32768-entry float32 sine table (0x14054ca90); stick length unclamped, run flag 0.7 / 0.4; mode-table fields 3–10 are one-shot turn starts from a locked stand (full speed along the stick heading, facing = heading ± 90° / 180° until the one-shot ends); the air state steers every jump and fall at the run speed with the same turn step, without the status speed scale; landing and windup are bare countdowns; the roll goes along the facing, reads no stick. Collision details: a long move’s hit is backed off 1 u along the normal (0x140163950 returns point and normal); the contact list is static shapes in add order with reversed triangles, then dynamic objects (head inserts at 0x1401d4e90 and in 0x1401d7c80); the floor flag mover + 0x08 is the last floor-pick result, cleared by launches, not the ground flag. The Palace benches are placed objects (kind 9, structure class) whose seat is under the 7.5 u step-over: the decoded passes walk over them from the seat side and block from the back. FORMATS “Movement parity”. Leads: the bench against the game (a recorded run; the parity test plan is in that section), the C + 0x30 flag of the turn start, the one-shots’ drawn rotation, states 2 / 9, the turn rate’s integer store.
- Not decoded: which cast each skill kind calls (callers listed in FORMATS, L); the long-move guard’s hit response and the guard 0x140255b70 in detail (M); the readers of the blocking-wall flag +0x12E8C (L); the attribute 16 touch handler 0x14022ba20 (L); the loader’s query bits have no reader we could find (M); the body push’s caller is found (docs 11-10 rules run: movement step 0x140254590 from the character tick, FORMATS “Movement collision response”); the object order of the world query; the collision control callbacks 0x140164960–0x140164da0 (L, entry points only); the turn step, the turn in the air and the roll are in FORMATS “Movement parity” (docs 11-14 movepar). Ours: Godot’s CharacterBody3D wall handling and step-up with the decoded floor snap, ground angle and leave-ground drop (ledger rows).
10. Camera
- Decoded (FORMATS “Play camera”, docs
11-10): the whole per-tick play camera
(0x140252a20, 30 Hz, nothing per frame):
projection (H),
setup/configdata.datwith all 13 fields and their readers (H) and the record rule (options only; lock grades and team modes pick nothing), ideal points, the wall test (nearest contact to the look-at point, + 0.5 · normal, radius-1 push-out, look-at moved along), smoothing 0.625 / 0.375 (H), stick input (dead zone 13000, linear, x / y invert options), manual turn, re-center (N + 1 capped ticks), yaw-follow while running (|left stick x| · rate), the lock-on turn (yaw from the body, pitch from the drawn eye + offset; no difference per grade; pitch snap on release), aim pitch for casts, the snap on pit return / respawn, the spectator camera for a player who is out (com/stNN/camdata.cam: 64-point table per stage, 150-tick delay, spot pick with rand()), the per-target screen projection (reticle position, and the sorted switch’s distance key), and how shake is applied (per-slot sideways / vertical amplitudes, ±a/2 jitter of the look-at point per tick, cleared after use; positional sources with 1 − (d/r)² falloff and linear fade). M where not marked. Intro camera paths (stNNcam.alr) as before.preview/prevcam.datlayout only (L). - Not decoded / not there: no fly-in and no match-end or results camera were found (the player camera stays the view after the intro; M, absence read from the frame’s view set-up 0x14012bfc0). Reactions and KO have no camera code.
- Decoded 11-12 (doc-body): the look-at anchor pointer (character + 0x13de0) is the model node with packed id 0x511D082B, set by the model set-up 0x14025d380; it sits at the model origin in every playable model (FORMATS “Body point, sight point and aim point”).
- Leads (L): who creates the positional shake sources (0x14022bf80 is their tick) and with which amplitudes / radius / pattern, and the two stage-effect adders (0x14022106f, 0x14022124e); which flag a KO clears (character + 0x20 or + 0x24) and what game modes 4 / 5 are, for the spectator rule; the camera probes’ collision groups (created at 0x1401632d0–0x140163368); the preview scene’s point converter 0x1402759b0.
- Ours: the rebuild’s camera has the decoded framing, smoothing, walls and lock steps; the rest of the list above is not implemented (ledger rows).
11. Throwable objects and breakable props
- Decoded (docs 11-10, FORMATS “Stage objects: classes, hits and breaking”): how a placement becomes an object (class tables, three states per definition: intact, pieces, wreck); the per-object parameters stored in the model’s joints (hits to break 1–3, piece attack value); which bodies hit an object (the shots’ object body and an effect’s destruction sphere) and the hit counter; the break sequence (break effects, bodies removed, break sound, pieces launched or wreck state); objects are never respawned during a battle. Earlier: explosions break props unless collision 0x6A = 3 (FORMATS “Rules shared by all kinds”); PS00 prop placement.
- Decoded (11-10, same section): the pieces’ flight: launch velocity, gravity, the 8-point box simulation, stage collision of the corners, rest, fade and removal.
- Decoded (docs 11-13 piecepose,
FORMATS “Broken pieces: the start
pose”): where a piece’s eight points
start: which joints become pieces (parent =
joint 0 only), the box (stored bounds of the
joint’s first index buffer, inset), the matrix
(object × armature chain of the pieces model, no
animation), previous = current − velocity, no
first-tick special case, collision delay 0 or 8
(H, computed from st03 with
converter/piecebox.py); what the object’s stored point is (M). Palace deck section 1: the joint 5 piece starts inside the tree’s faces in the game’s own pose. Not decoded: what is drawn for deeper joints, when the stored point is refreshed. - Re-checked (docs 11-13 climb,
FORMATS “Broken pieces: the Palace climb
re-check”): pose, box, push-out and
attribute filter hold (H); the
pieces’ triangle grid (30 × 20 × 30 cells, flags
bits 0 and 1, stored normals) decoded
(H); crumble pieces get no
spin, roll pieces a four-sub-step one
(M); a two-stage “sink, then
crumble” component
ACrmFTfound (M, not on the Palace). Wrong before: the 36–44 unit climb of deck section 1 was called the game’s behaviour; footage shows only a small pop and a ~1.0–1.1 s fall. Lead refuted (climb 2, H): the launch / gravity factor record is an effect record of type 31 in the object’s state-0 effect list (floats 0 and 1); the Palace decks and railings have none (1.0 / 1.0) and gravity is 1.0 in all 21 records found. The climb against the footage is unexplained. Climb 3 (H unless marked): the “sphere pass” is an object pass: corners against the up-facing triangles of intact ceiling / faller objects’ meshes (the Palace deck sections), no clamp and no bound on the pop; deck pieces have an 8-tick collision delay (the deck class has flag bit 2; the docs and the build said it had not); the launch jitter is added after scaling, counter + 2 per jittered piece, seeded by the object’s creation index (M); a resting piece is deleted at once. With these the end sections match the footage (floor ~1.1–1.3 s, gone ~2 s) and section 1’s slab pops 10 units instead of 31–44, but the two tree sections still take 3–6 s in the port. Palace map: sections 0–3 at x 147 / 57 / −71 / −147, pillars 4–7 under them; the footage’s hit 2 = section 1 (M). Collapse 6 (11-14, H unless marked; FORMATS “Broken pieces: test order, constraint table and rest”): the build’s 25.6 unit climb against the port’s 10.4 was the build numbering the box points with the z bit flipped (first difference at tick 9, reproduced exactly); and both were wrong about two more things: the 28 constraints are a fixed table (12 edges, 4 body diagonals, 6 face diagonals twice), and a cell’s triangles are read in reverse order of insertion. With those the port gives 38 units for that slab at index 1. A resting piece is deleted (age above 32) and frozen whether or not it touched an object floor; “stays awake on an intact object” was wrong. Class flags: bit 0 = 2/12, 2/13; bit 2 = 2/22, 2/23, 2/26, 2/42, 2/43; 0x80 = 2/17. One placement list per battle (list selector + 1, else list 0), index = placement number from 0: the deck’s jitter index is decoded. The jitter counter advances only in the low-impulse branch. Not decoded: the spin’s scale; who sets the placement-list selector byte (0x140531dcf); who sets class flag 0x1000000; whether the game’s slab really rises ~38 units (footage angle cannot tell; L); the object pass’s own list order (M). - Decoded (docs 11-10 stageobj2, FORMATS “Stage objects: other families”): the class components and which classes the versus stages place (H counts); throwables, object side: joint float 1 marks a throwable and is its damage value, the grab removes the object for the rest of the battle and collapses what stood on it (H; only class 2 / 3, on st03, st04, st05, st06); support links and chain collapse (M); the stage object net events (hit, break at a time stamp, earliest stamp wins) and the hit reaction message, with corrected record layouts (H layout, M protocol); the stage clock.
- Decoded (docs 11-12 collapse,
FORMATS “Stage destruction: support chains and
the collapse family”): the link pass
and every component’s link test (flag masks, ray
up / down / both ways from the mesh’s bounding
sphere centre, the sphere touch test)
(M); the links of every versus
stage computed by
stageobj.py(support_links; H as computed: the Palace’s pillars and bridge deck sections hold each other, the deck carries the railings); support lost: one supporter is enough, same tick, pieces without impulse, not sent over the net (M); the crumble variant 2 / 23 (M); the collapse family as an animated state 1 on the stage clock with joint-driven collision (M); the break attack sphere from joint float 0 of the state 0 model (M code, H data: st06 only). - Not decoded: the collapse animations’ lengths and stream export, the special object 1 / 15 (0x1401eb800, 0x1401e77b0), what breaks class 2 / 53, the unused-looking neighbour record of the faller link pass (0x1401eafe0), the hit condition of AHitif, who sets the “pre-collapsed stage” byte 0x14052ad0f; the triggers of the crash / collapse / end-of-world effect singletons (0x140224430) and the fields of effect record type 0x09.
- Decoded (docs 11-13 hurt, FORMATS “Stage attack bodies and landings”): the category 0x400 consumer is the character’s movement step 2 (0x140250cd0): a body-sphere test per tick by each locally simulated character; a contact becomes a normal skill hit through the character’s own skill object (0x140263ce0) with one of two fixed skill records, damage = the joint value, filed under the victim (no credit, the breaker is hit too), with defense, guard, invulnerability and line of sight as for a shot; values 1–2 need the piece to move towards the character and remove it, values ≥ 3 pierce shields (M code, H records). A piece’s body is live only while its speed² > 1 per tick; the break sphere lives one tick (M). A fall of more than 80 and every thrown landing send a shot-type contact to the stage objects around the landing point (radius 10 / 15 / 20): they break props (M).
- Not decoded (hurt): how the break handler uses the contact’s value (1 or the landing severity); behaviour 18 and field 0x50 of the two records.
- Decoded (docs 11-13 landmark,
FORMATS “Surface marks: craters, debris and the
hard landing”): the crater. Landing
probes (fall > 80: radius 10; thrown: 10 / 15
/ 20), blast starts and shot segment casts leave
contacts on the arena bodies; the arena pass
0x1402021f0 keeps one contact per probe (sphere:
first mesh in file order, its last triangle in
range; segment: nearest to the start) and calls
the mark routine 0x14021d3f0: attribute → kind 0
/ 1 / none, a mark 1 unit off the surface in a
ring of 32 (the per-battle crash object, system
model entries 0x40 + kind), refused inside an
existing mark, removed when the camera enters
it; plus a debris request (kind 15), three
one-shot models, two dust sprites, a material
sound and a radius-15 destroy contact
(M code). The underside crater
on the Palace’s upper level follows from the
9-unit slab and the file order
(H:
converter/markprobe.pyon st03, Rebirth and Xbox footage): original behaviour, not a port difference. The older “no surface mark” statement is corrected. - Decoded (docs 11-14 crater, FORMATS
“Crater and debris models”): system
model entries 24 and up = the stage layout’s
MD00 pair list (model index into the stage ALR,
animation record index) (H, all
versus stages parsed); the mark model: an
inside-out closed volume, radius 24.57 on the
Palace, no animation there (H
data), drawn as a three-pass stencil carve that
shows the bowl only where a surface crosses the
volume (M code, look agrees
with the Rebirth close-ups); the debris manager
(60 requests, 20 kinds, parameters from the
model’s first 0x13 chunk, update, fade) and the
piece vertex shader’s motion with vertex format
0x1A (M code,
H data: kind 15 = 200 pieces,
90 ticks, fade from 50); the one-shot model
pools, lifetimes and fades (M);
the smoke is spawned on every mark request,
burst and fragments only with an added mark
(correction).
converter/craterconv.pyexports marks, debris kinds, fragments, smoke and burst. - Not decoded (crater): the check at the mark draw’s start (0x14057f418 ≥ 1.05, state 0x9A, 0x1402930d0); the piece pixel shader; the exe’s input layout for format 0x1A (the spin pair’s scale is INFERRED); whether characters standing in a crater are depth-cut by its depth write; st08’s extra entries 0x54–0x67; the fade colour word 0x14057f38c’s other bits.
- Not decoded (landmark): the mark’s net message id, the stage objects’ own calls of the mark routine (0x1401eaa20, 0x1401eac80), the reaction-path probe at 0x140259cbd (radius 20 at centre height), the per-pair contact limit 0x1405301f4.
- Leads: the collapse family’s per-joint records in the draw (0x1401eb6e0) and tick (0x1401eb610) (L); the crash / collapse triggers (L). A “capture environment” message pair exists in the net table (environment skills).
- Ours: props are static; shots don’t hit or break them (ledger row).
12. Arsenal builder rules
- Decoded (docs 11-10, rules run; FORMATS “Arsenal rules”): an arsenal is always 30 places, a skill or an aura card (−1); copy limit 3 in the editor’s add routine 0x140159db0 (result −3, limit switch editor + 0xb4c, default on; H, agrees with the 404 pre-made decks); school capacity (deck + 0x50, 1..3) tested by editor native 31 (0x140216cc0) on the script’s request (M); stock = owned − used in all saved arsenals (0x140170e40); rule flags (deck + 0x52, 0x14015b830) and the per-game-rule requirement table 0x1402dbc78 (one school, no duplicates, low cost, high cost; H, table read); checked when an arsenal is picked in the lobby (0x1402152d0), not again at match start (M). No aura-count rule, no per-skill limit field. The aura regeneration factor follows the capacity, not the schools used.
- Not decoded: how a new
arsenal gets its capacity; the editor’s script
side (
.ssb: messages, when native 31 is asked); the second counter set (editor + 0x68). - Leads (L): arsenal grant /
buy path 0x14012d820, 0x14015b7b0 → 0x14015ab90;
the editor native table 0x1403f1d50 (146
entries) for the remaining natives; menu scripts
Menu/arsenaledit_*.ssb. - Ours: builder limits until implemented (ledger rows “3-copies-per-skill rule”, “Arsenal school capacity”).
13. Playable characters
- Decoded: models and
skeletons (
Player/pcNNa, 11 playable sets;enmNNaare story enemies), animations, the evade skill per character (charaset +58). - Decoded (docs 11-09, H):
setup/charaset/charaset.dat, 47 records × 76 bytes, every column (FORMATS “Character table”): body height, width, radius, centre height, scale, turn rate (20° per tick for the playable cast), the lying-pose flags and turns per landing, the footstep and impact-sound flags, evade skill, voice bank. There is no speed column. Ours: not yet read byskilldata.py; ledger rows “Per-character body size, turn step”, “Air control turn rate”, “Lying pose after a thrown landing”. Character select: 0x14015c990 class, parameters filecharaselparam(0x14015ca20).
14. Stage hazards, out-of-bounds, fall-off
- Decoded (branch matchflow, H): the character tick (0x14024f16e) sends a body back when its height < the kill height global 0x140530070 (0 by default, −500 when the stage number ends in 9: 0x1401d1c29; stage object 0x1401e2dd0 sets its own) or its ground attribute (+0x12EC0) is 0x11. Return routine 0x140251d80: respawn point = own slot’s start record (0x14012a5e0, CP00 table 0x1405300a8, stride 80), placed by 0x1401646d0; damage −3 via the health routine; alive: no-damage timer 90 (+0x6434) and the “no-damage timer” message (0x140252400). Barriers: the arena’s collision-only buffers (FORMATS “Stage bounds”).
- Decoded (branch hitreact): the return then sets the reaction state (setter 0x140259d10, reaction object at character + 0x12f00, state at + 4) whatever reaction ran: with health left state 0 (standing) and the idle animation, else state 0x12 (down) in lying pose 60, which ends in the dead state (FORMATS “Reaction states in detail”). H
- Ours:
PdRulesPIT_* (the pit-floor stand-in on st03 only),Player.in_pit()/fall_back(),Combatant.fall(), blink inPlayer._process. The ground attribute is approximated (ledger row “Pit floor attribute”). - Decoded (docs 11-10): the ground attribute is the attribute of the collision mesh the floor pick grounds on (H); attribute 0x11 is in no stage file (all 21 checked), so only the kill height sends a body back in this build. st01’s attribute 20 walls are solid for a body except in reaction states 5 and 7 (the earlier reading was inverted).
- Decoded (docs 11-10 stageobj2, FORMATS “Stage objects: other families”): the jump pad (H): a floor contact on the pad’s body within 7.5 units, in reaction state 0, 1 or 8 during the battle phase, calls the normal jump with apex = the placement’s phase byte × 0.1 m (values 100, 120, 200, 250 on st07, st05, st08, st06), plus its effect and sound; the timed falling platforms of st08 (M code, H data: start second in the definition’s sound row, on the shared stage clock; sink, break effects, free fall, deleted below −100 units); the floating props of st05 (M / L); the table of hazards per arena (H counts). Doors, chairs, units and readables exist only on the town stage (st09): out of scope.
- Decoded (docs 11-13 hurt, FORMATS
“Stage sprite sets (SP00)”): the SP00
section and slot table (H;
spritesets.pywrites the UV table and sheets), sprite id = 3 + slot, the slot modes’ blend states (M); the highway’s far papers use slot 42 (cut-out, 8 × 8 frames), the near papers slot 43; the near papers’ spawn and update numbers (M); the storm sphere as a camera-centred model turned to the wind (M / L). - Not decoded (hurt): slot
mode 6, the sprite ids of drops and smoke.
(The sphere’s model, the
vkSANDshader and the camera point are decoded, next entry.) - Decoded (docs 11-15 stagefx, FORMATS
“Storm sphere,
vkSAND, piece impact sounds and the object hit mark”): the system model table’s stage half = theMD00pairs, entry 24 + pair (H); the storm sphere = st02 pair 70 = model 95, a radius-10 sphere with its poles on the wind axis and vertex alpha fading to the poles, centred on the eye (0x14023f020 = the camera’s world position, H), drawn at model size (M); thevkSANDmaterial (alpha blend, no depth write, two textures) and shader (sum of two scrolling layers × vertex colour, alpha × storm intensity; scroll rates in the model’s 0x13 chunk; no light, no fog) (H); the pieces’ impact sound = sound row word 2 with a speed and speed-change test of 1 unit per tick, cue values 36–39 (H, threshold source M);pdvkClpsModel2belongs to the st04 family and st08, its two cues have no position (M); the object hit path calls the mark routine unless the attacker’s callback kind is 1 (H gate). - Not decoded (stagefx): who
writes the shot callback’s kind words (which
skills leave no mark on an object); the creator
of
pdvkClpsModel2; the sphere’s place in the draw order against other blended draws; texture 45’s content (not converted); Xbox side of the sphere; no comparison by ear of any collapse sound. - Not decoded: the falling platform’s per-object sink step, tick count and acceleration and whether its collision moves with it; the floating props’ period and collision; what jump kind 4 changes in the airborne code; the jump-point effect’s fields; the routine that sets its own kill height (0x1401e2dd0: not identified as one of the classes read in this run).
- Leads: falling platform numbers (M: 0x1401f3780 and the constructor); jump kind 4 (M: 0x140257b90’s kind switch); floating period (M: 0x1401f3c40); the kill height setter’s owner (L).
15. HUD and menus
- Decoded: capsule icon type mapping (table 0x1402f1278).
- Data the game uses: battle
HUD textures in
Menu/BtMenu<lang>.alr(an ALR with textures, read by 0x140150250/0x140150360); a 1 MB bitmap fontSystem/dbfont.ddx(plus a Korean one) drawn with thefont2shaders; DirectWrite/Direct2D andmedia/ArialUni.Ttffor online UI text;media/dlcustom.xpr(unknown, 6 MB). Menus are scripts:Menu/*.ssb(one per screen and language; versus:vsmenu,vsmode,vslobby,livearsel,livecharasel,livestagesel,liverulesel,battlestart,battleend) with their textures inMenu/*.alr. L for everything but the file list. - HUD code (M): 2-D battle menu class 0x1401501b0–0x140150c30; card/capsule panel 0x140151cb0; clock 0x140154cc9 (draws “mm:ss” on its own back plate); per-player status panel 0x140155310 (numbers and name plate; not followed further).
- Decoded (hud run): the
battle HUD sprite table, layout tables and the
main elements (FORMATS.md “Battle HUD”); Godot
draws them (
pd_hud.gd). Font, animations and status icons are still open (ledger “Look: HUD”). - Decoded (docs 11-09): the
dbfont.ddxatlas layout (FORMATS “Font atlas”). - Decoded (docs 11-14, uifix; FORMATS
“Arsenal editor input, skill card panel, screen
frame and the aura card”):
- the screen frame: a fixed 853:480 area fitted into the window with bars (0x140021e70, constant 0x1402f7e70; H), every 2-D and 3-D viewport mapped into it (0x140021710); the 2-D space is 853.25 × 480 with the 640 design area centred (M). Ours scales by window height from y = 0, which is right on 16:9 and 11 % too large on the Deck’s 16:10;
- the arsenal editor: item types 8 (detail panel), 9 (skill card), 12 / 14 (stock lists), 16 / 17 (name header, grid); the card follows the cursor every tick, no button or paging (H); grid of 3 × 10 places + 3 buttons with its move table, stock list with LT / RT paging and type tabs (M);
- the card routine’s arguments (style strip with number and rarity marks, frame flag); the description is one text, drawn by every caller (H);
gsdataheader (record count 753), text entry lookup by index → position, missing → 0 (H); the aura card is skill record 0 (deck build 0x14014f830; H). The converter scanned past the table and dropped record 0: fixed (skilldata.py, synthetic test);- slot icon corners, cost number and name text anchors on the ring (M).
- Not decoded (uifix): name plate piece arithmetic (0x140152b09), the (24, 12, 616, 468) rectangle of the 2-D viewport setter, the versus arsenal pick’s contents view, detail panel labels (0x14016f2c0).
- Decoded (docs 11-10,
hudtext):
- the bitmap font (FORMATS “Bitmap font and
text drawing”): width table 0x1402dd2c0,
code-point → cell map 0x1402dd3c0 (UTF-8 in,
Windows-1252 first rows), glyph quad and scale
rule (8 / 16 = 1:1, 7 / 14 = 7/8), text state
globals, corner colours,
font2blend, rich-text escapes and glyph modes, HUD digits = atlas row 116. H - HUD status icon row 0x140157860 and the clock’s truncation and last-minute pulse (FORMATS “HUD status icons and clock”). H / M
- the menu script VM: all 32 opcodes, thread
layout, built-in groups, the menu engine’s item
records and ~50 built-ins (FORMATS “Menu script
VM”); disassembler
converter/ssbdump.py. H opcodes, M built-ins.
- the bitmap font (FORMATS “Bitmap font and
text drawing”): width table 0x1402dd2c0,
code-point → cell map 0x1402dd3c0 (UTF-8 in,
Windows-1252 first rows), glyph quad and scale
rule (8 / 16 = 1:1, 7 / 14 = 7/8), text state
globals, corner colours,
- Decoded (docs 11-10, menus)
(FORMATS “Menu engine, menu table and screen
graph”):
- the menu table (87 ids → script names, saved words), open / go to / back and the history, the native openers and the return-menu rule. H
- the per-frame tick, scenes, the event code → task suffix table, item records, the item type table, list input with its four cues (confirm, cancel, refused, move). M
- texture sets
(
Menu/<Set>.alr= sprite tables only, layout lives in the scripts; 19 files checked), sprite and text built-ins, the fader, the menu services built-in. H sets and fader, M rest - groups 0 / 1 as used by menus (music, pads, cues), the data queries for arsenals, stages and characters. M
- the split-screen versus path end to end:
settings block, the setup function, screen order
title→playdatasel→mainmenu→vsmode→vsmenu→ battle →battleend→vslobby→vsmenu. H - the pause menu’s scenes and rows; the online screen graph; the session settings stepper (heavy mode = rule row 4); the one-on-one CPU battle’s data sources (CPU deck comes from the online service). M
media/dlcustom.xpr(Xbox packed resource) andmedia/ArialUni.Ttfare not referenced by the executable. M- corrected: 0x2040 = go to menu id, 0x1010 / 0x1011 = music, 0x20AE / 0x20AF = per-menu saved words.
- Decoded (docs 11-12, title)
(FORMATS “Title screen drawing”):
- built-in 0x6023 in full: pass order, every quad (logo in two layers, start prompt, nine flame sheets, legal line), the cloud plane with its projection, UV scroll and pixel formula, the five-level glare chain and its blur, blend modes, the gold colour set. H tables and sprite use, M the 2-D transform and colour channel order
- the tick’s four levels (A, B, C, D) and the frame counter per state, intro 126 ticks, leave 50 ticks. H
- pictures come from
Menu/FDLogo.alr(12 sprites);Title_Logo.binis a sound bank only (corrects the menus note);Menu/Title.alris unused. H / M - movies are started by the profile script (logos movie, three idle demo movies after 1800 ticks), not by the title drawing. M
- Not decoded (title): what the movie open built-in returns for a missing file; the shared dialog 0x140169d60; the alpha reference value in the title passes; the jingle cue inside the title sound bank calls (0x8049 / 0x804A).
- Leads (title): movie open 0x1401b1680 and class 0x1401bd160 (M to finish, small); 0x207F = renderer query 0x1400218a0 (L); colour pack helper 0x1401356f0 (H to confirm in minutes); a footage check of the intro timing (H once recorded).
- Not decoded (menus):
arsenal editor screen logic (group 5, 45
built-ins) and the script side of native 31;
livecharasel/livestagesel/livearselinternals and the character select parameter file; shared menu class 0x140167d00; window border sprites; item types 6, 7, 10, 12, 13, 16, 17, 19, 20; lobby packets. - Leads (menus): type table
0x1402dcaf0 and frame helper 0x14016cb40
(H to finish the window look);
arsenaledit+ handlers 0x5011–0x508E (H, needed for the arsenal builder 1:1); 0x14024c500 kinds and the threelive*selscripts (M); stepper 0x140183010 skip rules (M);MenuD/folder purpose (L). - Not decoded: the status
panel 0x140155310 beyond the element list (other
players’ rows, health drain), slot flash frames,
damage numbers, the clock pulse counter
+0xc44; menu item types’ draw functions (0x1402dcaf0), the fade object, the script loader / import records, most built-ins; every menu screen other thanbattlestart/battleend. - Leads: status panel: read
0x140155310 around its two icon-row calls
(0x140157276, 0x140157806) H;
menus:
ssbdump.py --callsper screen, then the group tables at 0x1402ddd00 H; damage numbers: probably a 3-D effect, not the HUD class L.
16. Audio
- Decoded: sound banks, skill sounds, cast voices (FORMATS “Sound banks”).
- Music (docs 11-10, H): the files are now in the dump (from the Deck’s install of the same build). Decoded: container header, the track table, the play function, the menu tracks and the stage → track table of the battle scripts (FORMATS “Music”). Ours: no music yet; needs a converter step (STHD → PCM) and the player.
- Music payload (docs 11-10 audio, H for layout): 16-bit PCM, planar per block with a fixed 0x3F0 channel stride, short blocks before the loop start and at the end; loop start = a block index, loop end = end of file; channel 0 left, 1 right (FORMATS “Music payload”). Not yet listened to.
- Stage ambience (docs 11-10 audio,
H): bank =
MapSE*by stage ones digit (file table 0x1403f2b60 entries 70–78, loader 0x14021a6a0), registered as bank slot 1. Played by EF00 sound emitter entries (types 0x0B/0x0C: held or interval one-shots, positional or not, common or stage bank) and by a few stage effects (storm bed with intensity volume, thunder, sparks, steam, collapse): FORMATS “Stage sounds”, dump toolstagesound.py. - Match and menu sounds (docs 11-10 audio): no announcer exists. Countdown = common cues 632 ×3 and 633 with four HUD sprites at ready ticks 0/30/60/90 (H); menu sound native 0x102b with cues 0–3, 37, 200 (H); footsteps = table 0x1402f6270 by ground attribute × two columns + foot (M) (FORMATS “Match, menu and footstep sounds”).
- Not decoded: which event each remaining battle cue site belongs to (lock-on beeps, card pick, KO / time-up if any: site list in FORMATS, L); the footstep trigger’s animation side and its two state columns; the effect sends’ bus (ids 11 / 12); natives 0x1014 / 0x1015.
- Decoded (docs 11-09, H):
DSP_*.binare Xbox DSP effect images that the PC port loads and frees without applying (closed).setup/soundparam.dat: per-cue flags, distances, curve and spread in 44 groups (FORMATS “Sound parameters”); the PC port reads only the positional flag (bit 4) and bit 3 (held cue, docs 11-10 audio). Ours: the positional flag is not used (ledger row). Corrected (ambient run 11-14): the port reads the whole record; next entry. - 3-D sends, listener, volume classes (ambient run 11-14, H; the listener M): soundparam bits 0–1 = volume class (four class volumes, 1.0 in a match), near / far / curve / spread drive the 3-D send routine 0x140241440 (linear or two log curves, silent beyond far, five speaker directions around the listener, width from spread × far). The listener is the local character (position and facing), set by 0x1402403a0 from the camera commit. 84 request slots, re-panned each tick. Event word 0x1C = length in ms (ends looping events). FORMATS “Stage soundscape, 3-D sends and the listener”.
- Soundscape check (ambient run
11-14): with no skill use the Palace
plays 1 bed, 10 held water points and 6 drip
emitters from its stage bank; st02 a bed, the
storm bed and the paper loop. Ours plays
none of it (no
MapSEbank converted, EF00 sound entries unread), nor footsteps and movement cues. Not confirmed by ear (music masks the recordings). - Stage object and collapse sounds (docs 11-15 stagefx): an object has three sound values: hit (word 0), break (word 1), and the impact of its flying pieces (word 2, cue values 36–39 → common cues 191–198, H), all through the one 64-entry queue. A Palace or Highway collapse has no stage bank cue; the collapse model object’s stage cues 1 / 2 are st04 / st08 only (M). A stage attack hit plays nothing of its own (H). Ours: hit and break values are queued, the piece impact is not.
media/Sound.xsb+Wave.xwb(docs 11-10 audio, H): unreferenced by the executable and every shipped library; a leftover, nothing to convert (FORMATS “The XACT bank”).- Engine: XAudio2 behind a DirectSound-style wrapper (class names “myDirectSound…”).
17. Controller rumble
- Decoded (docs 11-10 audio, H): the PC build has rumble. Feedback manager 0x140533428 sums left / right motor values per pad slot (added through 0x14022c660), the send step 0x14022c480 gates them (phases 5/6/9, vibration option, pause, pad connected) and calls the Windows.Gaming.Input vibration setter through 0x1400de3f0 (trigger motors unused). FORMATS “Controller rumble”.
- Sources: (1) the cast rumble sequencer fed from the cast animation profile fields 0x0A–0x4B (end mode, five steps, three release steps; right motor only in the data), local player only (H); (2) the positional shake sources, shared with camera shake (10), same falloff × fade × pattern (M); (3) EF00 screen-shake entries and the stage collapse, right motor (M).
- Not decoded: the shake sources’ creators and numbers (same gap as camera shake); the constants of the two stage sources.
- Ours: none (ledger rows).
18. Teams (2v2) and versus options
- Decoded (branch combatrules): 4 player slots, team number per slot (+0x1C), ally search 0x1402516a0, KO tally per slot pair. H
- Decoded (docs 11-10, rules run;
FORMATS “Versus options, stage list, teams and
start spots”): host options = game type
(0 free-for-all up to 4, 1 team battle, 2 one
against one; 0x14050d2d8), game rule 0..11
(0x140518cf0, type-dependent subset, stepper
0x140183010), stage, rating limit, private
slots; game rule = match mode
row (heavy = rule 4), no handicap and
no separate health / time option
(M). Online set-up 0x140187710:
team = side byte in a team battle, else slot
index; game mode 5 / 4. Stage list
setup/stageset/stageset.dat(17 selectable stages, variant count per stage,converter/stageset_dump.py; H); the host draws the variant at random. Start spots: start code → CP00 set and record (0x1401d1da0); online: set 5 or 6 at random, shuffled (0x1401907a0; H). Friendly fire: no team test in the hit code (M). Session attributes (0x140182b60): the “required / sent skill” values belong to trade sessions. - Not decoded: who writes the team side bytes in the lobby; respawn rules (if any); rules 3, 5, 10, 11 beyond mode row and arsenal requirement; the team rating average; the two three-way search filters.
- Leads (L): lobby natives 0x140213bd0–0x140215f80 (the side choice is among them); the start message pack side of 0x140191b40; the three status records per slot and the knockout routine 0x14024e000 for lives / respawn; rating 0x140188290.
- Ours: 1v1 only (NETPLAY.md); ledger rows for 2v2 / 4-player, start spots, stage variant draw.
19. CPU opponents (in scope from 11-10; docs 11-10 cpu run)
Full write-up: FORMATS “CPU opponents”. Dump
tool: converter/comdata.py.
- Decoded
- The one versus-vs-CPU battle (the
multiplayer menu’s one-on-one CPU battle,
built-in 0x4295): script
eneprog006.ssb, parameter record 20, no deck file, two players. H - Its deck (docs 11-12): the arsenal of the ranked player picked on the online ranking list (built-in 0x4293 fills the deck record 0x1404bc8e0; 0x4294 polls the download). No offline source. H
enemyparam.epa: byte 0 = the CPU’s start health, bytes 1..9 = AI script variables 30..38 (target selector, decision interval, four action percentages, a roam percentage, movement style, a check kind); record series of five strength steps. H layout, M meanings.comdataN.cad: vertices, up to 128 quad areas, edges, two point lists, five route sets over a shared byte pool; file choice by stage id mod 10 and variant. H (checked on st02–st04, st06–st08; st05 does not check clean).- The CPU player object and AI controller (50
integer + 20 vector variables, the script
thread), and the tick: input block reset →
mainfrom the top, 50,000-instruction budget, every 30 Hz tick → lock from the script’s target slot (grades at 80 / 300 units) → navigation → steering into the input block. H - Decisions become inputs: pressed slot bits, the evade bit with a heading, move strength and direction in the same input block a human’s pad fills. No reaction-delay or aim-error field exists; difficulty is the percentages. H / M
- The built-in table of group 4 (about 95 ids,
all 75 used by
eneprog006). M
- The one versus-vs-CPU battle (the
multiplayer menu’s one-on-one CPU battle,
built-in 0x4295): script
- Not decoded
- The route follower, stuck recovery and stage-object avoidance line by line.
- The character choice in the CPU battle start (0x1401907a0, read as a random pick: M).
eneprog006’s decision tree (not needed if the script is interpreted).- Area flag bit 1, the area record’s first 16 words, the per-area byte, point lists.
- The compact st01 nav file, the 660-byte
decks,
single2.csv’s consumer.
- Leads
- 0x1401776c0, 0x140177f60, 0x14017a1a0, 0x14017a750 (navigation insides). M
- 0x140183e80 writes the in-memory deck record 0x1404bc8e0. M
- Run the menu script
livedbtlthroughssbdump.pyfor the character / deck choice. H - st05: compare
comdata0withcomdata1/2and the edge table’s use at run time. L
20. Online services around the match
- Lobby, matchmaking, sessions, chat,
leaderboards, trading (classes
0x1400c5000–0x140100000, lobby 0x140187330, live
task 0x140180c10). Not needed: our netplay has
its own lobby. For the compatible net mode
(docs 11-12 netcompat) the session
document and the device addresses are what the
platform supplies; Rebirth serves them from an
EOS lobby (
converter/NETCOMPAT.md, sections 3 and 4).
21. The original network model
Full write-up: FORMATS “The original network protocol (executable)” (docs 11-10).
Capture-verified (docs 11-14 netmsg; FORMATS “Versus network messages”)
- Layouts (H): every datagram
of two loopback captures of a live 1v1 (41 614,
of them 33 771 battle packets) parses to its
exact length with
converter/netmsg.py: 7-byte mesh header, 8-byte wrapper, 0x18 header, mask / table order, the 26 sizes, sequence after each reliable payload, acknowledge bits 26 + (type − 2). - Behaviour seen (H): 15 packets per second, tick / 2 + 1 per packet, tick 0 held ~3.4 s for the start burst (capsules, stat slots × 3, ready); resend after exactly 6 packets; acknowledge in the next packet; heartbeat every 2 s; lobby at 10 per second; ping only in the lobby; the victim sends hit log, damage effect and the end of the attacker’s shot; capsule message at each take with the next card; environment entry, capture request and the aura card answer; draw countdown flag at tick 3600.
- Corrections (H): start order = 4 × g + permutation (g 5 or 6); lead word is in every packet and read only at tick / 2 mod 30 = 15; message 0’s target byte is the opponent from tick 0; facing is 16-bit; stage event wire order (stamp first, stamp = elapsed × 2 + player index); message 5 comes mostly from the victim; message 3’s 16 floats are a 4 × 4 transform and 0x56 is the cast profile record.
- No checksum, version or signature in the game’s layers: a peer is judged only by lengths, the 0x1200 word, its member id and sequence duplicates.
- Not exercised by the capture (stay M): hello and the join / leave messages, messages 4, 12, 13, 16..18, 21, 25, lobby types 5, 6, 9, 21, three or four players.
- Layouts (H): every datagram
of two loopback captures of a live 1v1 (41 614,
of them 33 771 battle packets) parses to its
exact length with
Decoded
- Message table (H): 0x1403fb4d0, 26 entries of 40 bytes {u32 size, u32 reliable, u64 queued, sender, receiver, name}; senders 0x14027c080–0x14027c4d0, receivers 0x14027c4f0–0x14027d040. Payload struct of every message, who sends it when and what the receiver does (M; stage messages 6 / 7 only by layout, L).
- Packet (M): 8-byte datagram wrapper, 0x18 header {u64 presence mask, player index, tick / 2, lead report, one more word}, messages in table order without type or length bytes, a u32 sequence after each reliable payload, acknowledges at the end. Own reliability layer: resend every 6 packets until acknowledged, duplicate lists of 10 + 50. Send 0x14027abe0, receive 0x14027b870, manager 0x140527bd0.
- Rate (M): one game packet per peer every 2 ticks = 15 per second; position and button cards in every packet, each queued event type at most once per packet.
- Remote bodies (M): 16 samples at character + 0x16900 (decoder 0x14018f940), update 0x14018f330: straight blend between the two newest samples, no extrapolation; action id and animation frame come with the sample; casts through queued fire messages.
- Clock (M): no clock message; peers that run ahead stall (lead report every 2 s, ahead / 4 against 4 / 8 / 16 / 32), and nobody ticks while a peer is 60 ticks behind.
- Authority (M): peer to peer mesh, no host in the battle. Each machine simulates its own body, owns its deck and capsules and decides the hits it takes; every peer flies every shot from the shooter’s spawn parameters. Knockout tick and health travel in the position message; match end is checked by every peer on its own. No seed, no snapshot.
- Disconnect (M): a peer gone from the session is made inactive; one that stops sending battle packets is knocked out locally (0x14012cde0). No host migration.
- Mesh layer (M) (docs 11-12 netcompat): 7-byte message header {sequence, type, length, flags}, hello / heartbeat / acknowledge / custom 0x40; the game sends all its data as custom 0, unflagged; hello and heartbeat every 2048 ms, endpoint retries every 1000 ms; no filtering at this layer (the flag is created off).
- Wrapper and header (M): 8-byte wrapper {game length + 6, 0x1200, type 8, sender’s member id}; header word 0x0C doubles as the member count in lobby type 3, word 0x14 is a talk flag.
- Lobby (M; table H): dispatch 0x1403e8850: types 1..10 match lobby (player info 0x80 bytes with host-only stage / variant / type / rule, completeness, team change, start table with the host’s random start order), 11..20 card trade, 21 leave; the lobby tick 0x14027b480 repeats until complete; phases 1..7 at 0x140527920. No deck and no seed travel.
- Session control (M; table H) (docs 11-12 netcompat2): wrapper types 2 join request (address block, player key, private-slot wish), 3 join reply (member id 1..3, or 5 closed / 6 full), 5 member introduction (host → each member about each other), 6 leave, 4 keep-alive after 15 silent ticks, 10 ping / echo; a member silent for 150 session ticks is dropped; the host is member 0 for the session’s life (no migration in this layer). Types 0, 1, 7, 9 are leftovers without a sender.
- Mesh, to the end (M): no resend timer (a “send all pending” method exists but nothing calls it; the game never flags a message) and no heartbeat time-out.
- Lobby values (M): player info 0x38 / 0x3C = free private / public slots; the 64-bit value = a 0..999 999 counter of the save; lobby type 4 is dead; the menu choice is a script-defined integer (L for its meaning).
- Card trade (M flow): session game type 11, roles creator / joiner, types 11..20 as a nine-state exchange; a peer with role 0 ignores them all.
- Skill object net classes (M): 0x14026e860 gives each object a class 1..5 and the flags 0x200..0x8000 (who announces its end, whose word it waits for); position fields 0x1C / 0x1E are looping character effect ids; stage event bytes 0x10..0x12 = hit count, surface code, hit-kind flag.
- Rebirth mapping (from its public repository, described in NETCOMPAT.md): session = EOS lobby with string attributes, device address record with the EOS user id, EOS P2P socket with three channels, the game’s datagrams carried unchanged.
Not decoded: the name of the first value of “ready” (a per-player set-up value the receiver rebuilds the remote body with), the meaning of the lobby’s menu choice (in the lobby script), what the lobby script does when the host is gone, the platform-side host change handler 0x1400e89c0, the card routines of the trade (0x140185170 / 0x140185240), the update rate behind the session and lobby ticks. Nothing is verified against a capture (checklist: NETCOMPAT.md section 7).
Leads: “ready” value: source 0x1404bc8c0, applied by 0x140250480 → 0x14019e430; menu choice: the lobby script calling command 0x140213b80; host gone: script query 0x140216040 (0x1401842a0); stage message writers 0x140202224 / 0x140202570 / 0x140203dc0 (L).
Interoperation (assessment): not reachable with a packet translator. A compatible peer must run peer-authoritative (own body only, victim-side hits, own deck and capsules), fly every skill kind the same as the game, speak all 26 messages and the reliability layer, and join through the platform session (Rebirth: an EOS lobby and EOS P2P, which needs Rebirth’s product credentials), the session control messages and the lobby packets (both decoded). Build task list and gaps:
converter/NETCOMPAT.md. Ours is host-authoritative with snapshots and prediction (NETPLAY.md); a compatible mode would be a second net mode on the same combat core.
22. Skill effects and stage effect records (docs 11-12 effects)
- Decoded (FORMATS “Effect instances,
slots and joint attach”, “Stage effect records
by type”):
- The effect instance table, spawn, stop, loop and length (H); the six slots: 0 cast, 1 flight, 2 shot end, 3 release on the caster, 4 looping character effect, 5 its end / a hit on a character (H 0..3, M 4 / 5).
- Joints: rotation in radians, scale, name tags; every element sits on its own joint; a named joint rides the owner character’s joint of the same name, an unnamed one the instance root; the joint pair table (H layout and attach, M turn sign and pairs).
- Mesh matrix sources 3, 4, 5, 7, 8 and particle source 3 (M).
- The
.eftper-model draw layer (H field, L meaning). - The fire shot: texture pick confirmed right; the differences are joint transforms (hand / forearm / wrist attach, upright hit petals, flash 1 m up) and the release slot’s place (H data, M turn sign).
- Defense look = the skill’s own slots 0 / 4 / 5 (M); status effects 518 / 519 / 521 play slot 4 while on and slot 5 at the end (H table, M play).
- Stage effect constructor table by type; smoke (types 2, 3, 8) in full (H); crash debris request layout and model record (M); type 31 spawns nothing (H).
- Not decoded: (the debris
manager’s update and draw are done, docs 11-14
crater) the stage model draw (types 10 / 13),
the stage sprite draw and blend, types 4, 5, 6,
14 / 15, 21..24; the order of an element’s own
scale / offset against its joint; what the two
draw layers change; the particle rand seed; the
environment visual object; the consumer of joint
pairs;
msparticle00/01. - Leads: model draw object
pdvkEbModelExecvtable 0x14048cbc8 (M); sprite draw 0x140205d60 (M); pair consumer 0x1401130e0 (L); environment visual 0x14017b770 / 0x14017ba00 (L); mesh setup 0x1401a5940 / 0x1401a5ff0 for the element order (M).
23. Effects on the Xbox against the PC port (docs 11-10 xboxfx)
- Decoded (FORMATS “Effect packs and
the Xbox / PC effect comparison”):
- The pack format
e.i+aN.eand the PC load path; both builds play effects only from the packs (H). The PC’s loose effect files are an older revision the game never opens; 415 effects differ from the packs (H). Our converter reads the loose files. - Xbox packs = PC packs except for the storage order of uncompressed textures (H).
- Same 21 element functions and the same effect shaders on both; heat haze textures are converted correctly by the PC (H).
- Point sprites: every Xbox point program
against its PC shader; one wrong translation,
mseftbb01s(1407 elements in the effects of nine shot skills): the PC draws them at the Xbox size divided once more by the view depth, below a pixel at play distances (H for the math and constants on both sides, M for the 64-pixel console limit and the element’s position / colour update).
- The pack format
- Not decoded: the draw translation of msparticle00 / 01, thunder01, tale02, flair01, the blades and the full-screen filter on the Xbox side; how the Xbox reads the 510 haze textures that are not in the signed format; render states the PC maps differently.
- Leads: Xbox shader table
records by name (vertex program, 240-byte pixel
shader definition, 16-byte name record)
(H); Xbox element function
table 0x2bb1ac (H); PC
MSParticleclasses against the Xbox programs writing a point size at 0x2a8a78, 0x2a8c08, 0x2a8e20 (M); footage of skill records 42 / 53 on both platforms (capture request in FORMATS) (H as a check).
24. Stage sky, light sets and glow (docs 11-13 skyglow)
- Decoded (FORMATS “Sky and far
scenery draw”, “Glow pass”, “Stage light
script”):
- The sky object (
pdMapSky, draw 0x1401c87f0) draws stage model 1 (far scenery) under light set 3 and stage model 2 (the sky) under light set 2, the sky centred on the camera, then returns to set 0 (H). Selecting a set applies its fog states (H). - SC domes multiply by a grey vertex colour (format 0x09, +16) and blend per material (H: shader, data and footage).
- St02’s clipped white sky in the rebuild comes from the sky’s input (no vertex colour, wrong light set), not from the glow chain, which matches a CPU model of the decoded passes (H, renders).
- The sand storm, the cloud scroll and the capsule scroll run on one counter stepped by the 30 Hz tick from device setup; the storm is 105 s on / 105 s off since boot (H).
- (docs 11-15 skycol) Light set 2 carries a point light 0 (colour, range 5e6..1e9) on 14 of 19 versus stages; it reaches the cloud shader as c5 / cP0_POS (w = range) and saturates the point term over most of the dome. The rebuild zeroes it: st03’s purple sky (H: code, data, renders against xemu; FORMATS “Sky colour: set 2’s point light”).
- (docs 11-15 skybright) Stage model
2 carries untextured vertex-colour layers
(
svc/svcal, vertex format 0x0B) on 16 of 19 versus stages; the first is an opaque backdrop dome behind the clouds. pdconv drops them. St03’s is (76, 80, 102) over the upper sky: the missing half of its brightness against xemu (H: data in both builds, shader, renders to 0.01..0.03 of the xemu sky box). St03’s innersvcdome is wound outward and culled (H). FORMATS “St03 sky brightness against the Xbox”. (skycol2 11-15) Built: pdconv converts the 0x0B layers of model 2 and Godot draws them (PdData.vcol_sky_material); the frame clears to black. - (skybright) Xbox sky draw 0xb1580 = the PC’s: model 1 under set 3, model 2 at the eye under set 2 with depth writes off; selecting a set applies its fog (0x89440), so set 2’s fog is on for the whole sky; the cloud vertex program’s fog coordinate is the view depth (H, default.xbe). The cloud point vector leaves through a colour output clamped to [0, 1] (H). The PC battle frame clears to black; 0x2001 is only the shadow colour (H).
- The sky object (
- Not decoded: what
SVCuploads to c16, its fog coordinate on the Xbox (the backdrop reads as unfogged in xemu, M); the footage’s exact cloud phase; the render states 0x40 / 0x3C / 0x3B around the sky draw; the set 0 linear-fog override (bit 4 of 0x140530034, object id 0xe02713, 0x140199ce0); the glow paths of PLACEHOLDERS “Glow paths not modelled”; who calls the glow easing 0x14019a240. (ThevkSANDshader is decoded: system 14, docs 11-15 stagefx.) - Leads: Xbox draw of the sky
(default.xbe: the light set and fog state at the
cloud draw) (M that it mirrors
the PC); which stages besides st02 / st22 carry
a model 1 (L); the model draw
0x140293860 (ALR, sub-model index)
(M). (skycol) St03 in
xemu is still about 2 × our sky with the point
light on: settled by skybright (the dropped
backdrop). (skybright) The
SVCclass’s constant upload (c16) in either exe (M that it leaves the backdrop unfogged); the second set-2 selection at Xbox 0x10d94a (L); Xbox SelColor tap spacing for the glow (L that it changes this sky).
25. The straight fire shot against the game (docs 11-13 bofcmp)
- Decoded (FORMATS “The straight fire
shot, the rebuild against the game”):
- The stage, stage objects and capsules take the most recently allocated effect light as point light 0 under light set 0 (0x140199970, index 0x140527cc8) (H). This corrects the earlier “the stage gets no effect light”.
- Cast animation: slot 70, 40 frames, release tick 20, no root motion, feet planted (H).
- The flash and the red burst are the pack’s cast slot particle01 emitters and release slot 3; the game plays both (H).
- Spark size is the one PC-port difference (sub-pixel point sprites); the rest is the same on Xbox (L, footage).
- Not decoded: why the rebuild’s additive particles stay red where the game’s saturate; the gate that keeps the skill card away at a cast press (slot field +0x3C, input mask +0x1425c); the character aura glow system; the wall impact and scorch mark were not compared; which code turns our body during a cast is inferred, not run.
- Leads: additive sum on
stored instead of linear values
(M);
pdBattlePspand its aura script as the aura glow’s owner (M); slot field +0x3C set during a cast (L).
26. Character aura glow, flare, pickup cue (docs 11-14 auraglow)
- Decoded (FORMATS “Character aura
glow, the cast / aura-card flare …”):
- Owner
pdBattlePsp: four 0x120-byte records from object + 0xC0, set by the scriptauradefault.ssbthrough built-ins 0x2021–0x203B; record layout (H). - Script rules: colour by school, strength / size by min((level + 3) / 4, 5), none at level 0; 30-tick flares for event 10 (cast start) and event 8 (aura card used) (H).
- Event sites: cast start 0x140258603, fire routine 0x1402626d0 for skill id 0, remote copies 0x140190402 / 0x14019077e; the aura card has no cast state (profile 343, slot 0) (H, checked in the skill data).
- Level feed from the status record each tick, 0 under status slot 8 (H).
- Blur weights exp(c / size) normalised, table 0x14048f090 (H); 128 × 128 tile per player, silhouette of the character’s model, strength as the blend constant (M).
- Pickup cue 0x56 from the slot-fill routine; aura card use → level cue 0x59 (M).
- Jump: slot choice and rates re-read, no long-fall rule in the air tick 0x14025b0f0 (H); float state slots 43 / 44 under status slot 11 (M).
- Owner
- Not decoded: GFilter2 tap offsets and direction, silhouette shader and depth, the final composite, the Xbox build; what event 1 is (0x1402521a7); the alpha feed’s fades; why the game’s arms differ from the animation keys (answered in 27: the wrong file).
- Leads: joint rotation after the evaluator (consumer of the evaluator output, a second per-joint rotation) for the arm pose (L); 0x140287460 for the taps (M); search the other scripts for built-ins 0x2034 / 0x2039 before calling the pools dead (L).
27. Pose mixer and the character file (docs 11-14 armpose)
- Decoded (FORMATS “Pose mixer and the
character file the battle loads”):
- File pick 0x140250f70: model name + colour variant digit whenever the charaset variant count is not 0 (it never is); 130 slots expected by the player init 0x140256be8. The plain-named file the rebuild converted is not loaded; its skeleton and most of its animations differ (H, code + charaset + both files).
- Pose mixer at character + 0x940: four layers, play 0x140297d80, mix 0x140298020 (weights, slerp 0x14028ed60, bind fallback), matrix = parent · T · R · S (H).
- Joint record fields incl. flags, name id, hook kind; hook 0x14025dc20 with setup 0x14025d380: root pinned to the base x / z, neck and head look twists, nothing on any other joint (H for the dispatch, M for the twists).
- Arm pose numbers for the evade slots in both files; the Xbox strip matches the loaded file (H).
- Not decoded: the look
twists’ target and clamps; joint flag bits 0x2,
0x10, 0x20, 0x400 (not read by the mixer); the
six extra-motion files per character folder
(
.ala, 27–30 chunks each; charaset +0x40 holds six lengths, reader 0x1402527c8); what slot 129 is; who, if anything, loads a plain-named character file (second name builder at 0x140197510). - Leads: 0x14025dc40 / 0x14025dde0 (look twists, M); 0x1402527c8 (extra motions, L); PC footage of a standing evade to close the check on the PC side (L).
28. Debug character viewer: the skill bench (docs 11-14 bench)
- Decoded (FORMATS “Debug character viewer: the skill bench”): the viewer scene’s modes (character list, motion list, skill list, background colour editor; H), that skill mode calls the battle character’s own skill-use entry (H), the scene object’s bench fields on PC and Xbox (selection, pause, movement switch, camera distance / height / yaw / pitch and their reset values; H, written and read back on both running builds), the camera formula (H: presets land as computed on both), the stick steps and the second-pad pitch (M, read in both executables), the frame counter and motion slot in the character object (H PC; Xbox offsets found at run time).
- Not decoded: where the Xbox viewer sets its wider projection (measured only: 0.533 of the PC size), the scene’s static owner (the bench searches for the block), the character-list turntable step, why records 262 / 282 stay idle, the PC pad buttons for bits 0x40 / 0x200 (not needed: the bench writes the fields).
- Ours:
tools/bench/(camera tool, capture script, contact sheets). No rebuild code.
Ranked next decode runs (multiplayer)
0-sky. Sky backdrops (24, docs 11-15
skybright): decoded and built (skycol2
11-15: pdconv converts format 0x0B sky layers;
Godot draws svc /
svcal unlit by vertex colour with
culling and the material blend; black frame
clear; set 2’s point light from skycol). One
small decode left: the SVC fog
coordinate (c16) on the Xbox.
0-bench. Skill bench (28, docs 11-14
bench): no decode needed to use it. A
build run first (the rebuild’s viewer mode as
the third row), then per-skill comparison runs
take their answers from the bench instead of
footage. 0-char. Character file (27,
docs 11-14 armpose): no decode left for
the jump arms; a build run: convert the variant
files, re-derive joint indices and slot-length
timings, re-check every animation-derived
statement made on the plain file. Small decodes
after it: the neck / head look twists, the
extra-motion files. 0. Open questions
(docs 11-12, doc-answers): all settled from the
files, nothing left to decode; three
build tasks follow (multishot re-aim flight;
blast mask / order / 31 ticks; aura card after
an environment capture, aim points, lunge test
floor). Footage only to confirm the explosion
look’s size. 0-lock. Lock-on marker (4,
docs 11-15 lockring): decoded; a HUD
build run next (ring by grade, torso-root aim
point, closing-in + cue 4, ring swap, gauge /
number / name). Small decodes left: the marker’s
blend states, the needle’s turn direction (one
bench frame settles both). 0-ui. HUD /
menu placement and the arsenal screen (15, docs
11-14 uifix): decoded; build tasks
follow (one 853:480 screen frame for HUD, menus
and the 3-D view; re-convert skills for the aura
card; the arsenal editor’s card panel and grid).
Small decode leads left: name plate pieces, lock
reticle size, the detail panel’s labels. 0-sky.
Sky and light sets (24, docs 11-13
skyglow): a build run first (format
0x09 vertex colour, light set 2 for the sky
model and set 3 for model 1, sky centred on the
camera, boot-time storm clock), then a short
Xbox decode for the cloud pass’s fog state.
(skycol 11-15) Build next: set 2’s
point light 0 on the sky model (pdconv
points, PdData p0 for
set 2); it fixes st03’s purple sky and changes
13 more stages. 0a. Effects (22, docs
11-12 effects): joints, slots and
attach decoded; next decode runs: the stage
model draw (break effects; the debris manager is
done, docs 11-14 crater: a build run for
craters, debris and prop debris comes first),
then the element order against its joint and the
environment visual object. The larger part is a
build run (joint transforms for every element,
release slot on the caster, defense slots 4 /
5). 0b. Effect packs (23, docs 11-10
xboxfx): a build run first (convert
effects from the packs instead of the loose
files; draw mseftbb01s as point
sprites), then a decode run for the msparticle
draws on both platforms. 0c. Title
screen (15, docs 11-12 title): drawing
decoded; a build run next (title scene from the
tables, levels from the tick), then a short
decode run for the movie open path and the
shared dialog, and one footage comparison of the
intro. 0-move. Movement parity (9, docs
11-14 movepar): decoded to the tick; a
build run next (integer angles + sine table,
state 1 order, turn starts, air turn step, roll
along the facing, floor flag, contact order, 1 u
long-move back-off), with the replay test of
FORMATS “Movement parity” section 8 built first;
then one recording session (needs the playtester
for the capture) for the bench cases and the
tolerances. 0d. Skill records (5, docs
11-13 step3): every unplayed record has
a decoded path except the deck view (1) and the
levitates’ hold (2). Build runs next, by records
unlocked: the card eraser (19 + 6 close-range),
the refusal fix (5), level cost (6), the instant
sets (erase 9, special 7), status leftovers and
auto cards (8), hit effect 45 (3), fast rain
(3), hold (3), set 6 (2). Decode leftovers:
state 0x18, the levitate hold, reaction row +
6.
Lock-on and targeting (8): decoded in branch lockon (section 8); the vertical aim of casts is decoded (docs 11-10 vaim) and waits for a build run plus a footage check; other leftovers are ledger rows.- Match flow (2): done in branch matchflow (phases, end check, time-out, pit). The loading screen and the results screens are decoded (docs 11-10, hudtext); the heavy mode is game rule 4 (docs 11-10, rules). Left: the countdown / KO / time-up art.
In-match camera (10): decoded (docs 11-10: the full tick, presets, walls, yaw-follow, lock turn, spectator camera, shake application). Left: an implementation run, then the shake sources’ numbers and the look-at anchor point.- Status effects and the instant/environment sets (5, 6): decoded (docs 11-10): slots, status set, hit effects, environments (FORMATS “Status slots, hit effects and environments in full”); sets 1 and 3, the formulas, ricochet, the kinesis cast side and the remote mine (FORMATS “Skill casting leftovers”: 281 of 387 usable records fully written up, coverage table there). Left to decode: the stance and deck view action states (0x15 / 0x16 / 0x18), hit effect 18, card fields 0x5C..0x60, fast_rain, the auto-shelter pass list. The larger part left is implementation: power carried by the shot and compared by the block, the formulas, the skill-allowed check, the hit-effect table, environments with capture.
- 30 Hz fixed tick (1, done in branch gamespeed): step gameplay at the game’s rate (also simplifies netplay ticks). Mostly an implementation run; the constants are decoded.
Wall pass and body push (9): decoded (docs 11-10: collision response, body push, attribute table, masks, shot casts, ground attribute); left: implementation, the cast each skill kind uses, the turn step and roll steering.- Stage objects (11, 14):
breakables and pieces decoded (docs 11-10), the
pieces’ start pose (docs 11-13 piecepose; climb
re-check 11-13: the gravity / launch factor
record is decoded and is not the cause of the
Palace deck climb; the object pass, the 8-tick
delay and the exact launch jitter are decoded
(climb 3); the point numbering, the constraint
table, the cell order and the rest rule are
decoded (collapse 6, 11-14); next = put
those four into the build and re-measure, plus
side-on footage of section 1; deeper
joints); jump pads, throwables (object side),
support links, timed falling platforms, the net
events and a hazards-per-arena table decoded
(docs 11-10 stageobj2); link tests, the links
per stage, the crumble variant and the collapse
family decoded (docs 11-12 collapse). Left to
decode (the 0x400 attack body and landing damage
are done, docs 11-13 hurt; the crater placement
is done, docs 11-13 landmark, its debris manager
and mark models are done, docs 11-14 crater: a
build run): collapse animation export, falling
platform numbers. Mostly an implementation run
now, cheapest arena first (st07: jump pads
only). (docs 11-15 stagefx) The Highway
storm sphere, the pieces’ impact sound and the
object hit mark are decoded: a build run
(converter: second
vksandtexture, scroll rates,MD00pairs; Godot: sphere at the eye, piece thuds, mark on object hits). Small decode left: the shot callback’s kind words. Per-character data (13): decoded (docs 11-09); left is implementation (converter columns, turn step, body size, lying-pose rule).- Battle HUD from the game’s textures
and font (15): sprites done (hud run),
font atlas layout done (docs 11-09); font
widths, text drawing, status icons and the menu
script VM done (docs 11-10); now an
implementation run (
PdFont, icon row, result banners, results list). Left to decode: the status panel’s other-player rows and animations. Menus (docs 11-10 menus): engine, menu table, screen graph and the split-screen versus path decoded; next is an implementation run (script interpreter + menu engine running the user’svsmenu), then a decode run for the arsenal editor screen and the window frame. Audio leftovers (16): decoded (docs 11-10 audio): stage ambience, countdown, menu cues, footstep table, music payload spec, the unused XACT bank. Left is implementation (music converter step and player, stage emitters, countdown) and the small leads: battle cue sites → events, footstep trigger states. Ambient run 11-14: 3-D sends, listener, volume classes and the event length decoded; left is implementation (stage bank + emitters, the 3-D send routine, event length) and the leads: effect sends 11 / 12, the class fader’s users, the Doppler step.Arsenal builder rules (12): decoded (docs 11-10 rules run: copy limit 3, school capacity, rule flags, lobby check). Left: implementation; the capacity’s source. 11a.Versus options, teams, pad mapping (8, 18): decoded (docs 11-10 rules run). Left: the lobby’s team-side choice, respawn rules, the unread pad bits; then the 2v2 / 4-player implementation.Rumble (17): decoded (docs 11-10 audio); left: implement the cast sequencer; shake-source numbers come with the camera shake sources (10).- Original network model
(21): battle side decoded (docs 11-10: packet,
reliability, all 26 messages, remote playback,
clock stall, authority) and, docs 11-12
netcompat, the mesh layer, wrapper, header and
lobby messages, with Rebirth’s EOS mapping
described (
converter/NETCOMPAT.md). Docs 11-12 netcompat2: session control (join / reply / introduction / leave / keep-alive / ping), mesh searched to the end, lobby values, card trade, skill object net classes. Docs 11-14 netmsg: verified on two captures of a live Rebirth 1v1 (all datagrams parse; corrections and the event timeline in FORMATS “Versus network messages”, parserconverter/netmsg.py). Left for the compatible mode: the join / hello on the wire and a 3-4 player capture; then it is an implementation project (task list in NETCOMPAT.md). - CPU opponent (19): data
files, tick, input path and built-in table
decoded (docs 11-10 cpu); the shot-threat
built-in 0x40BA is read for every behaviour and
the sight pair’s point is identified (docs 11-12
doc-body, M). Left to decode:
the route follower / stuck recovery insides and
the CPU battle menu’s character and deck choice;
then an implementation run (script interpreter
for
eneprog006, built-ins, nav conversion). - Fire shot differences (25, docs 11-13 bofcmp): stage effect light, cast pose and the flash / burst elements decoded. The character aura glow is decoded (26, docs 11-14 auraglow) up to its filter taps and composite. Next decode runs, in order: the aura glow’s GFilter2 taps and composite (0x140287460, then a build run); the joint rotation after the animation evaluator (arm pose); the additive particle sum (render probe first); the skill card gate at a cast press; msparticle00.