input-system

Generate strongly-typed C# classes from your Input Action Asset, enable the correct action map at runtime, and subscribe to performed or canceled callbacks. This reliable event handling ensures your gameplay logic responds correctly across keyboard, gamepad, and touch devices.

Runtime rebinding in Unity is implemented through an interactive rebinding flow that lets players change controls and persist binding overrides. This allows users to customize their keyboard and gamepad inputs while saving those preferences for future gameplay sessions.

Input buffering is a pattern that captures player inputs slightly before they can be consumed, such as jump commands. By storing these inputs briefly, Unity gameplay remains responsive and prevents missed button presses during fast-paced action sequences.

The Unity PlayerInput component supports inspector wiring and C# event callbacks for action map switching. It offers convenience by handling started, performed, and canceled callback phases, trading some flexibility for easier setup across different input devices.

Active device scheme detection allows you to adapt behavior for different Unity input methods. By identifying whether a keyboard, gamepad, or touch device is active, you can dynamically switch control schemes to match the player's current hardware.