bind wasd keys to move the player

One canonical InputProfileComponent holds an actions array. Each action has key, valueType, contexts, policy, prediction, and bindings that map device sources to the action. Bind keyboard, mouse, gamepad, touch, or xr devices; the schema constrains device, control, event, trigger, and processor kinds.

map keyboard and gamepad controls to actions

One canonical InputProfileComponent holds an actions array. Each action has key, valueType, contexts, policy, prediction, and bindings that map device sources to the action. Bind keyboard, mouse, gamepad, touch, or xr devices; the schema constrains device, control, event, trigger, and processor kinds.

add a jump button and fire button binding

One canonical InputProfileComponent holds an actions array. Each action has key, valueType, contexts, policy, prediction, and bindings that map device sources to the action. Bind keyboard, mouse, gamepad, touch, or xr devices; the schema constrains device, control, event, trigger, and processor kinds.

remap controls for keyboard mouse and gamepad

One canonical InputProfileComponent holds an actions array. Each action has key, valueType, contexts, policy, prediction, and bindings that map device sources to the action. Bind keyboard, mouse, gamepad, touch, or xr devices; the schema constrains device, control, event, trigger, and processor kinds.

Input mapping actions bindings keyboard mouse gamepad touch

The recipe

Attach InputProfileComponent with project_add_component (project.entity.component.set): { "type":"InputProfileComponent", "version":1, "actions":[ ... ] }.
Each action object needs: key (stable id), valueType (one of boolean, float, vector1d, vector2d, vector3d, world_target, screen2d, trigger, composite), contexts (for example ["gameplay"]), triggers, processors, policy, prediction, and bindings.
policy.effectSystem routes the action: movement, action, script, or look. Set movement for WASD, look for mouselook (add the policy.look block), action for verbs (fire, interact).
prediction.mode is client_predicted (responsive movement), client_only (look), or server_authoritative (anti-cheat verbs).
A binding maps sources to the action: { "id":"binding.move.wasd", "sources":[{ "device":"keyboard", "control":"KeyW", "event":"down", "modifiers":[] }, ...], "triggerOverrides":[], "processors":[], "priority":0 }. Valid devices: keyboard, mouse, gamepad, touch, xr. Valid events: down, up, press, move, axis, sample.
For a jump button, add a boolean action with a keyboard Space down binding. For gamepad, add a second binding with device:"gamepad". For mobile, add a touch binding to the same action; one action, many devices.
Shape raw input with processors[].kind: deadzone, curve, invert, sensitivity, clamp, normalize, axisComposition, stickComposition, threshold, quantize. Shape timing with triggers[].kind: pressed, released, held, tap, doubleTap, hold, chord, continuous, continuous_delta, step, cancel.

Pitfalls

Trigger and processor parameters are discriminated by kind. A hold trigger needs parameters.durationMs (1..60000); a curve processor needs scale/exponent. Mismatched parameters are rejected; you cannot edit one leaf at a time and stay valid.
policy.look.sensitivityDeg is clamped 0.001..45 and pitch bounds -89..89.
version is readonly to most surfaces; keep it 1 unless you are migrating.
The removed InputActionDeclarationComponent, InputBindingSetComponent, and InputContextStackComponent all fold into this one component; never author them.

Verify

engine_get_component_schema on InputProfileComponent for projected field contracts before writing a binding. Device-dependent control checks live in InputSourceSpecSchema in packages/ecs/src/index.ts; use the native mouse binding shown in the first-person-controls playbook for look input.
simulation_run to confirm the action fires on the mapped control.

The recipe

Pitfalls

Verify

On this page