In a workspace app, a button might affect a different context than the user's current view. The manager accepts a contextOverlay . Example: "Approve as Admin" button runs with admin permissions even if the current user is in a read-only view.

When a menu opens, the manager disables the Gameplay context. Suddenly, the inputs that move the character are ignored, and the inputs for the menu take precedence, eliminating input conflicts entirely.

While a "Version 1" approach might simply check if a key is down, represents a paradigm shift: moving from simple detection to sophisticated state management, abstraction, and context awareness.

Button Manager v2 is not just a script; it is a dedicated subsystem. It treats inputs not as fleeting events, but as persistent objects with lifecycles. The core philosophy of v2 is . The game logic should never ask "Is the Space bar down?" It should ask "Is the Jump button active?"