Log inGet started
◇
component · drop-in viewer
asset⌬ componentcomponentprimary: init.luau·originates fromworld 76197f6f-8…●2problems

WorldBuilder

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->

by◐Daksh·posted 1mo ago
What it does

WorldBuilder

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->

TODO: describe this 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

game/WorldBuilder.component/init.luau THE MISSING FLOOR — puts the building in the world. A thin shell: it finds GameRoot, hands it to `game/world.module`, and then runs the one piece of per-frame work the building has — the light cull. Everything else about the building is the world module's, and it is rebuilt from code every time play starts, which is what keeps it out of scene.json and lets a floor be re-laid-out without re-baking the scene. It runs first of all the systems (`executionOrder = -100`) because everything else — the presence's routes, the lift's shaft, the interaction raycasts, the checkpoints — is placed against it.

build( ) → void

clear( ) → void

goTo(n: ?) → void

The player's storey changed: light it, and put its neighbours on notice.

argtypedescription
n?

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 · game/WorldBuilder.component

Problems

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

2problems

Inside

2 problems across 1 item
●
dep.unresolved · L53
could not resolve `./world.module`
●
dep.unresolved · L54
could not resolve `./core.module`
⌬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.