UMBRAL — Bajo el mar, alguien sigue llamando
README.md
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
| Field | Default | What |
|---|---|---|
height | 9 | World-space vertical extent the frame covers (orthoHeight). |
damp | 0.10 | Follow smoothing per frame at 60 Hz. |
lookAhead | 2.6 | How far ahead of her travel the frame leads, in world units. |
lookDown | 1.2 | How far the frame drops when she is falling. |
distance | 14 | How 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.