Player movement (executable + action table in gsdata_<lang>.dat)
Decoded from the executable’s per-tick
character code (addresses in the branch REPORT,
not here). Units as for skills: 1 tick = 1/30 s,
1 world unit = 0.1 m, speeds in km/h-like raw
values with raw / 10.8 = units per
tick (raw / 3.6 m/s).
godot/scripts/movement.gd
(PdMovement) holds every conversion below;
skilldata.py writes the data part
to movement.json.
Ground movement (engine
constants). Each tick the body moves
forward × speed along its facing,
which turns toward the stick by a per-character
turn step (decoded: “Character table” below; 20°
per tick for the playable cast).
- Two speeds, not scaled by stick length: walk 7.5 (2.08 m/s) and run 20 (5.56 m/s).
- Hysteresis on the stick length: walk → run above 0.7, run → walk below 0.4.
- Speed × (1 + p/100), p a status bonus percent (not modelled).
- Speed × max(0, 1 − |Δ| / 90°), Δ = the angle still left between facing and stick after this tick’s turn step (corrected movepar 11-14: it was read as the angle before the turn), so the body slows while it turns. Our body turns at once, so Δ = 0. Angles are 15-bit (0x8000 = 360°). Order, the one-tick lag of the move direction and the locked turn starts: “Movement parity” below.
Vertical (engine constants).
Each tick vy −= g,
vy = max(vy, −7.5),
y += vy. g = 0.12
units/tick² = 10.8 m/s² (the default
set at spawn and on landing; the jump routine
can take another), fall cap 7.5 units/tick =
22.5 m/s.
Jump routine.
(height H in m, gravity g, kind):
vy = sqrt(20 · g · H) units/tick,
which is sqrt(2 g h) with h = 10 H units. A
start animation plays first (its length − 2
ticks), then the rising phase lasts vy / g ticks
with the “up” animation stretched to fit. Skills
and stage jump pads use it. The controller’s
default vy is 4.0 units/tick, but that value is
always overwritten by the routine. Each call
passes its own height, gravity and kind, so an
evade jump always launches with the evade’s
values, whatever jump came before it (our port:
a skill’s jump is dropped on its landing and
when a hit’s reaction replaces its windup or air
state, and before every evade windup).
Action table. At file offset 0x2B00C, records of 0x72 bytes (s16 fields), indexed by an action id. Hit reactions, evades and skill moves pick records by id. Action records have 0x00 = 2. Fields used here:
| off | field |
|---|---|
| 0x06 | a sound id (0 = none; corrected step3 11-13: was read as a character / variant) |
| 0x4C | action type: 1 animated move, 5 hop, 9 height jump, others not decoded |
| 0x4E | type 5: launch speed (raw, as above) |
| 0x50 | type 5: launch angle above the ground, degrees |
| 0x52–0x5C | animation ids / tick counts; type 5 picks the anim at 0x54 when the stick is within 45° of facing, else 0x5C |
| 0x5A | type 9: jump height |
- Type 5 (hop): launch at
v = raw / 10.8units/tick,vy = v sin(angle)and horizontalv cos(angle)along the stick. There’s no steering in the air. - Type 1: plays the animation 0x52 for its length (the motion is the animation’s own, not decoded).
What the action table really
is. The slots its records play
(0x52..0x5C) are the hit-reaction animations in
Esper-RE’s slot list: record 2 the shot hits
(front/back/left/right), the type-5 records 3,
5, 7, 27, 28, 32 the “blown away” falls (front
slot when the angle passed in is within 45° of
the facing, else the back one), the type-1
records the drain / spike / raise hits. Rendered
on pc00a the type-5 slots are a body thrown
backwards, lying flat in the air. So record 3 is
a knockback launch, not the evade
jump: the hop that
movement.gd builds from it has the
knockback’s speed and angle.
Not decoded: walk/run start-up (no acceleration in the code found: speed is set directly each tick). The turn step: “Character table”. The evade: the section after it.