Y
Yothiel
Currently, binding an action to an already-used key will ask for confirmation, then unassign that key from all other actions upon confirmation.
This implementation prevents easy remapping of say, all "Q" actions, to another single key.
For context, alternate keyboard layouts are the norm in several European countries. For AZERTY keyboard users in France, that often means swapping their A/Q & W/Z key bindings for the many games centered around WASD movements.
But keyboard layouts aside, we should really be able to bind multiple actions to a single key when they're used in different contexts. Especially when it's what the default config does with Q or T.
Tested workarounds, for the knowledge base:
  • dispatching conflicting actions to different keys. Pro: simple. Con: user experience ranges from confusing when swapping vehicles, to madness-inducing when getting in an excavator)
  • switching keyboard layout to QWERTY in the OS. Pro: simple, widely-known solution for non-qwerty users. Con: makes typing text a pain, and does not cover a fully custom remapping usecase
  • manual edit inputManager.cfg. Pro: Can customize freely. Con: not user friendly