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

Interactable

<!-- 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

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/v2

game/interact.component/init.luau THE MISSING FLOOR — the interaction contract. One component says "this thing can be touched". Whoever builds a note, a door, a lift button, a fuse box or a photograph attaches this to it and describes it in four strings; the player's interactor finds it, shows the prompt, and on [E] fires it. Neither side needs to know about the other. A system that wants to REACT to an interaction subscribes to the bus rather than hunting for the entity: local Core = require("./core.module") Core.Bus.on("interact", function(ev) if ev.kind == "note" and ev.payload == "note_intro" then ... end end) The bus event is { kind, payload, id, label, verb, entity, by } — `by` is the avatar entity that touched it, which is how an interaction reaches the player. PUBLIC FIELDS kind what it is, for the handler to switch on verb the word on the prompt: READ, OPEN, TAKE, PRESS, USE, LOOK label the noun after the verb: "note", "apartment 703", "elevator panel" payload the id the handler keys on — unique per object in the game active set false to take it out of the world without despawning it range how close the player must be, in metres (default 2.6) once true = it can only be used once, then it goes quiet loud true = using it makes noise the presence can hear locked true = it shows its prompt but refuses (see lockedText) lockedText what to say when it refuses ("It's locked.")

awake( ) → void

The interaction that replaced `held`/`locked`.

onDestroy( ) → void

promptText( ) → void

What the HUD should show for this object, or nil if it should show nothing.

inRange(pos: ?) → void

Is this reachable from `pos` (a vec3-ish table)?

argtypedescription
pos?

trigger(by: ?) → void

Touch it. Returns true if the interaction was accepted. A locked object refuses, says so, and is still "used" in the sense that the player's attention is taken — so it returns true and lets the caller show the refusal line.

argtypedescription
by?

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/Interactable.component

Problems

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

3problems

Inside

3 problems across 1 item
●
dep.unresolved · L77
could not resolve `./core.module`
●
dep.unresolved · L82
could not resolve `./core.module`
●
dep.unresolved · L114
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.