Ability to inspect each individual action and *all* their relative keybindings within the keybindings menu.

[AdamALittle]

Is your feature request related to a problem? Please describe.

The keybindings menu is extremely confusing, and generally does not work intuitively. Individual actions on the keybindings menu are only capable of showing one binding state at a time, as well as being un-organized/un-grouped, and unclear of when the action is able to be executed when it's associated keypress occurs.

Claiming an action is "global" communicates that pressing it's associated key at any time and in any context will execute the action. The only globally applicable actions I can think of are UI navigation, quit out of UI element/go back, confirm/continue/interact with selected UI element.

Solution you would like.

A: The keybindings menu should function similar to most other UI panels in the game. Pressing UDLR or Numpad keys should navigate a selector through the various actions that can be bound.

B: Pressing enter on any given action should display a sub-window that gives far more control and information of the context the action can be performed in, it's default keybinding, and the currently active keybinding(s) attached to this action.

C: Additionally, when the Keybindings menu is opened, the current context that you are viewing the keys for should be displayed.

Describe alternatives you have considered.

Just adding the ability to view ALL the current keybindings for an action would be nice too. When there's a global keybinding active, but the action is still unbound locally, display what the global keybinding is!

Additional context

Hovering selector over an action example:

Pressing enter with that action selected could bring up something like this:

Then, pressing Esc would navigate back out of that menu to the first image.

Some notion of what context the user is currently in would also be nice:

(Sorry for scuffed images, just trying to get a concept across)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.