Stage bounds and the
pit (executable + stage collision)
Barriers: each arena’s
model 0 holds collision-only index buffers
(vertex format 0x08, positions only), written by
the converter as model_0_collision.
They are mostly vertical faces (st03: 64 of 87
triangles; st05 46 of 66; st07 42 of 126; st01
has none): the invisible walls. Godot adds them
as colliders with the arena only without
collision.json; the game’s
characters collide with the .dat
collision set instead (“Stage collision”).
The fall check (character
tick): a body is sent back when its height is
below the stage’s kill height,
or when the ground attribute under it is
0x11. The kill height is a stage
global: 0 by default, −500 on stages
whose number ends in 9, and one stage
object type sets its own. st03’s model 0 has a
flat plane at exactly height 0 under the whole
arena (the pit floor); a body landing on it is
at the kill height, not below, so the attribute
is what catches it there. (Decoded 11-10: the
ground attribute is the attribute of the
collision mesh the floor pick grounds on, and
attribute 0x11 is in no stage file of this
build, so only the kill height sends a body
back; that render plane is not in the collision
set, a body falls past height 0. “Collision
attributes, groups and casts”.) Measured in
Godot (rays straight down to 80 m below the kill
height, the converted collision): the spots
where versus/net/orbs runs sent bodies back on
st01 ((27.4, 20.1), (18.9, 17.8), (30.7, 14.8)
m) and st07 ((−17.95, 29.27)) have no
floor under them within ±2 m (st01’s
are outside its arena box, which ends at x =
23.2); those bodies had run off the edge (st01
has no collision-only barrier buffers). st01
does have floor at y = −1.0 m along its west rim
(x ≈ −22), below the kill height. Body origin =
the feet (capsule centre +0.9 m).
Sent back: the respawn
point is the start record of the player’s own
slot (slot mod the start set’s player count, the
active CP00 set), placed on the
ground; the body’s position history is reset to
it. Then 3 damage through the
plain health change (no hit, no reaction, no
invulnerability check); still alive: the idle
action and the no-damage timer = 90
ticks (sent to the other peers in
online play); at 0 health the usual
knockout.
No-damage timer and the
blink: one per-player timer (it is also
what the get-up (animation length + 45) and the
respawn (90) set). While it runs, hits do
nothing, and the character is not drawn
on ticks when the timer is odd: a 15 Hz
blink.
Who sets the timer(fixes 11-13, M): the only writers of C
+ 0x6434 in the executable are the pit return
(0x140251d80, 90), the respawn (0x140251f80, 90;
called only at 0x140261e6f, in the message-18
routine 0x140261de0, and at 0x14027ce33, a net
message receiver), the get-up (0x14025c447,
length + 45) and the net message 19 receiver
(0x14027ce84). None is on the battle start or
the ready phase (0x14012ade0), so a match starts
with no timer and the bodies are drawn through
the countdown (the character’s initial value
comes from its zeroed set-up: not followed). The
Rebirth PC footage of 11-13 agrees (no blink
during “3, 2, 1”).