input-system-new

To decouple input handling in Unity, you can use a ScriptableObject-based input reader that exposes events for moves and actions, separating device detection from gameplay code. This allows multi-device support.

The Unity New Input System handles multiple devices by routing input through a unified ScriptableObject event surface. This allows seamless switching between keyboard, gamepad, and touch inputs without altering gameplay logic.

Set up UI navigation and gameplay input switching by mapping action events through an InputReader ScriptableObject. This enables seamless switching between gameplay and UI input maps, allowing multi-device navigation.

Yes, you can implement input rebinding for gamepad and keyboard without rewriting game logic by using a decoupled ScriptableObject input reader. This approach exposes rebindable events, keeping control mapping separate.

Multiplayer input readiness is supported when using ScriptableObject events in Unity, as the decoupled input reader architecture allows multiple devices to route events independently, preparing the system for multiplayer.

A limitation of using ScriptableObject events for input switching in Unity is that ScriptableObjects are assets, meaning event state might persist across play sessions if not properly reset, requiring careful test scaffolding.