Sugar Cookie
All keyboard and mouse interactions should be customizable in a new interface window and saved to the cloud, as well as provide the option to save and load to/from a file. All menu options should be available for key binding. And all current keybinds should be modifiable, including things like control and alt/option used for camera manipulation.
Take inspiration from other software and games that allow for extensive interface customization. Make it easy to identify conflicts. Combine it with gesture key definitions so they are listed and counted in the same interface window.
Bonus Points:
Allow some key binds to be associated with values that have toggles and ranges, as in the Quick Preferences menu. These binds can toggle between two preset values or, if held, change fluidly with the movement of the mouse.
As an example, if shift-alt-H were bound to Hover Height, two values can be set in the bind configuration interface and each click of shift-alt-H will swap between the two values. Alternatively, holding down shift-alt-H and moving the mouse horizontally will fade in a scroll bar in the middle of the screen, allowing the user to custom-set a new value. Releasing the key bind hides the scroll bar and locks in the new chosen value.
If the function is just a toggle, like Show Name Tags, then the two values are True and False by default and no scrollbar will appear. However, it may be desirable to display the new value briefly on the screen in its place.
If the function has a list of N possible states -- like Sunrise, Noon, Sunset, and Midnight -- then the scrollbar interface could still be used, but with discrete steps and the displayed value words instead of a floating point ranged value.
·