Why does my input action fire callbacks 3 times after toggling enable?

Each OnEnable subscribes again. C# events stack subscriptions. Unsubscribe in OnDisable so the count stays at 1 across enable cycles.

Use generated C# class?

InputActionAsset's generated class auto-creates a single instance — same problem. Track subscriptions yourself or use += in Awake / -= in OnDestroy for one-time.

PlayerInput component alternative?

PlayerInput in Send Messages mode dispatches to MonoBehaviour methods by name; auto-rebound on enable. No subscription stacking.

Fix: Input Action Callbacks Stack After Re-Enable

Quick answer: Subscribe in OnEnable; unsubscribe (-=) in OnDisable. Stacks otherwise.

Player toggles between menu and game. Each toggle re-enables the action. Jump fires twice, then thrice, then four times.

The Fix

PlayerActions _actions;

void Awake() { _actions = new PlayerActions(); }

void OnEnable() {
    _actions.Player.Enable();
    _actions.Player.Jump.performed += OnJump;
}

void OnDisable() {
    _actions.Player.Jump.performed -= OnJump;
    _actions.Player.Disable();
}

void OnDestroy() { _actions.Dispose(); }

Pair every += with -=. Dispose at end. C# event handler list grows otherwise.

Verifying

Toggle scenes 5 times. Jump fires once per press. Without unsubscribe: 5 fires per press.

“Subscribe pair. Unsubscribe pair. One callback.”

Related Issues

For Input composite, see composite. For control scheme, see scheme.

Pair subscribes. One callback.