PlayerInputBridge

The missing wire between PlayerInput and Movement — the human equivalent of AIInput.

What it does

PlayerInput publishes input in its own dialect (playerInput.moveChanged, playerInput.actionPressed), but Movement listens for a different one (input.movement.vector, input.jump.requested). Out of the box, a keyboard can't drive the mover — the two components never connect. AIInput already speaks Movement's dialect, which is why an AI entity moves; PlayerInputBridge does the same job for a human.

Drop a PlayerInputBridgeComponent on the same entity that carries PlayerInput and Movement. The PlayerInputBridgeSystem listens for that entity's move-changed events and forwards them verbatim — the XZ payloads are already identical — as input.movement.vector, and translates any configured jump action into input.jump.requested. It only translates input for entities it actually governs (scoped by entityId), so two local players can each carry their own bridge with their own jump map. A pure core (isJumpAction) holds the one decision the bridge makes; both event names are imported as constants, so a rename on either side can't silently desync the bus.

Use it in a scene

{
  "Player": {
    "tags": ["player"],
    "components": {
      "PlayerInput": {},
      "Movement": { "speed": 6, "groundY": 0 },
      "PlayerInputBridge": { "jumpActions": ["jump"] }
    }
  }
}

Props

• jumpActions (string[], default ["jump"]) — the PlayerInput action names that fire a Movement jump. Add "attack" to make the primary action double as a jump.

Events

• Listens for playerInput.moveChanged (PlayerInputEvents.MOVE_CHANGED) — { entityId, x, z }.
• Listens for playerInput.actionPressed (PlayerInputEvents.ACTION_PRESSED) — { entityId, action, source }.
• Emits input.movement.vector (MovementInputEvents.SET_MOVEMENT_VECTOR) — { entityId, x, z } — forwarded verbatim.
• Emits input.jump.requested (MovementInputEvents.JUMP_REQUESTED) — { entityId } — when a pressed action is in jumpActions.

Dependencies

PlayerInput (the emitter it translates) and Movement (the consumer it feeds). Put all three on the same entity.

Notes

• Pure EventBus relay — no per-frame work, no renderer access.
• It forwards only for entities that carry the bridge, so an AI entity emitting input.movement.vector directly (via AIInput) and a human routed through the bridge never collide.
• The move payload is forwarded unchanged because PlayerInput's { entityId, x, z } already matches what Movement expects — the bridge exists for the name mismatch, not a shape mismatch.