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

World

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

by◐lauramarka·posted 1mo ago
What it does

World

<!-- 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.world.World — the village. ONE CONTINUOUS PLACE, NOT SEVEN ROOMS. The brief lists eight locations, and a village is exactly the kind of world where they are simply adjacent: the lane runs past the houses, the yard is behind the lane, the paddy is past the yard, the pond is at the end of it. So they are built once, at real positions, and moving between them is walking. That is also what makes the `place` event cheap — it says where the story is, not which room to teleport into. LAID OUT AS A RULE, NOT BY HAND. Every wall, door and roof panel comes from `wall()`, `opening()` and `pitchRoof()`, and every run of them from a loop with a count. The scenes guide's test applies: change the number of houses and one edit is enough. BUILT TO HUMAN SCALE, and that is load-bearing. Doorways 2.05 m, seat height 0.45 m, table 0.90 m, step risers 0.16 m, lane 3.2 m. The village is authored to the dimensions a real adult occupies, NOT to the proportions of the low-poly stand-in currently wearing the player's body — so a correctly-scaled realistic model simply fits when it arrives. See `game/cast/MODELS.md`. MATERIALS ARE AUTHORED, NOT GENERATED. Each surface is a lit surface with its own base colour, because generated texture plates could not be relied on (the image service left ten jobs orphaned). Every tint below is from the art direction, so the village reads as mud, thatch, tin and wet earth from its material properties. When real textures exist, each drops onto a material that is already the right colour — one line per surface, no geometry change.

ModelBoxCollider

tint(e: ?, colour: ?) → void

Tint a surface. The tint fields live on the MODEL COMPONENT, not on the entity — writing `entity.tintR` is silently ignored, because no such entity property exists, and the whole village renders white with no error anywhere. Reach the component and set the field on it.

argtypedescription
e?
colour?

box(name: ?, parent: ?, x: ?, y: ?, z: ?, sx: ?, sy: ?, sz: ?, colour: ?) → void

A box of a given size at a given place. The one primitive the whole village is made of; everything below is a composition of these.

argtypedescription
name?
parent?
x?
y?
z?
sx?
sy?
sz?
colour?

wall(name: ?, parent: ?, x: ?, y: ?, z: ?, sx: ?, sy: ?, sz: ?, colour: ?) → void

A solid wall with its collider, so the player cannot walk through the house.

argtypedescription
name?
parent?
x?
y?
z?
sx?
sy?
sz?
colour?

opening(name: ?, parent: ?, x: ?, z: ?, spanX: ?, wallH: ?, thickness: ?, colour: ?) → void

argtypedescription
name?
parent?
x?
z?
spanX?
wallH?
thickness?
colour?

pitchRoof(name: ?, parent: ?, x: ?, y: ?, z: ?, spanX: ?, depth: ?, colour: ?) → void

A pitched roof, as two tilted slabs. `rotation` is a quaternion, and Transform.quatFromAxisAngle hands its four components back separately, so it goes in braces.

argtypedescription
name?
parent?
x?
y?
z?
spanX?
depth?
colour?

tree(name: ?, parent: ?, x: ?, z: ?, height: ?, spread: ?, trunkColour: ?, crownColour: ?) → void

A tree. The first version was a thin trunk with ONE flat box on top, which reads as a lollipop on a stick — the worst thing in the frame. A palm is a crown of fronds radiating from the top of a bare trunk, so the crown is built as several lobes with a central mass, and a shade tree gets a shorter, thicker trunk and a deeper crown. Still boxes; the shape is what carries it.

argtypedescription
name?
parent?
x?
z?
height?
spread?
trunkColour?
crownColour?

bush(name: ?, parent: ?, x: ?, z: ?, size: ?, colour: ?) → void

Small vegetation: a clump of bushes, the low scrub that grows along every bund and wall foot in a village. Three overlapping masses, waist height or below, so the ground is not bare without costing much.

argtypedescription
name?
parent?
x?
z?
size?
colour?

buildGround(root: ?) → void

The pieces

argtypedescription
root?

buildLane(root: ?) → void

argtypedescription
root?

buildFamilyHouse(root: ?, x: ?, z: ?) → void

The family house, in its yard. Built from the rules above: a plinth, four walls with one real doorway, and a pitched thatch roof.

argtypedescription
root?
x?
z?

buildCourtyard(root: ?, x: ?, z: ?) → void

The yard: swept, with the cooking hearth, a water jar, a rope bed and the tree that gives it shade. This is where most of the story happens.

argtypedescription
root?
x?
z?

buildPond(root: ?, x: ?, z: ?) → void

The pond, at the end of the lane, with its steps down to the water.

argtypedescription
root?
x?
z?

buildFields(root: ?, x: ?, z: ?) → void

Two strips of paddy on the raised ground past the yard, with the bund between them that the story walks along.

argtypedescription
root?
x?
z?

buildBazaar(root: ?, x: ?, z: ?) → void

The tea stall and the shop, on the bazaar stretch of the lane.

argtypedescription
root?
x?
z?

build( ) → void

awake( ) → void

start( ) → void

rebuild( ) → boolean

Rebuild the village. Safe to call — the build runs once per life.

examples

entity.find("World").component.get("game.world.World"):rebuild()

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

7items
▣
module · born here
❒asset
# game.Game The spine of **Hidden Love — A Bangladeshi Romance Story**. One shared module holding the constants and the rules, so no two slices have to agree by convention. ```lua local Game = require("game.Game") Game.bus.on("chapter", function(n) print(n) end) ``` Nothing here touches the engine at require time — it is data and pure functions, safe to require from a scene entrypoint, a component, a module or an `execute` chunk. ## What it holds | Field | What it is | |---|---| | `ART` | The art-direction sentence, verbatim from the reference pass. Every generated prompt reuses it word for word. | | `TITLE` / `SUBTITLE` / `ENDING_TITLE` | The title card and the closing card. | | `CAST` | The seven named people: who they are, what they wear, and the reference image for the two leads. | | `CHAPTERS` | The twelve chapters in order — `place`, `who`, `beat`, `objective`. The storyline is this table. | | `PLACES` | The seven sets the world slice builds, each with the reference image it answers to. | | `METERS` / `TIERS` | friendship, trust, closeness — and the three ways the same ending can land. | | `MOUNTS` | The names of the scene's mount entities a slice attaches to. | | `SLICES` | The five slice modules the entrypoint requires and mounts. | | `bus` | `on` / `off` / `emit`. How slices talk without requiring each other. | ## The rule the whole game runs on Every chapter reaches the end. The meters decide how *warm* the telling is, not whether it finishes — `warmth(state)` is the mean of the three meters as 0..1, and `tier(state)` names what that earns at the finale. ## State and saving `Game.newState()` is the whole save: chapter, the three meters, the choices taken, flags, the phone log, and time in chapter. `Game.SAVE_PATH` is where it is written, under `/zero/source/local/`. `Game.addMeter(state, key, amount)` clamps and announces on the bus; move the relationship through it and never by assignment, so everything watching stays in step. ## Mounting The scene lays down one entity per key in `Game.MOUNTS` and the entrypoint hands them to each slice's `mount(refs)`. A slice that is not present yet is not an error — the scene loads without it.
▲ 0↑ born
backing path · game/world/World.component

Problems

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

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬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.