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

IlvaLook

Puts Ilva's real body where the scene left a stand-in.

by◐Catapulta33·posted 9d ago
What it does

IlvaLook

Puts Ilva's real body where the scene left a stand-in.

build.luau gives the player's visual (IlvaVisual, a child of the motor's body) a capsule, because the look has to be replaceable without touching movement. This component — attached to the Map root by umbral.Art.decorate — waits for the player rig to exist (it is a prototype, so it is only there once the peer has joined), points the visual's Model at umbral.art.meshes.ilva, and scales and offsets her from the visual's own measured bounds so her feet stand on the body's origin and she is as tall as her collision box, 1.25 units.

It is idempotent: a visual already carrying the mesh and standing at the right size is left alone, and it stops correcting once the measurement agrees with the target.

Siblings it needs: nothing. It only reads IlvaVisual and its Model component.

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 · IlvaLook — her body, where the scene left a stand-in. `build.luau` hangs `IlvaVisual` under the motor's body and fills it with a capsule: the look is deliberately something a mesh can replace without touching movement. This component is attached to `Map` by `umbral.Art` and does that swap. It cannot happen in the scene build itself — the player rig is a prototype that only exists once the peer has joined — so the component waits for `IlvaVisual` to appear and then dresses it. Two things this has to get right that are not obvious: * Writing `Model.model` on an existing component does not reach the renderer. The value reads back as the mesh and the entity keeps drawing the old geometry, so the visual is given a *fresh* Model carrying the mesh instead of a mutated one. * The generated mesh reports a bounds box twice the size it draws at, so a scale taken from that number leaves a half-size Ilva in the room. The fit is measured off the entity's own bounds each frame and corrects itself until the measurement agrees with the target, which is also what puts her feet on the body's origin — the collision box extends up from there, so the two have to agree for her to stand on the floor.

LightModel

meshRef( ) → void

matRef( ) → void

The mesh carries its own PBR material with it: the armour's bronze, the patina, the bone-white cape. A Model added with the mesh alone draws it as a flat pale ghost, so the bundle's material is named with it.

lantern(visual: ?) → void

Her lantern, lit. The reference's Ilva carries a brass lantern with a blue flame at her belt and the mesh has the lamp modelled into it, but nothing in the scene lights it, so at gameplay distance her bronze reads as a black silhouette. A small cold light at the hip is that flame: it picks the armour and the salt crust out of the dark without touching the room's own light.

argtypedescription
visual?

step( ) → 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.

Showing up to 3 levels deep. Open a part to see what it holds further down.

11+items
◐
material · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
❒
bundle · born here
❒asset
▲ 0↑ born

Problems

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

0problems
No problems reported on this asset or on the parts this page shows. Parts it leaves out are not counted here.
⌬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.