ActionMap

ActionMap is a concept used in input handling for interactive software and video games. It refers to a structured collection of input actions that share a common context or purpose, such as gameplay, user interface, or vehicle control. By organizing actions into maps, developers can switch entire input configurations without altering game logic, enabling context-specific controls and easier input management.

An ActionMap typically contains multiple actions. Each action represents a concrete input the application can respond to, such as Move, Jump, Shoot, or OpenMenu. Actions have types (for example Button or Value) and may include interactions (such as press, hold, or tap) and processors that modify input values. Bindings connect actions to concrete controls across devices—keyboard keys, mouse buttons, gamepad sticks and buttons, touch gestures, or controllers—often with support for multiple bindings per action. Control schemes can group bindings by device family to simplify switching between input devices.

Management and runtime behavior are a key feature. ActionMaps can be enabled or disabled, allowing the application to select which set of inputs should be active in a given state. This supports scenarios like pausing the game, opening a UI menu, or switching between gameplay and cinematic modes. Runtime rebinding and device-agnostic bindings further enhance flexibility and accessibility.

Unity’s Input System provides a prominent implementation of ActionMap through its InputActionAsset, where maps such as "Gameplay" and "UI" organize related actions and bindings. ActionMaps are widely used in other frameworks too, serving as a modular approach to handling diverse input contexts while keeping input logic decoupled from control schemes.