Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld 76197f6f-8…●2problems

world

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

by◐Daksh·posted 1mo ago
What it does

world

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

TODO: describe this module.

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/world.module/init.luau THE MISSING FLOOR — the building. `M.build(root)` spawns the whole block under `root`: the street, the ground floor, and floors 2 to 11 as ONE RULE run in a loop. `M.destroy()` clears it. Nothing here ticks per frame except the light cull, which is the only thing that must.

ModelInteractable

paletteFor(n: ?) → void

argtypedescription
n?

bandedWall(opts: ?) → void

The lower half of every corridor wall is the institutional green the whole building is painted in; the upper half is the nicotine cream. Two runs per wall, which is what makes the corridors read as the reference rather than as a grey tube.

argtypedescription
opts?

street(root: ?) → void

argtypedescription
root?

liftShaft(root: ?) → void

argtypedescription
root?

storeyCore(root: ?, n: ?) → void

Everything that repeats on 2..11, and under the ground floor too.

argtypedescription
root?
n?

apartment(floorRoot: ?, n: ?, sgn: ?, num: ?, zc: ?, pal: ?, full: ?) → void

One apartment: a door opening in the corridor wall, a leaf on a hinge, a number plate, and — where it matters — the room behind it. `full` says whether to build the room out or leave a shallow stub; most of the building's flats are locked, and the ones the player can actually walk into are the ones worth standing in.

argtypedescription
floorRoot?
n?
sgn?
num?
zc?
pal?
full?

dress(floorRoot: ?, n: ?) → void

What a floor has in it beyond its walls. Every one of these leaves a named entity so the story and dread slices can find it.

argtypedescription
floorRoot?
n?

impossibleFloor(root: ?) → void

Floor 11: the same corridor, and not the same at all.

argtypedescription
root?

groundDressing(root: ?, floorRoot: ?) → void

argtypedescription
root?
floorRoot?

storeyLights(floorRoot: ?, n: ?) → void

Every other floor's five lights. They sit at `y + ch - 0.2` — the ceiling of THIS floor, not the ceiling of the ground floor, which is the mistake that puts every strip in the building on top of each other.

argtypedescription
floorRoot?
n?

roofFloor(floorRoot: ?, n: ?) → void

Floor 10's maintenance room and roof access, and the records that make it the major clue.

argtypedescription
floorRoot?
n?

floorRoot(n: ?) → void

argtypedescription
n?

destroy( ) → void

ensureFloor(n: ?) → void

Build ONE storey, the first time anything asks for it, under the building root. Storeys cost about a fifth of a second each to lay out, so ten of them up front is a freeze at play start; three is a blink, and the lift calls this for the storey it is going to before it moves.

argtypedescription
n?

build(root: ?) → void

argtypedescription
root?

playerFloor( ) → void

setActiveFloor(n: ?) → void

Only three storeys are ever live: the one the player is on and the two it can reach. Everything else is switched off, which is what keeps the number of lights the renderer sees in the teens rather than the hundreds.

argtypedescription
n?

retune( ) → void

A cheap retune, called by the WorldBuilder once every quarter second.

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.

5+items
◇
component · born here
❒asset
# interact <!-- 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.
▲ 0↑ born
backing path · game/world.module

Problems

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

These counts cover only the parts this page shows. Problems on the parts it leaves out are not counted here.

2+problems

Inside

2 problems across 1 item
●
dep.unresolved · L51
could not resolve `./core.module`
●
dep.unresolved · L52
could not resolve `./build.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.