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

Look

The side camera. An orthographic camera that rides the player down Véspera.

by◐Catapulta33·posted 9d ago
What it does

umbral.Look

The side camera. An orthographic camera that rides the player down Véspera.

Attaches to: the CameraRig entity of the scene's PlayerPrototype. It needs a sibling Camera component — that is what it writes each frame — and it is happiest beside an AudioListener.

Why the behaviour field is empty

Camera.behavior is left unset on purpose. The engine documents that a camera with no behaviour has nothing overwriting its transform, which is what lets this component own the pose every frame without fighting a built-in rig. The built-in twoDKit.Camera2D was rejected: it is pixel-perfect for a 128×128 atlas of 16 px tiles, and UMBRAL's reference art is painterly.

Fields

FieldDefaultWhat
height9World-space vertical extent the frame covers (orthoHeight).
damp0.10Follow smoothing per frame at 60 Hz.
lookAhead2.6How far ahead of her travel the frame leads, in world units.
lookDown1.2How far the frame drops when she is falling.
distance14How far in front of the play plane the camera sits.

How it follows

It reads the entity in Camera.follow, which the engine binds per peer when a player's prototype clone spawns — so every player looks through their own camera at their own body, and no id is ever authored ahead of time. If that slot is not readable it does nothing rather than guessing, which is why a camera that never moves means the follow binding is missing rather than the maths being wrong.

The aim is the body's position lifted 1.9 units, so the frame is centred on Ilva rather than on her feet; the horizontal lead is read from her travel and clamped, so a sprint leads the frame and a standing still camera does not creep.

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 · the side camera. One orthographic camera that rides the player: damped, with a dead zone and a little look-ahead in the direction Ilva is running, so the frame always shows the way she is going. It never shakes and never snaps. The Camera component's `behavior` is left empty on purpose, so nothing else writes the transform and this component owns the pose every frame. The followed entity comes from `Camera.follow`, which the engine binds per peer; when that is not readable it finds the local Player2D body.

findFollow( ) → void

findSiblingBody( ) → void

The camera and the body are siblings under the PlayerPrototype, and the engine only binds `Camera.follow` when a behaviour asks for it — with the behaviour empty it stays nil, which is exactly the case here. So take her from the prototype: the sibling carrying the motor.

readPos(e: ?) → void

argtypedescription
e?

awake( ) → void

update(dt: ?) → void

argtypedescription
dt?

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/Look.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.