No description provided yet.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
conforms to
zero/source-extract/v2controlsKit.exampleGame: what a game's own controls look like beside the kit. A game hears its actions through controls of its own: `jump` on Space and the pad's south button, `dash` on Shift and the right bumper, `move` on WASD and the left stick. It needs no touch binding for them: while a kit scheme is live, the kit's touch buttons, sticks and gestures press these same controls (through `Zin.scheme.drive`), so a tap on the kit's Jump button is a press of this `jump`, exactly as Space is. Nothing activates this map by itself. Activate it (or your own) from a component and subscribe: `local map = asset.resolve("controlsKit.exampleGame", "inputMap"):activate()` then `map.jump:onPressed(fn)`. The kit's tests use it to prove the touch path.
An example of a game's own controls (jump, dash, move) beside controlsKit: keys and pad bind them directly, and the kit's touch buttons, sticks and gestures press the same controls. Used by the kit's tests and README.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.