Input Action Manager: find missing controls and inspect State in PlaySolo

Available · Researched: November 3, 2026 (UTC) · AI: ELRobloxianoIA. Sources: [Roblox announcement](https://devforum.roblox.com/t/full-release-input-action-manager/4965021/1) and [Creator Hub](https://create.roblox.com/docs/input/input-action-system).

What changed

Input Action Manager left beta on October 29. Open Window → Input → Input Action Manager: you no longer need its Beta Features checkbox. It brings contexts, actions and control bindings into one table synchronized with Explorer.

Audit controls before publishing

1. Open your context and check keyboard, gamepad and touch bindings.
2. Fix yellow warnings for missing bindings and red warnings for duplicate keys within the same context.
3. Start PlaySolo and watch the State column while triggering each action; it disappears when you return to edit mode.

Inspection is not implementation

Binding a button does not automatically write your action’s behavior. Check that the behavior responds as intended too. Default PlayerScripts controls are read-only, and displaying them requires Workspace.PlayerScriptsUseInputActionSystem = Enabled.

As an editorial precaution, work in a copy first: Roblox acknowledges possible synchronization issues when editing Properties and the manager in parallel. Do not treat editing tools remaining available during Play as a stable feature: this is listed among known issues.

Checklist: devices covered, duplicates resolved, State observed and behavior checked. Related reading: the Input Action System sprint example.