Open questions settled from the files
Eight behaviours the playtester could only have judged from footage, answered from the Store build 1.3.25854.2 executable and the effect / skill data instead (our reading of the machine code; addresses are virtual, base 0x140000000). Confidence per item; where it says M the code was read end to end and only the footage check is missing. Corrections to older sections are marked there with (doc-answers).
1. Explosion look: how large the game draws it
- The scale is real and reaches the meshes. The end routine (0x14026cd70, reasons 1..3) multiplies the three rotation rows of the shot’s matrix by 0x64 × 0.1 × 0.2 for a set-0 record with hit effect 5 (1.0 for every other record: the register is preset from the float at 0x1402f7da8) and hands that matrix to the effect spawn (0x14018d2f0 → 0x14018a040). The instance set-up (0x14018a174..) copies the matrix as given into the instance (+0x50 and +0x90); nothing normalises it, and the hit-slot meshes of these effects use matrix source 0 (the live matrix, “Effect drawing”). No later routine rewrites the blast’s effect matrix (the only matrix updates, 0x14018d440, are for flight effects). H for the formula and the path, M for “nothing shrinks it on the way to the screen” (the draw side was not re-read).
- The lobbed explosion effects are authored for exactly this scale. Their hit slot holds unit spheres (radius 0.5 u) whose scale keys grow them 10.9× over 29–30 frames, i.e. to 5.45 u; × 6 (0x64 = 300) that is 32.7 u, 1.09 × the 30 u blast radius, reached on the frame the blast sphere is full. So “scale = radius / 5” is the designers’ rule: a 5 u reference explosion. (Checked in the effect files of the three lobbed exploding records.)
- Around that core the effects carry much larger elements, and they are scaled too. With the decoded scale the largest hit-slot element of the lobbed effects reaches 2–5 × the blast radius (one grows 29× from 0.86 u: 150 u, a 15 m shock ring for a 3 m blast; the 0x64 = 400 record’s reach 54–144 u). The straight exploding shot’s effect (also used by the exploding ricochet through its cast profile) is authored at full size instead (domes of 15 → 30 u, ground rings to 38 u, columns to 45 u) and gets the same × 6: a dome 180 u in radius.
- Answer: yes. By the files
the game draws the ring / dome of a 3 m blast
15–20 m and more across; the hit sphere is only
the core. No per-model scale key or units step
exists beyond the element scale keys (“Effect
drawing”: scale = 1 + w ×
raw_m[0..2]) and the joint scale (1.0 on these meshes). M: one arsenal-preview frame of the exploding straight shot would make it H. - Slot duration (new,
H): 0x14018aee0 returns the
largest window end (
raw_f[3]) over the elements of every model of the slot; the slot’s model list is a run of s16 at slot entry + 4, ended by a negative value (so both models of a two-model slot play).
2. Explosion damage over the radius
The blast’s tick is 0x14026ae10 (the handler pair at 0x1403e23a8 that the blast start 0x14026dbd0 installs in the object, +0x1e0). Read in full, H in code (no footage):
- Radius this tick r = R ×
(30 − left) / 30 with
leftthe object’s timer (+0x18, set to 30 at the start); it is tested before the timer counts down, so the sphere is tested on 31 ticks, r = 0 on the first and r = R on the last, and the object ends after the tick that saw left = 0. (+0x190 = r, +0x194 = r × 0.2, +0x1a4 = the centre.) - Who is tested: the 32 entries of the character list (0x1404bcb50) in list order, not nearest first; an entry with a player object must have its bit in the blast’s hit mask, be alive and active.
- The test (0x14026c5b0): |character point (+0x60) − centre| < r + the character’s radius (+0xb0), then the stage line of sight from the centre (0x1401641b0), then the defense check (0x14026dcb0); a hit clears the character’s bit (0x14026ecc0) and runs the common hit routine 0x14026f870 with the blast object.
- No fall-off. Neither the test nor the hit routine reads the distance, r or R: the damage is the object’s carried value (+0x60), the same for a character at the centre and one at the edge. (The one thing that lowers it is the already documented excess rule: after a defense broke, later characters take the excess.)
- Hit mask at the start (0x14026dbd0), new: when the shot ended on a character (reasons 2 and 3) only that character’s bit is cleared and the rest of the shot’s mask stays, so the caster, whose bit the kind cleared at spawn, is spared. When it ended on stage geometry (reason 1; no character passed in) the mask gets all four player bits set: the blast can hit its own caster and anyone else in reach, whatever was cleared before.
3. Multishot at close range
The flight routine 0x140266bf0, read in full (M: code only). It replaces “homing after the arc” in “Multishot (6)”:
- While the arc counter (+0x1cc) is above 0, each tick: (1) the counter goes down and the frame turns about its up axis by the stored turn (+0x1c8, the −ω of the init); (2) with a target, the shot re-aims: d = distance from the shot (+0x140) to the target point, and when R² − d² / 4 > 0 (R = the arc radius +0x1d0) it builds the frame the init would build from here: looking at the target point, rolled by the record’s second angle (+0x1c4), turned by asin(d / 2R) on the side of the first angle (+0x1c0 > 0, else the other side). That frame’s forward axis is the tangent of the radius-R arc that ends at the target’s current position. The shot’s frame is then turned toward it by at most the homing rate (+0x1d8 = 0x80 × 0.1° × the cast’s percent) with the limited-turn helper 0x1401950c0 (rotation about the cross product, angle = min(rate, angle between)); (3) it moves by the speed (+0x1d4) along its forward axis.
- A deflected shot (bit 0x100 of +0x24) steers toward the opposite of that direction at 5° per tick (0x1402f7cd4) instead.
- When the target is farther than 2R from the shot, or there is no target, step (2) is skipped: the open arc.
- After the arc counter reaches 0 there is no steering at all: the shot flies straight for the remaining 30 ticks. There is no cone test anywhere in the routine.
- Answer: a curving shot does not miss a standing target at 7 m. The arc is solved to end at the target point for any distance (radius D / 2 sin b), the whole-tick truncation of the arc length is corrected by the per-tick re-aim, and the hit test is the usual 15 u sphere. A 2-D replay of the routine for four multishot records at 4–20 m passes within 0–5.3 u of the target every time. A moving target is tracked during the arc only, at the homing rate.
4. Melee lunge: where it ends
Re-read 0x14025c04d..0x14025c08d (H
in code): with d the horizontal
distance to the target, the lunge moves only
while d > 11 u, by speed, or,
when speed > d − 11, by speed − (d −
11) (two subtractions on the speed, the
result goes to the move 0x14024f9c0 as its
step). It is not a clamp to d − 11: the last
step overshoots the 11 u point, so the lunge
itself ends anywhere between 11 − speed and 11
u, and no further lunge move happens below 11 u.
The body push (“Body push between characters”:
no state test, a casting body is pushed like any
other, minimum centre distance 10 u for the
playable bodies) then holds the two bodies at
10 u or more. So the decoded
end distance is 1.0–1.1 m centre to
centre (bodies touching), not a visible
gap.
5. Straight shot at a higher or lower target
Nothing new was needed: “Vertical aim of a cast” has the rule (M), re-checked against the shot code. Locked: the shot leaves along the caster’s facing tilted by atan2(caster centre height − target point height, horizontal distance), no clamp and no lead, then steers in 3-D at the capped homing rate inside the 60° cone, so a target one floor up or down is hit as long as the stage does not block the line. Unlocked: the tilt is the camera’s aim pitch (camera pitch − the 9° rest pitch); a CPU without a lock fires level. The target point is the posed torso root node (“Body point, sight point and aim point”), 11–12 u over the feet when standing, and the shot starts at the fire node, so the first ticks’ homing takes up the muzzle offset.
6. Environment capture: what the button holds, and the owner
0x14017be00 (capture, from a skill-button press while the pickup kind is 3), H in code:
- All three branches run the slot-fill routine 0x140261a00 with card id 0, flag 0 and no pickup cue. Card id 0 is the aura card everywhere else (an aura capsule is a capsule whose skill id is 0; formula 15 counts “slots filled with skill id 0”). The slot-fill replaces what the button held (a placed mine of that button is removed, the card set by 0x140262670, cost and power refreshed). So after a capture the pressed button holds an aura card, exactly as after picking up an aura capsule; using it raises the level.
- The owner may capture its own environment. In the network modes (game mode 4 / 5) the routine first compares the environment’s owner with the local player index (0x1404bbe00): when they are the same it captures at once (capturable test 0x14017c5d0, slot fill, flash, cue 0x58, end = stamp = now, entry re-sent, draw countdown restart); otherwise it sends the capture request (message 10) to the owner. An explicit own-capture branch, not an oversight. Outside the network modes the same guard test and slot fill run for whoever pressed.
7. The CPU’s deck in versus
H (code and menu scripts
agree). Versus has no built-in CPU deck and
reads no com/deck file. The
one-on-one CPU battle (livedbtl,
menu 74) is entered only from the online
ranking screen
(liveranking): the player picks a
row of the ranking list, built-in
0x4293(row) (0x140214740 →
0x140183e80) takes that row’s record (64 rows ×
0x4C at 0x14051d4c0, with one text per row in
the table at 0x140594140), parses the text into
a 0x64-byte deck record (0x1400bf3d0) and stores
it at 0x1404bc8e0; the state word 0x140519abc (2
loading, 3 ready, 4 failed) is polled by 0x4294,
and on “ready” the script opens menu 74, whose
0x4295 starts the battle with that record as the
CPU’s deck. The list itself is requested from
the service by 0x4285 (0x140214400 →
0x140183ba0). So the CPU plays the
arsenal of the ranked player the user
chose: one deck per battle, a choice of
up to 64, all from the online service; the AI
script and parameter record are fixed
(eneprog006, record 20); the
characters are set by the start routine’s picker
(0x1401907a0, read as a random pick:
M). Offline there is no
source.
8. Wall slide and ledge approach
Not re-decoded: the movecoll build run implemented both from “Collision response” (wall push removes only the into-the-wall part of the move, the body stays one body radius off the face, steps under 0.75 m are walked over, a drop inside the floor test’s reach is walked down without the air state) and left only footage confirmation open, plus three details it marks itself (the long-move backoff value, the contact list order, the floor flag = ground flag).
Implementation notes for the rebuild
- Explosion look: keep the decoded scale (0x64 × 0.02 on the shot’s matrix) for every hit-effect-5 record and play both models of the slot; do not shrink the effect to the hit sphere. Length of the look = the slot’s largest window end.
- Blast: test on 31 ticks (r = 0 first, R last), characters in player order, full carried value at any distance. A blast started by a stage hit sets all four player bits (it can hit its caster and team-mates); one started on a character keeps the shot’s mask minus that character.
- Multishot: drop the homing after the arc and the cone; during the arc ticks re-aim each tick as above (turn −ω, then toward the re-solved tangent by at most the homing rate, then move); skip the re-aim without a target or when d > 2R; fly straight for the last 30 ticks. A deflected shot steers to the opposite direction at 5° per tick during the arc.
- Lunge: keep the step as built (speed − (d − 11)); with the decoded body push the end distance becomes 1.0–1.1 m; the melee autotest’s floor of 0.8 m must follow (1.0 m).
- Vertical aim: aim and steer at the torso root node, start at the fire node; nothing else.
- Environment capture: put an aura card (card id 0) into the pressed button, replacing its card; keep allowing the owner.
- CPU deck: there is nothing to pull from the
game for versus. Offer the choice ourselves (a
saved arsenal or a
com/deckfile) and keep it listed as our extension; AI script and parameter record stay the decoded fixed pair.