Skill kinds (what a skill object does, per behavior / skill set)
Decoded from the executable’s skill-object
code (our reading of the machine code; addresses
only in the branch report) and written by
skilldata.py as
skills.json kind (see
the end of this section). Units:
tick = 1/30 s,
u = game unit = 0.1 m, record
fields s16. “v / 10.8” is a speed in u per tick
(= raw / 3.6 m/s), as in “Straight
behavior”.
Dispatch
When the cast releases (see “Cast animation profiles”), the game creates one skill object and picks its code from two tables of {init, update} handlers:
- skill set 0x52 = 0: by the behavior 0x7A (0..20). Behaviors 3 and 14 share one handler, 15 and 16 share one, 18 and 19 do nothing;
- skill set ≠ 0: by the set (1 erase, 2 defense, 3 special, 4 status, 5 environment; 6 has none). Every set ≠ 0 record has 0x7A = 0, so “behavior 0” in the raw counts includes all of them.
| id | kind (kind.name) |
usable records (this build) | type |
|---|---|---|---|
| 0 | straight | 95 (set 0) | attack, erase, special, status |
| 13 | melee | 29 | attack, special, erase |
| 4 | auto | 20 | erase, special, status |
| 12 | blade | 19 | attack, status, erase, special |
| 1 | parabola | 13 | attack, erase |
| 8 | mine | 13 | status, attack, erase, special |
| 6 | multishot (curving shots) | 11 | attack |
| 5 | crawl (floor-hugging homing shot) | 10 | attack, status |
| 20 | rain | 9 | attack |
| 16 | hole_all | 7 | attack, erase |
| 2 | fall | 6 | attack |
| 17 | ricochet | 5 | attack |
| 9 | burst (mine_burst) | 5 | attack, status |
| 15 | hole | 3 | attack, status |
| 7 | fast_rain | 3 | attack |
| 10 | moving | 3 | attack |
| 14 | pursuit | 2 | attack |
| 11 | kinesis | 2 | attack |
| set 2 | defense | 47 | defense |
| set 4 | status | 34 | status, special, erase |
| set 5 | environment | 30 | environment |
| set 1 | erase | 9 | erase |
| set 3 | special | 9 | special, status |
| set 6 | (no handler) | 2 | attack |
Rules shared by all kinds
- Lifetime counter. Each tick after the kind’s update, a non-zero counter is decremented; at 0 the object ends (“Straight behavior” has the L + 1 detail).
- Who can be hit. In versus every object can hit any character (the caster too, unless its own bit is cleared; the kinds below clear it) and collides with the stage along its path. Each object hits a given character once: the hit clears that character’s bit in the object. For rain (20) the bit is cleared in every drop of the same volley, so one rain volley hits a character once.
- Projectile hit (straight, parabola, fall, multishot, crawl, ricochet, kinesis, rain drops): the segment from last tick’s position to this tick’s is tested against a sphere at the character’s centre with radius = object radius + character radius. Object radius is 5 u unless the kind sets another; the character radius is 10 u (the value the actor setup writes; per-character values not checked). Then a line-of-sight test from the last position to the character: a wall in between cancels the hit, unless collision 0x6A is 2 or 3. After a hit the object ends, unless the kind passes through (fast_rain, moving, hole, and explosions).
- Before any hit the target’s active defense is checked (below). Auto (4) has no check.
- Explode on hit. A set-0 record with hit effect 0x62 = 5 turns into an explosion of radius 0x64 × 0.1 u when it hits or is blocked (the character it hit directly is not hit again), and when it meets stage geometry (end reason 1; a ricochet bounces instead and never ends there). Not at the lifetime end (reason 0 skips the switch; shotvar r2). The look is the end routine’s slot 2 of the shot’s effect, scaled to 2 × the blast radius (“Shot end”). Mines and bursts explode the same way.
- Explosion: a sphere at the object’s last position whose radius grows linearly from 0 to R (r = R·(30 − left)/30, tested before the timer counts down: 31 tests, r = 0 first, R last), then ends. It hits every character once (centre distance < r + character radius, line of sight from the centre, defense checked first), breaks stage props unless 0x6A = 3, and passes through. (doc-answers: the tick 0x14026ae10 followed: characters in list order, full carried value at any distance, no fall-off; a blast started on stage geometry sets all four player bits, the caster’s too. “Open questions settled” 2.) The blast is the attack object itself, so a defense it breaks through writes the excess into that object’s carried value (+0x60), and every character it reaches later takes the excess, not the full value: the block routine 0x140271760 is called with the attack object from both defense checks (0x14026e2b3, 0x14026f6ac) and nothing restores +0x60, and the hit code after the defense check (0x14026fa98 on) reads the damage from that same field. As the sphere grows from 0, nearer characters are reached first (within one tick: list order). (Read 11-10, power run round 2; the per-tick loop followed through in doc-answers: H in code.)
- Strength (used against defenses) is the card power, i.e. the attack’s damage: set 0 → the damage formula 0x56 + the strength status + 0x5A × uses so far; formula 0 (every damaging record) is the plain 0x58, 0x56 = 31 (erase / status / special records without damage) gives 0, the others are in “Card power and the damage formulas”. Set 2 → durability 0x5A + 0x5C × uses so far, at least 0. (Corrected docs 11-10: this said that 31 is the plain formula of most attacks and gives strength 0.)
Melee (13), blade (12) and pursuit (3, 14)
(melee run 11-11; built in
godot/scripts/combat/melee_attack.gd,
melee_lunge.gd. Confidence
H unless marked.)
The lunge (cast state 12). Every skill of set 0 with behaviour 3, 12, 13 or 14 starts the cast in the lunge state (the local cast set-up 0x14025a77d..0x14025a854; the remote-cast copy at 0x140190430). It is set up once, at the cast start, from the ground cast profile and the record:
- Wait = profile 0x52 (the lunge start frame); lunge frames n = profile 0x54 − 0x52.
- Speed (0x14018f050), only with a target and n > 0: for 0x7E ≥ 0, 10 × 0x7E / n u/tick (0x7E metres spread over the lunge frames); for 0x7E < 0, 0x7E / 10.8 u/tick; then capped at 10 u/tick (.rdata 0x1402f7f7c). Without a target the speed is 0 and the has-target flag 0.
- Turn rate (0x14018f0f0) = int(0x80 / 10 × 32768 / 360) angle units per tick: 0x80 is in tenths of a degree per tick.
- Tracking flag = 0x82 ≠ 0 with a target (0x14018f170); read only by the check 0x140250180, not by the tick.
- So 0x7C is the hit object’s size,
0x7E the lunge distance, 0x80 the lunge
turn rate, 0x82 the tracking flag
(skills.json kind
lunge_distance,lunge_turn_deg_per_tick,lunge_track).
Per tick (0x14025be40): while the wait runs, the caster turns toward its target (without one: the cast yaw) by the character’s own turn step (charaset, 20°/tick for the playable cast); the wait counts down when the animation’s frame step passes (once per tick at our speed, M). Then for the n lunge ticks: with a target, it turns toward it by at most the turn rate and, while the horizontal distance d to it is over 11 u (.rdata 0x1402f7f90), moves along its facing (0x14024f9c0; skipped while 0x14024d4d0(C + 0x40, 4) is set) by the speed, or by speed − (d − 11) once the speed would pass the stop point (as read, 0x14025c063..0x14025c084: not the clamp to d − 11 one would expect; re-read and confirmed (doc-answers), H in code: the lunge ends at 11 − speed..11 u and the body push then holds 10 u, “Open questions settled” 4). Without a target it only turns toward the cast yaw. A lunge kind gets a target only within the lock’s near range (8 m, “Lock-on”).
The attack point. The cast’s
effect instance (spawned at the cast start from
the profile’s 0x04 effect, or record 0x20
without a profile; handle at C + 0x13b20, effect
number at C + 0x13b24) follows the caster’s root
matrix. 0x14018a310 gives the attack matrices:
for each model of the effect’s current slot, the
skeleton joints whose name tag (joint record +
0x2C) masked with 0xFFFFFF00 is 0xB3D8C500 (a
fixed prefix plus a two-digit number NN) give
attack point NN − 1 = effect root × the joint’s
translation, rotation and scale. With none, it
falls back to the caster’s joint tagged
0xADB07630 (0x14018aa50), the right hand (joint
38 of the playable models,
PdCharacter.HAND_BONE). Skeleton
joint records are 0x40 bytes: nine floats
(position, rotation, scale), u16 flags at 0x24,
parent s16 at 0x2A, name tag u32 at 0x2C.
None of the effects the melee, blade and
pursuit records use has attack joints
(only 13 effect files in the data do), so for
these cards the point is always the right
hand.
Melee (13) (init 0x14026a020, tick 0x14026a0d0): lifetime L = the ground profile’s 0x58 − 0x56 (active end − release); the object ends at once without a profile or while the caster’s status +0x10 is set. Radius 0x7C × 0.1 u; the caster’s own hit bit is cleared. Every tick: the attack point (above); every character is tested (0x14026c340); the stage props once (flag 0x400) at chest + facing × 20 u (0x1401633b0); then the counter: nonzero → decrement, zero → end. So the object hits on L + 1 ticks.
Pursuit (3, 14) (init 0x140265d60, tick 0x140265e00): a sphere of 0x7C × 0.1 u on the caster’s chest, no lifetime; one tick: if the caster has a locked target, that target alone is tested (0x14026c340), then the object ends. The “chase” is the lunge above.
The hit test (0x14026c340, melee and pursuit). The target’s hit bit must be set and the target alive; distance from the object’s point to the target’s point (record + 0x60) < object radius + target radius (+0xb0: the character table radius, 5 u for the playable cast; corrected 11-12, was “10 u”); line of sight from the caster’s chest (position + centre height, +0x1a4) to the target point (0x1401641b0); then, if the target has a live defense (0x14026ee80), the defense check (0x14026dcb0) along the path from the target’s point to chest + 10 u × normalize(chest − target point), i.e. a point 10 u behind the attacker. Not blocked: the guard test 0x14026ecc0, then the hit 0x14026f870 (damage, reaction, hit effect, as a shot’s).
Blade (12) (init 0x140269c60, tick 0x140269db0): lifetime as melee; blade length 0x7C × 0.1 u. Each tick the blade runs from the attack point along the point matrix’s Z row for that length; the quad swept between last tick’s blade and this tick’s (two triangles) is tested against a 12 u sphere at each character’s point (.rdata 0x1402f7f9c; fixed, not the character radius) in 0x14026c730, then line of sight from the chest and the defense check with the same path as melee, then the same hit calls. Stage props along the segment, once.
Defense check for these kinds (0x14026dcb0). The attack’s radius (+0x190: the sphere’s, the blade’s length) pads the shapes. Types 0, 3, 4 (planes, 0x14026de21): the path is tested against the two planes the radius in front of and behind the barrier plane (the endpoints’ sign products ≤ 0, i.e. from either side), and the crossing point must lie within defense radius
- attack radius of the barrier centre. Types 1, 2, 5, 6 (spheres, 0x14026e18f): segment-point distance (0x140193bc0) < defense radius + attack radius. Then the block routine (0x140271760), as for shots.
Repelled end. A held or
stopping break by a type-3
defense ends the attack with end reason 7
(0x14026cd70, jump table at 0x14026d79c, case
0x14026d368): for behaviours 3, 12 and 13 (not
14), with the caster alive (status +0x34 ≠ 0)
and its status +0x10 clear, the caster starts
action 26 (0x140258690) at its
current facing. Action 26 is a type-3
(front/back) action, animations [121, 122]
(rules.json repel_action). Other
kinds turn around at reason 7.
Ground and air. The lunge
state is chosen before the air state for these
kinds. The gravity during the lunge was not
followed. No close-range record has an
air profile: the record’s 0x16 is 0 for
all 50 (melee 29, blade 19, pursuit 2;
anim.profiles.air = null in
skills.json, checked 11-12), so by “Choosing the
profile” an air cast plays the ground profile:
its slot, release tick, active end and
its lunge frames. The lunge in
the air therefore uses the same frames as on the
ground (MeleeLunge.from_record
reads profiles.ground).
Auto (4): no projectile
- Waits 0x7E ticks, then applies its effect directly: 0x7C = 2 → to every living character, otherwise only to the locked target. With 0x7C = 0 it needs a valid target at cast time or it fizzles. No hit test, no defense check.
- (autocrawl 11-12, init 0x140265ea0, update 0x140265f50) The init sets the counter to 0x7E; with 0x7C = 0 it also requires the target and the range test 0x140273c80, else the object ends at once. Each update counts down; at 0 it runs the hit routine 0x14026f870 once on each of the four player slots that is present, simulated on this machine and alive (0x7C = 2; there is no own-side test, so the caster is hit too) or on the target, stops its effect and ends.
- In the hit routine, kind 4 skips the auto-shelter (0x14026f530) and jumps past the hit-state checks: health minus the card power (object +0x60), the combo sum and its 90-tick window, the card-field routine 0x140272510 (0x5C), the hit effect 0x140272bc0, slots 8, 12 and 11 cleared, then the reaction (every auto record’s tier action ids are 0: nothing starts).
- The object has no effect slot of its own: the spawn 0x140263a00 gives it slot 1 of its effect file at its start point, held until it ends.
Parabola (1)
- Horizontal speed v = 0x7C / 10.8 u/tick (0x7E when 0x7C = 0). Spawns at the cast point and aims at the target’s position: horizontal distance d → flight time T = d / v ticks.
- Arc height H = 0x80 × 10 u (= 0x80 m above the line to the target): gravity g = 8H / T² per tick², initial vertical speed g·T/2 − (height difference)/T, so it lands on the target point at T. Lifetime T + 30 ticks (it keeps falling past the landing point).
- Tracking: each tick the landing point moves toward the target’s current position by at most 0x82 / 10.8 u × p (homing percent, see “Straight behavior”). A deflected shot (flag set by a type-2 defense, below) moves its landing point away instead, at 60 / 10.8 u/tick.
- Hits like a projectile (radius 5 u).
- In detail (lobbed 11-12; init
0x140264b00, update 0x140265080, played in the
rebuild):
- Landing point (0x14026e410 with flag 0): with a target, the target record’s point, then the range clamp (below); a clamped point drops the target (the shot no longer tracks). Without a target: 300 u along the launch heading when the range class 0x54 is 1, else 190 u (.rdata 0x1402f8138 / 0x1402f80cc), at the start height.
- The heading is the yaw of the shot’s own launch frame (not turned toward the point); d is the horizontal distance to the point, T = d / v kept as a float; the stored lifetime counter is int(T) + 30. The init clears the caster’s hit bit (its own shot cannot hit it).
- Each tick: with a target, a tracking shift D is worked out (0x14026bf50): the apex height is the base height + v_y² / 2g; when the target point is above the apex, or above the base while the shot already falls, the last D is kept; otherwise the time t until the shot comes down to the target point’s height (v_y / g + √(2(apex − y) / g)) gives the predicted horizontal landing spot base + heading · v · t, and D is the horizontal gap from it to the target point. D is capped to the tracking speed (a deflected shot: D turned to point away at 60 / 10.8 u, or (60 / 10.8, 0, 0) when D is zero), stored, and added to the base point. Then the position becomes base + heading · v + (0, v_y, 0), v_y drops by g and the new position is the next base. Then the common hit routine.
- Reflected (object state 5): v_y turns over, the heading points at the new target point, the time from the shift routine sets the new horizontal speed (distance / t) and lifetime t + 30; with no target the lifetime also gains 2 · int(v_y / g).
- Range clamp (0x140273d40): set 0 with range class 2, or behaviour 16, is never clamped. Range class 0 keeps the point between 80 and 300 u (3-D distance) from the object, every other class (and every other set) between 300 and 600 u; a point moved onto the band edge counts as clamped.
Fall (2)
- Spawns 0x7C × 10 u above and 0x7E × 10 u back from the landing point (not the caster), along the horizontal line from the object to that point, flies at 0x80 / 10.8 u/tick toward it, tracking the target by at most 0x82 / 10.8 u/tick × p per tick (deflected: away, as parabola). Lifetime int(2 × line length / speed).
- In detail (lobbed 11-12; init 0x140265470, update 0x1402657f0, played): the landing point is the parabola’s (target point + range clamp, or 190 / 300 u ahead). Each tick, with a target, the target point is taken into the shot’s own frame: while it is still ahead, its sideways and vertical offset from the line is the shift (capped to the tracking speed; deflected as parabola); once it is behind, the last shift is reused. The shift moves the shot, then it steps along its line. The init does not clear the caster’s hit bit: a fall can hit its own caster.
Multishot (6): curving shots
- The cast spawns several objects; shot i (its
index in the volley, modulo
0x86 when 0x86 > 1, else 0)
leaves at (0x82 + 0x88·i)° off
the straight line to the target, with that bend
turned (0x84 + 0x8A·i)° around
the line, and flies a circular
arc that ends at the target point:
chord D, arc radius D / (2·sin b) with b the
first angle, speed 0x7E / 10.8
u/tick, so the arc takes 2·b / ω ticks
(ω = speed / radius); lifetime that
- Homing 0x80 × 0.1° per tick × p is the per-tick re-aim during the arc (the shot turns toward the re-solved arc tangent by at most that rate); after the arc it flies straight, no steering and no cone (corrected, doc-answers: flight routine 0x140266bf0 in “Open questions settled” 3). 0x7C (range, as straight) is read elsewhere (not followed).
- Init in detail (shotvar 11-11, 0x1402666b0, M): the aim point is the locked body record’s point; with no target, 200 u along the launch frame’s forward axis (the float at 0x1402f80dc); a third case (object +0x10 ≠ 5) takes the landing-point routine 0x14026e410 (not followed). The frame is built looking from the start point at the aim point, then rolled about its forward axis by the second angle (0x84 + 0x8A·i; routine 0x140290180: positive turns the frame’s right axis toward its up axis) and then turned about its own up axis by the first (0x82 + 0x88·i; 0x140290050: positive turns forward toward the right). Both in whole degrees (× π/180). Radius = D / (2 sin b) (+0x1d0), turn per tick = speed / radius (+0x1c8, stored negated so the shot curves back), arc ticks = 2 × trunc(|b / turn|) (+0x1cc), lifetime that + 30; homing +0x1d8 = 0x80 × 0.1 × π/180 × the cast’s homing percent. The owner’s hit bit is cleared.
Crawl: floor-hugging homing shot
- Lifetime and speed exactly like straight (0x7C life/range, 0x7E start, 0x80 cruise, 0x82 ramp). It follows the floor (a ground probe each tick) and falls with 0.12 u/tick² when over a drop. Turn toward the target 0x84 × 0.01° per tick × p; 0x86 × 0.1° caps how far the heading may be off (partly decoded).
- (autocrawl 11-12, init 0x140266060, update 0x140266290) The frame is the cast frame with its forward axis laid flat and world up (the cast pitch is not used). Each tick the position moves by speed × the flat forward plus the fall speed upward, then the floor probe 0x140163cb0 pushes a sphere of the object radius (+0x190) out of stage faces whose normal y is above 0.643 (0x1402f7d50), skipping face attributes 16, 18, 20 and 31. Touching a floor: the fall speed is 0 and, with a target, the heading turns; not touching: the fall speed drops by 0.12 u per tick (0x1402f7ce4) and there is no turn.
- The turn keeps a rate w between ticks. Step a = 0x84 × 0.01 (0x1402f7c74) degrees × the homing percent (+0x64), cap = 0x86 × 0.1 degrees. With diff = the wrapped flat angle from the heading to the target point: if |diff| < a, w = diff; else w moves by a toward diff’s sign and is clamped to ±cap. The heading turns by w. A deflected shot aims away and uses a = 5 degrees (0x1402f7cd4). The hit test is the shared projectile one (post-update 0x14026e720).
Mine (8)
- Placed at the floor point a probe from 10 u above to 10 u below the spawn point finds (none: the spawn point). Counter = 0x80 ticks, counted down while above 0.
- When the counter runs out: 0x7C = 0 → the mine explodes (end reason 8; it does not just end); 0x7C = 1 → armed for good (no further lifetime): every tick, each living character still in its hit mask whose record point is within 0x7E × 0.1 u of the mine (no character-radius pad) with line of sight sets it off (end reason 8). 0x7C = 2: the remote mine, see “Mine mode 2”. The explosion: radius 0x82 × 0.1 u (0x1402637f0), started with no body spared, so a mine hits its own caster; its look is the effect’s slot 2 scaled by radius × 0.2 (lobbed 11-12; init 0x140267b90, update 0x140267e90, end 0x14026cd70).
- A new card filling the slot ends the first live mine of that slot silently (0x14026ef10, end reason 0), any mode; a spent card leaving the slot does not.
Burst (9, mine_burst)
- An explosion around the cast point at once: radius 0x7C × 0.1 u, growing over 30 ticks like every explosion (r = R × (30 − ticks left) / 30). The caster is passed as the body already hit, so a burst spares its caster. Look: slot 2 with an unrotated frame scaled by radius × 0.2 (lobbed 11-12; init 0x140268050, update 0x140268320).
Hole (15) and hole_all (16)
- One object on the floor at the target (hole_all: one per opponent, spawned together).
- Lifetime 0x7C + 0x7E ticks: first 0x7C ticks a warning phase (the spot follows the floor; not fully followed), then 0x7E ticks active: a sphere of radius 0x80 × 0.1 u that hits only characters standing on the ground (a character flag; airborne ones are skipped). Passes through (can hit several).
- (autocrawl 11-12, init 0x14026a510, update 0x14026a7f0) Placement (0x14026e410 with mode 1): with a target, a ray from the target point straight down to y = 0 gives the floor point (none: the target point itself, and the target is dropped). The range clamp 0x140273d40 passes hole_all and range class 2; class 0 keeps the point 80..300 u from the start point (+0x68), moving it onto the limit along the same line and dropping the target; class 1 keeps it 300..600 u (0x1402f8138 / 0x1402f81e0, squared 0x1402f8288 / 0x1402f8290). The distance is 3-D from the start point (about 12 u up at the cast node), so a near target on a flat floor gets a point moved under the floor, the pick below finds nothing and the object ends at once (autocrawl r2). Without a target the point is 190 u ahead of the start point along the heading (class 1: 300 u). The point is lifted 1 u and picked down onto the floor (0x140163680); found: floor + 1 u, else the object ends.
- Drift: target +0x60 minus target +0xa0 (read as the target’s last move); its flat length and angle are kept at +0x1c0 / +0x1c4 and sent in the placement message 0x14026d7d0.
- Warning (counter ≥ 0x7E): the radius grows as R × (0x7C − (counter − 0x7E)) / 0x7C with R = 0x80 × 0.1 u; the spot moves by the drift each tick and is re-picked on the floor within ±(7.5 u + drift length); no floor: the drift becomes 0.
- Active: every body whose hit bit is still set, not a non-player, alive, local and standing on the ground goes through 0x14026c5b0: distance from the spot below R + 10 u, a sight line, the defense check 0x14026dcb0, the guard 0x14026ecc0, then the hit 0x14026f870 (the bit is then cleared). The caster’s bit is not cleared at the start, so the caster can be hit. Flags 0x20 (passes through) and 0x10 (networked). The effect is scaled XZ by the current radius × 0.2 × 0.5, Y by 0.5. The object ends when the counter reaches 0.
Rain (20)
- An emitter 0x86 × 0.1 u above the landing point lives 0x7C + 0x7E ticks. Its first 0x7C ticks drop nothing; after that it drops 0x80 drops, one every 0x82 + 1 ticks (the interval counter is reset to 0x82 and fires when it drops below 0), while the lifetime lasts. Drops are projectiles of radius 5 u flying at 0x8C / 10.8 u/tick; they share the volley’s hit mask, so one volley hits a character once.
- In detail (lobbed 11-12; init
0x14026b480, update 0x14026bbd0, drop
0x14026b8d0, played):
- Landing point (0x14026e410 with flag 1): with a target, a ray from the target point straight down to height 0 gives the floor point (no floor: the target is dropped), then the range clamp; without a target 190 / 300 u ahead as parabola.
- With a target the emitter follows the point 0x86 × 0.1 u above the target point by at most 0x8A / 10.8 u per tick (3-D), snapping onto it when nearer.
- Each drop: an identity frame turned by a random yaw over the whole turn (below(0x8001) engine units) and pitched down by 0x1c71 + below(0x71c) units (80..100°); it starts below(1000) / 1000 × 0x88 × 0.1 u from the emitter along that frame’s up axis and flies along its forward axis. Lifetime int((0x86 × 0.1 + 30) / speed). Three draws of the shared generator per drop. The effect’s slot 4 is played at each drop’s start, slot 5 is kept on the emitter.
- Neither emitter nor drops clear the caster’s hit bit: rain can hit its caster.
- Fast rain (7) is not played: its per-tick motion is not decoded.
Rare kinds (parameters located, behaviour partly followed)
- Fast rain (7): lifetime 0x7C + 0x7E; drop radius 0x84 × 0.1 u; positions from 0x80 × 10 and 0x82; passes through.
- Moving: lifetime
0x7C ticks, radius 0x7E
× 0.1 u, speed 0x82 /
10.8, kept 0x80 × 10 − 2
u above the floor; passes through.
(autocrawl 11-12, init 0x140268590, update
0x140268940) Frame at the start point
(+0x68) with the heading (+0xc0), level; a floor
probe 0x140164330 within ±20 u (none: ends).
Speed ramps from 0x82 / 10.8 to 0x84 / 10.8 over
0x86 ticks. The column height is 0x80 × 10 − 2
u, or the gap to a ceiling (a ray up from floor
+ 1 u) minus 1. Each tick: move along the
heading, re-probe the floor within ±7.5 u (none:
ends), a ceiling within the height puts x/z
back, else y = floor + 1 u. Hit test
0x14026c1c0: the segment base → top against a
sphere of R
- 10 u around each character’s point; defense check first, a sight line from the top unless collision 0x6A is 2 or 3, the guard, the hit. The caster is skipped only during a 30-tick grace. The effect sits at the column’s middle, scaled XZ by R × 0.1 and Y by height × 0.1.
- Kinesis (11): lifetime/speed like straight (0x7C..0x82); 0x86 and 0x8A × 0.1° shape it; it has a third handler (not followed).
- Ricochet (17): lifetime/speed like straight; shot i (mod 0x88) gets angles 0x84/0x86 + 0x8A/0x8C × i like multishot (0x86 / 0x8C roll the frame, 0x84 / 0x8A then turn it); 0x8E is the bounce count (see “Ricochet (17)” in “Skill casting leftovers”).
Defense (set 2)
Record fields: 0x54 type (0..7), 0x56 radius × 0.1 u, 0x58 lifetime + 2 ticks (lifetime = 0x58 − 2), 0x5A durability (+ 0x5C per use), 0x5E = 1 anti-pierce, 0x60 = 1 add-on for melee-type attacks only, 0x62 add-on with value 0x64 (below). 0x66 not followed.
- Placement (every tick): types 0, 3, 4, 5 sit in front of the caster, at the caster’s own radius + 5 u along its facing; types 1, 2, 6, 7 are centred on the caster.
- Shape of the check: types 0, 3, 4 are a plane facing outward at the barrier: an attack is caught when its path from last tick to this tick crosses the plane within the radius of the barrier centre. Types 1, 2, 5, 6 are a sphere of that radius around the barrier, tested against the path. Melee/blade/pursuit are tested along their own path, two-sided and padded (“Melee (13), blade (12) and pursuit (3, 14)”).
- A character’s active defense is any of its live set-2 objects except type 7.
- Shield piercing 0x68 = 2 on a set-0 attack (not while the attacker has a certain state flag) passes types 0, 1, 3, 4, 5. A value of 3 would pass types 2 and 6.
- Per type, before the block (attack kinds
that pass):
- 0 (front plane): fast_rain, moving, rain;
- 4 (front plane): as type 0; straight and multishot shots are reflected (below);
- 3 (front plane): explosions, fast_rain, moving, mine, burst, rain; a blocked melee-type attack ends with the “repelled” end (the attacker’s action 26; “Melee (13), blade (12) and pursuit (3, 14)”);
- 5 (front sphere): explosions, melee/blade/pursuit, fast_rain, moving, mine, burst, rain;
- 1 (centred sphere): nothing passes except piercing;
- 2 (centred sphere): never blocks: it marks shots inside it as deflected (straight shots then turn away from their target at 5°/tick, parabola/fall landing points move away); the check runs every tick for shots aimed at the holder;
- 6 (centred sphere): reflects straight, parabola, fall, crawl, multishot and kinesis shots (with a 20-tick count set on the shot, not followed); everything else passes; explosions pass;
- 7: auto-shelter. Cast by hand it is a one-tick object that never blocks. Its real use is from a capsule slot. In the guard test that runs before every hit, the defender’s four slots are searched for a set-2 type-7 card in a usable state. It does not trigger for an auto (4) attack, or for a piercing one (0x68 = 2) unless the attacker’s status slot 31 is set. The card is then cast with no animation (the regular cast routine), and the new object is block-checked against that attack at once. If it stops the attack, the hit is cancelled. Our build treats that object as a centred shelter (type 1 rules); the exact pass list for this path was not separated.
- Block: the defense’s durability minus the attack’s strength (0x140271bbe subtracts the attack’s carried value +0x60 from the defense’s). ≥ 0 (equal included): held: the attack ends (“blocked”, it still explodes if it has hit effect 5) and the defense ends too — one defense stops one attack (its end code 9). The block also clears the defender’s bit in the attack object’s per-character hit mask (+0x24, bits 0..3 = character index; every hit test checks that bit first), so the explosion of a blocked attack never hits the defender, at any distance; other characters in its radius are hit as usual. < 0: broken: the defense ends with end code 10, the add-on runs as after a hold, and then the attack goes on only when it breaks through: the attacker’s status slot 20 is set, or the attack’s 0x68 is 1 (read through 0x1402723b0, which gives 0 while the attacker’s status slot 31 is set and −1 for records outside set 0), and the defense is not anti-pierce (0x5E ≠ 1). It then carries the excess (strength − durability) as its new carried value, i.e. as its strength and its damage. In every other case the broken defense still stops the attack exactly like a hold (hit mask bit cleared, end code 3, or 7 for the type-3 melee case). (Break path read 11-10, power run, 0x140271d39..0x140271eb2; H for the control flow. The docs before said every broken defense lets the attack on with the excess.) The strength is the attack’s damage, so a defense holds an attack whose damage is at most its durability (durabilities are 0..8, attack damages 1..10 in the data); only the no-damage records (formula 31) are always held. 0x68 values in the data: 0 (242 set-0 records), 1 (7), 2 (5, piercing), 20 (1; neither 1 nor 2, so it acts as 0 here). (Corrected docs 11-10: this said plain attacks have strength 0.)
- Add-on (0x62, applied by the defender after a hold and after a break (0x140271ed0 is called on both paths, with the attack’s carried value before any excess is written); with 0x60 = 1 only when the attack is melee-type, i.e. set 0 with behaviour 3, 12, 13 or 14; never for behaviour 18): 1 health + the attack’s carried value (skill object + 0x60, read as its damage); 2 aura + that same value; 3 erase the attacker’s card (the slot’s card routine); 4 the attacker’s status slot 4 (bound) set to 1 for 0x64 ticks; 5 slot 5 (skill buttons locked) for 0x64 ticks; 7 capture: the card goes into the defender’s slot. 6 is unused in the data. When 0x5E is set, piercing does not pass, and a breaking-through attack that breaks the defense still stops (break path above; no longer inferred).
- Reflect: the shot turns around (re-aimed back along its path), its owner becomes the defender and its target the old owner, it may hit anyone except the new owner, and its kind’s init runs again (fresh lifetime and speed).
Instant sets (1 erase, 3 special, 4 status)
The object applies its effect once at spawn and ends. Set 1 calls the erase routine, set 3 dispatches on 0x54 (with 0x56..0x5A as values); both are decoded in “Skill casting leftovers” (set 1 acts on field capsules, set 3 is jumps, teleports, levitate and the evades).
Status set (4). 0x54 = who: 0 the caster, 1 its locked target (no target: nothing), 2 every living character. Each of them gets up to four effects i = 0..3: id 0x56 + 2i (0 = none), value 0x5E + 2i, ticks 0x66 + 2i, through one 23-way switch on the id:
| id | effect |
|---|---|
| 1 | aura level + value (the level routine; bounded as in “Combat rules”) |
| 2 | aura + value |
| 3 | health + value (the health-change routine) |
| 4, 5, 6, 7 | add to status slot 0, 1, 2, 3 (strength, speed %, homing %, regen %), timed by ticks |
| 8 | when any slot is set: the status reset routine |
| 9 | aura + (value − 1) × current aura (when aura > 0) |
| 10 | aura level + the current level (doubles it) |
| 11, 15 | start a stance action (a character action with the record’s animation; 15 with action 0x16) |
| 12 | slot 8 (no lock-on) = 1, timed by ticks (0: permanent) |
| 13 | slots 8 and 11 = 1 (+ a float routine) |
| 14 | slot 33 (hit immunity) = 1, timed by ticks |
| 17 | slot 37 = 1 (team chat; no gameplay effect) |
| 18 | copy the target’s slots 0..3 (base, timed value, ticks) |
| 16, 19..23 | card / deck effects (decoded 11-10, see the full section) |
Status slots
Each character has 47 slots of 12 bytes at status record + 0x61B8: {base, timed value, ticks left}. Three routines touch them:
- read (slot k): base + timed + the active environment’s value for k (below), clamped to ±cap[k]. The cap table is 47 s32 in the executable: 9 for slot 0, 90 for 1..3, 4 for 9..10, 10 for 21, 22, 38 and 39, 900 for 34, 1 elsewhere.
- add (k, v, t): t > 0 makes the timed value v for t ticks. It replaces the timed value before it, so timed values don’t stack. With t = 0, v is added to the base, clamped to ±cap. set works the same, but with t = 0 the base becomes v.
- tick (every tick, all 47): ticks > 0 counts down. At 0 the timed value is cleared, so it lasts t + 1 ticks.
What a slot means: an environment record of effect type k (set 5, 0x54) adds its 0x58 to slot k of every character, through the read routine above. So the slots mean what the environment records do. This is our reading of their effects, checked against the code paths that test the slots:
| slot | meaning | slot | meaning | |
|---|---|---|---|---|
| 0 | strength: + damage of own attacks | 21 / 22 | attacks above / below a damage are banned | |
| 1 | movement speed % | 25 | erase skills banned | |
| 2 | homing % | 29 | no aura regen while moving | |
| 3 | aura regen % (the s of “Combat rules”) | 30 | costs doubled (> 0) or halved (< 0) | |
| 4 | bound (can’t move) | 31 | attack bonuses / pierce off | |
| 5 | skill buttons locked | 32 | every skill single-use | |
| 6 | each skill press costs health | 33 | hit immunity | |
| 8 | can’t be locked on to | 34 | capsule respawn delay + value ticks | |
| 11 | levitate | 35 | directional controls inverted | |
| 17 / 18 / 19 | health per cast / per capsule / per aura particle | 36 | skill buttons scrambled | |
| 20 | every attack pierces | 38 / 39 | skills above / below a cost banned | |
| 41..45 | one school banned each |
Slots 7, 9, 10, 12..16, 23, 24, 26..28, 40 and 46 are in the complete table of “Status slots, hit effects and environments in full” (docs 11-10).
Environment (set 5)
One environment slot per caster: casting stores the caster’s position and the skill, with expiry = now + 0x5A ticks when 0x5A > 0, else none (it lasts until erased or captured; a cast while another environment is active stores nothing, so it is not replaced: corrected 11-10). 0x54 is the effect type, 0x58 its value; 0x56 is the capture guard time. The effect type is a status slot number. While an environment is active, every status read of slot 0x54 adds 0x58 (see “Status slots”). Which environment counts, how they end and the capture are in “Status slots, hit effects and environments in full”.
Hit effects (set-0 field 0x62, values 0x64 / 0x66)
Applied to the character an attack hits, after the damage; a 52-way switch on 0x62 (0 = none).
- 5: explode (above).
- 1, 2, 11, 44: change the target’s aura (1) or aura level (2, 11, 44); 4, 47: set its aura level. (Corrected 11-10: these were listed as health changes. All 52 ids are in the table of “Status slots, hit effects and environments in full”.)
- 19..37: status slot 0x62 − 2 of the target set to 1 for 0x64 ticks, or permanently when 0x64 = 0 (see “Status slots”). 41 → slot 36, 52 → slot 46 (same pattern).
- 6, 7, 8: add 1 to slot 4, 5, 6 (bound, skills locked, press damage) for 0x64 ticks.
- 12..15: add 0x64 to slot 0..3 (strength, speed %, homing %, regen %) for 0x66 ticks (0 = permanent).
- 16 (a button lock),
40 (forced lock-on, slot 9) and
the rest (3, 9, 10, 17, 18, 38, 39, 42, 43, 45,
46, 48..51): one row each in the full table
(docs 11-10).
kind.hit_effect(when 0x62 ≠ 0) is {id, action, slot, v, w}: one decoded action per id from the table in “The 52 hit effects” (converterHIT_EFFECTS, the same table as godotPdHitEffect.ROWS; action names are ours).kind.hit_effect_classis the coarse class of the action: none, explode, aura_change, level_change, level_set, health_change, health_set, steal, status, reset, invert, other (hitfx 11-10: ids 1, 2, 11, 44, 4, 47 are no longer health classes). Slot writes also getstatus_slot,status_value,status_ticksandstatus_name(23, 24, 32, 36 store v for w ticks; the other direct writes 1 for v ticks).
Not decoded
The card effects 0x5C..0x60, knockdown and the hit animations 0x6E..0x74, kind 7 (partly, see “Skill casting leftovers”), the object side of kinesis, the exact pass list of an auto-shelter. Slots, status effects, hit effects and environments are in “Status slots, hit effects and environments in full”; the formulas, the erase and special sets, ricochet, the kinesis cast side and mine mode 2 are in “Skill casting leftovers” (both docs 11-10).
skills.json
kind (one object per
skill, additive): name, then the
fields above in game units with suffixes:
_ticks, _u (0.1 m),
_upt (u per tick),
_deg, _deg_per_tick (×
the homing percent p at runtime), plus
hit (swept_sphere,
bone_sphere,
swept_blade, direct,
area, none),
pass_through,
explode_radius_u (hit effect 5),
ignores_walls (0x6A = 2 or 3),
pierce (0x68 = 2). Melee, blade and
pursuit get lunge_distance (0x7E),
lunge_turn_deg_per_tick (0x80 /
10), lunge_track (0x82 ≠ 0),
radius_u (melee, pursuit) or
length_u and
target_radius_u (blade),
life_ticks (the active window;
pursuit 1). Defenses get type,
placement, shape,
radius_u, life_ticks,
durability,
durability_per_use,
passes, response,
auto (type 7),
anti_pierce, addon
(heal_blocked, aura_blocked, erase_card,
bind_attacker, lock_attacker_skills, other,
capture_card; null = none),
addon_value,
addon_melee_only. Status records
(set 4) get target (self, target,
all) and effects (id,
effect (our name),
slot, value,
ticks). Environments get
slot and slot_name,
value (0x58),
duration_ticks (0x5A, null = none)
and capture_guard_ticks (0x56;
envs: read as one four-field record,
EnvRecord in skilldata.py).