# InputSystem: Conflict detected: Multiple actions bound to same control 'Keyboard/space'

- **ID:** `unity/input-system-duplicate-binding`
- **Domain:** unity
- **Category:** config_error
- **Verification:** ai_generated
- **Fix Rate:** 88%

## Root Cause

Multiple input actions in the same Input Action Asset are bound to the same physical control, causing ambiguous input handling.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Unity 2022.3 | active | — | — |
| Unity 2023.1 | active | — | — |
| Input System 1.5.0 | active | — | — |
| Input System 1.7.0 | active | — | — |

## Workarounds

1. **In the Input Actions window, select the action with the duplicate binding, expand its bindings, and delete the one that maps to 'Keyboard/space' or change its path to a different key.** (90% success)
   ```
   In the Input Actions window, select the action with the duplicate binding, expand its bindings, and delete the one that maps to 'Keyboard/space' or change its path to a different key.
   ```
2. **Select the conflicting binding in the Input Actions editor, click 'Add Interaction' and choose 'Hold' (set hold time to 0.5s). This allows the same key to trigger different actions based on press duration.** (85% success)
   ```
   Select the conflicting binding in the Input Actions editor, click 'Add Interaction' and choose 'Hold' (set hold time to 0.5s). This allows the same key to trigger different actions based on press duration.
   ```
3. **In the Input Actions editor, create a new action map (e.g., 'Menu'), move the conflicting action there, and in code enable only one map at a time: 'playerInput.actions.FindActionMap("Gameplay").Enable(); playerInput.actions.FindActionMap("Menu").Disable();'** (92% success)
   ```
   In the Input Actions editor, create a new action map (e.g., 'Menu'), move the conflicting action there, and in code enable only one map at a time: 'playerInput.actions.FindActionMap("Gameplay").Enable(); playerInput.actions.FindActionMap("Menu").Disable();'
   ```

## Dead Ends

- **Deleting the entire Input Action Asset and recreating it from scratch.** — The conflict arises from binding assignments, not asset corruption; recreating the asset without adjusting bindings reproduces the same conflict. (90% fail)
- **Setting InputSystem.settings.ignoreConflictResolution = true in code or project settings.** — This suppresses the warning but does not resolve the underlying ambiguity, potentially causing unpredictable input behavior at runtime. (70% fail)
- **Renaming the actions to different names without changing bindings.** — Conflicts are based on control paths, not action names; renaming does not alter which controls are bound. (95% fail)