Interact
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->
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.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
conforms to
zero/source-extract/v2game.interact.Interact — the interaction system. ONE SYSTEM, NOT ONE SCRIPT PER OBJECT. Anything interactive is an ENTRY in a registry: a place in the world, how close you must be, what it says when you are close enough, and what happens when you press the key. Nothing about the player is baked into an object, and nothing about an object is baked into the player — so a new interactive thing is one `register()` call and no new code. interact:register({ label = "Open the gate", x = -5, z = 6, radius = 2.2, action = "door", target = gateEntity }) WHAT IT PUBLISHES, and why over the bus: the prompt has to be DRAWN by the screens slice and the story has to REACT to what was touched. So this slice owns neither. It emits: "prompt" (label) or (nil) when nothing is in range "interact" (action, entry) when the key is pressed "beat" (beatKey) for a story moment an object triggers THE KEY. `E` is read from the input map, but a component that polls raw input and a component that answers a call are the same component here: `press()` is the action, and the input binding calls it. That keeps the system testable without a keyboard, which is how it was verified.
register(entry: { [string]: any }) → number
Add something interactive. The one call that makes a new object usable — nothing else in this file needs to know it exists.
| arg | type | description |
|---|---|---|
| entry | { [string]: any } | name, label, x, y, z, radius, action, and an optional target entity. |
examples
interact:register({ name = "gate", label = "Open the gate", x = -5, z = 6, radius = 2.2, action = "door" })buildRegistry( ) → void
The village as it stands: the house door, the things in the yard, the water, the stall and the shop. Positions are the world slice's own, so this does not guess at geometry it did not build.
buildDoor(entry: ?) → void
A door that actually swings. The leaf is built here rather than in the world slice because it is the interaction system that owns what a door DOES; the world only declares where the opening is. Without this the doorway is a hole.
| arg | type | description |
|---|---|---|
| entry | ? |
toggleDoor(name: ?) → void
| arg | type | description |
|---|---|---|
| name | ? |
press( ) → string
Perform the interaction on whatever is in range. Safe to call with nothing in range — it does nothing and says so.
examples
interact:press()
playerPosition( ) → void
distance(a: ?, b: ?) → void
| arg | type | description |
|---|---|---|
| a | ? | |
| b | ? |
awake( ) → void
start( ) → void
update(dt: ?) → void
Cheap: one position read and a distance per registered thing, and the bus only hears about it when the thing in range CHANGES — not every frame.
| arg | type | description |
|---|---|---|
| dt | ? |
onDestroy( ) → void
Sub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
agent_score is exposed.+ 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".
Scoped to this part · feeds back into the world's score.