input-system

Multi-device input in Unity is handled by configuring action maps and PlayerInput components to support simultaneous devices. This integration generates C# classes that automatically detect and route inputs from gamepads, keyboards, and other connected devices.

Runtime rebinding in Unity is achieved by exposing the action map bindings through the PlayerInput component and invoking the rebind operation on specific actions. This allows players to customize their control schemes dynamically during gameplay.

Separating gameplay and UI input in Unity involves creating distinct action maps for each context within your input action asset. The generated C# classes allow you to enable or disable specific maps, ensuring UI navigation does not trigger gameplay actions.

Input buffering for character actions in Unity can be implemented by capturing input events from the generated action classes and storing them temporarily. The system processes the buffered inputs when the character's state allows, improving control responsiveness.

The Unity New Input System supports multiplayer by assigning unique PlayerInput components to each player instance. This mechanism routes specific device inputs to the correct player, allowing local multiplayer configurations with separate action maps.

Generating C# classes from Unity input action assets requires enabling the "Generate C# Class" option within the action asset editor. This creates a scriptable object wrapper, providing strongly typed access to your defined actions and bindings.