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

BellLook

Gives every bell in the map its real body.

by◐Catapulta33·posted 9d ago
What it does

BellLook

Gives every bell in the map its real body.

build.luau places each bell as bell_<name> carrying a cube and a turquoise Light; the shape is a stand-in for the art. This component — attached to the Map root by umbral.Art.decorate — finds those entities and replaces the cube with umbral.art.meshes.bell_great, the generated bronze bell (cracked, verdigrised, names engraved around the lower band).

It replaces the whole Model rather than writing its model field: a write to that field after the component exists reads back as the new mesh but never reaches the renderer, so the bell would keep drawing its cube. Each bell keeps its position, the scale umbral.Art gives it from its own radius, and its Light.

Idempotent: it runs once and stops. Siblings it needs: nothing.

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 · BellLook — the great bells, where the scene left a stand-in. `build.luau` gives every `bell_<name>` entity a cube: the shape is a placeholder the art replaces. `umbral.Art` puts the generated bronze bell on them by writing `Model.model`, which does not reach the renderer — the value reads back as the mesh while the entity keeps drawing the cube. So this component does it the way that works: each bell is given a fresh Model carrying the bell mesh, keeping the position, the scale the art chose for its radius, and the Light the map already hung on it.

Model

bellRef( ) → void

bellMatRef( ) → void

The bell mesh carries its own bronze material: the salt crust, the verdigris and the engraved band are in that material's maps, so it is named with the mesh rather than letting the Model fall back to a flat pale surface.

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
△
mesh · born here
❒asset
▲ 0↑ born
◐
material · 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.