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

Interactor

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

by◐kemz·posted 1mo ago
What it does

Interactor

<!-- 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.player.Interactor — the player's one verb. Mounted once, on the scene's `mount_player`. Every frame it finds the nearest thing `game.player.interact` is offering and tells the world what is in front of the player, then watches the key. It owns no interactions of its own: a shop, a door, a car and the memory slice's street arguments all arrive here the same way. It announces on the bus rather than drawing anything itself, so the HUD shows the prompt and the slice that offered the action gets told when it is taken.

positionOf(ent: any) → void

argtypedescription
entany

held(name: string) → boolean

argtypedescription
namestring

reachable( ) → any

What the player is currently able to act on, or nil.

awake( ) → void

update(_dt: number) → void

argtypedescription
_dtnumber

onDestroy( ) → void

readout( ) →

What the player can act on right now, read back from the same value the prompt draws.

take( ) →

Take whatever is in front of the player, without a key press.

Sub-parts

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

11items
▣
module · born here
❒asset
# game.core **The shared vocabulary of THE CITY REMEMBERS.** Every build slice reads it; no slice writes it. It answers the questions five agents building at once would otherwise each answer differently: where the districts are, how big a block is, what the clock says, what a reputation score is worth, how much heat is a star, which colours the references were drawn in, and the names of the scene entities each slice attaches its component to. It holds **no behaviour**. Rules live here (a pure function from position to district, from score to band, from heat to stars); systems live in the slices. ## What is in it | Field | What it settles | |---|---| | `city` | 9 × 9 grid of 80 m blocks on a 100 m pitch, 20 m streets, origin at block (4, 4), ground 1400 m. | | `districts` | The six districts in the ledger's own order, each with the grid test that claims a cell and its character, height range, density and police presence. | | `landmarks` | The named places the city must contain (station, hospital, precinct, bank, dealer, market, hotel, diner) with the grid cell each sits in. | | `clock` | One game day is 24 real minutes. Day 1 begins at 07:20, when the player steps off the train. | | `reputation` | One score per district, −100 … +100, labelled in the ledger's six bands: RESPECTED, CAUTIOUS, NEUTRAL, SKEPTICAL, WARY, HOSTILE. | | `wanted` | Heat in points, five star thresholds, decay and the cooldown before heat falls. | | `money`, `health`, `xp` | Starting money 0, health, regen, hospital fee, and the rank ladder from NOBODY upward. | | `memory` | The fifteen memory kinds with each one's reputation weight, witness radius and ticker pattern, plus the bond thresholds that turn a stranger into an ally or a foe. | | `palette`, `ui` | Every colour in the references, so five slices produce one city. | | `ids` | The scene's named entities and the six mounts each slice attaches to. | | `camera`, `arrival` | The gameplay camera's setting, and where the player arrives. | ## Functions ```lua local Core = require("game.core") Core.districtAt(x, z) -- -> "oldTown" the district a world position is in Core.districtName("oldTown") -- -> "Old Town" Core.cellOf(x, z) -- -> i, j the grid cell a position falls in Core.blockCentre(i, j) -- -> x, z world centre of a cell Core.clockOf(elapsed) -- -> { day, label, phase, ... } Core.dayStamp(5) -- -> "DAY 5" Core.reputationLabel(70) -- -> { label = "RESPECTED", colour = "teal" } Core.wantedStars(140) -- -> 3 Core.rankName(500) -- -> "SOMEBODY" Core.memoryShape() -- -> the shape one stored memory has ``` ## The mounts A slice attaches its component to its own mount and to no other one. The mounts are entities the scene build places; adding a component to one is an `entityOps.addComponents` call and does not involve writing the scene file. ``` mount_city the city's geometry and atmosphere mount_life pedestrians, traffic, the police mount_memory the memory ledger and reputation mount_player the player, vehicles, the arrival mount_ui every screen mount_world weather and ambience ``` ## The memory contract `game.core` defines what a memory *is*; `game.memory` (the memory slice) is what stores one. Any slice that wants the city to remember something calls: ```lua require("game.memory").record({ kind = "helped", district = Core.districtAt(x, z), subject = npcId, subjectName = "the man from the alley", text = "Helped a stranger out of a bad alley.", x = x, z = z, }) ``` and the memory slice dates it, weights it, files it, moves that district's reputation, gives it to whoever saw it, and draws it in the ledger.
▲ 0↑ born
▣
module · born here
❒asset
# interact <!-- 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.
▲ 0↑ born
backing path · game/player/Interactor.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.