Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld 07a07267-3…

input

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

by◐lolboy21·posted 1mo ago
What it does

input

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

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.input — THE ONE OWNER of the control map. Two things were reading this map at once: the `CharacterController` on the player's body (which is handed `inputMap` by the scene and reads movement itself) and the weapon slice, which activated the same map a second time for the trigger and the reload. An input map hands out ONE control set, and the second activation takes the deliveries — so the weapon buttons worked and the body never moved, and a button whose last delivery was `true` stayed true, which is a weapon that fires on its own. So there is exactly one activation, here, and everything that wants to know what the player is doing reads it from here. This module owns READING, not deciding. It publishes what the controls say and hands out one-shot presses; the player slice decides what a body does with them, and the weapon slice decides what a trigger does.

bindButton(ctrl: ?, slot: ?, edge: ?) → void

argtypedescription
ctrl?
slot?
edge?

bind( ) → void

Activate the map, once, and bind every control the game reads. Safe to call from wherever: a second call is a no-op, because a second call is the bug this module exists to prevent.

state( ) → void

The live values. Read them every frame; never cache them across one.

takePress(name: ?) → void

Take a one-shot press, clearing it. Answers true once per press.

argtypedescription
name?

rest( ) → void

Release everything, for a respawn or a mode flip. Held controls keep their last value otherwise, which is a player who keeps walking after they died.

unbind( ) → 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.

Showing up to 3 levels deep. Open a part to see what it holds further down.

21+items
·
inputmap · born here
❒asset
# operator Unbroken Front — the operator's controls: move, look, fire, aim, reload, jump, sprint, crouch, interact, weapon switching and leaning.
▲ 0↑ born
·
inputbinding · born here
❒asset
# aim The 'Aim' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# attack The 'Attack' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# crouch The 'Crouch' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# inspect The 'Inspect Weapon' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# interact The 'Interact' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# jump The 'Jump' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# lean_left The 'Lean Left' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# lean_right The 'Lean Right' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# look The 'Look' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# menu The 'Menu' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# move The 'Move' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# next_weapon The 'Next Weapon' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# reload The 'Reload' control.
▲ 0↑ born
·
inputbinding · born here
❒asset
# sprint The 'Sprint' control.
▲ 0↑ born
backing path · game/player/input.module

Problems

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

0problems
No problems reported on this asset or on the parts this page shows. Parts it leaves out are not counted here.
⌬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.