Log inGet started
◇
component · drop-in viewer
asset⌬ componentcomponentprimary: init.luau·originates fromworld e2fc9693-0…

Motor

Ilva's motor: a 2D platformer body driven on the engine's own physics.

by◐Catapulta33·posted 9d ago
What it does

umbral.Motor

Ilva's motor: a 2D platformer body driven on the engine's own physics.

Attaches to: the player body entity (the body of the scene's PlayerPrototype). It needs a BoxCollider and a Physics component — it adds both itself if they are absent — and it reads an input map carrying move, jump and sprint, which the scene supplies as inputMaps.umbralMove (keyboard, gamepad and touch together).

Why it is not a script-driven kinematics solver

The body is a dynamic rigid body with a box collider, held to the XY plane by axis locks (lockTranslationZ, lockRotationX/Y/Z). This component writes the horizontal velocity from the move control and the vertical velocity for jumps; the engine's simulation does the rest — collisions, one-way ledges, contact with anything in the world. Nothing here re-implements collision, so a ledge added anywhere in the scene works the moment it exists.

twoDKit.Player2D was installed first and rejected: its motor holds the body still unless a twoDKit.Level2D exists (update returns early on #Levels.all() == 0), and it activates controlsKit's platformer scheme, which suppresses every other input map in the player group. UMBRAL builds its own architecture, so both were dead weight here.

Feel, and the fields that set it

FieldDefaultWhat
speed7.5Top horizontal speed, units/s.
accel / airAccel60 / 34How fast she reaches it on the ground and in the air.
friction48How fast she stops with no input on the ground.
jumpSpeed15.5Upward speed a full jump gives.
jumpCut0.45Share of the rise that survives letting go early — variable height.
airJumps0Mid-air jumps. Set to 1 by the Vuelo de la Sal.
canDashfalseThe Paso de Marea.
coyote / buffer0.10 / 0.12Grace after leaving a ledge, and grace before landing for an early press.

grounded and facing are public and synced, so every peer sees her footing and her heading.

Methods

  • ref:readState() — { x, y, vx, vy, grounded, facing, clock, dashing, airJumpsLeft }. clock advancing is the proof the motor is stepping; if it stays at 0 the body is not being simulated, whatever else looks right.
  • ref:placeAt(x, y) — put her feet at a point, at rest.

The two failures worth remembering

Ground is detected through Physics.groundContact, with a short downward raycast under her feet as the fallback, so a body resting on a merged collider reads as standing.

Movement silently doing nothing has two causes seen here: a control read as v.x when the axis reports a bare number (the handler now accepts both), and a suppressed input map — the motor's own map is in the umbral group precisely because controlsKit's platformer scheme suppresses everything in player.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

UMBRAL · Ilva's motor. A 2D platformer body on the engine's own physics. The body is a dynamic rigid body with a box collider, held to the XY plane by axis locks, and this component drives it: it sets the horizontal velocity from the move control and writes the vertical velocity for jumps. The simulation does the rest — collisions, one-way ledges, the ground under her feet — so nothing here re-implements the engine's collision. Feel, in the order that matters: * acceleration and turn-around, so she has weight * variable jump: let go early and she stops rising * coyote time and a jump buffer, so a late and an early press both work * air jumps (the Vuelo de la Sal) and a dash (the Paso de Marea), locked until the game unlocks them Controls come from an input map that carries keyboard, gamepad and touch (the engine's default map does): move, jump, dash.

BoxColliderPhysics

setVel(vx: ?, vy: ?) → void

argtypedescription
vx?
vy?

getVel( ) → void

onGround( ) → void

Standing on something: ask the engine what this body rests on, and fall back to a short probe under her feet.

awake( ) → void

update(dt: ?) → void

argtypedescription
dt?

readState( ) → void

What the rest of the game reads about her.

placeAt(x: ?, y: ?) → void

Put her feet at a point, at rest.

argtypedescription
x?
y?

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

3items
This part has no composite children. See the Files segment for its leaf payloads.
backing path · umbral/Motor.component

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.