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

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):

3. Multishot at close range

The flight routine 0x140266bf0, read in full (M: code only). It replaces “homing after the arc” in “Multishot (6)”:

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:

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