Among us, most have written a custom set of key bindings. Though I have noticed that many sets become quite polluted if left unrevised forever. Consider this thread an invitation to revision, and to discuss the various pitfalls of key bindings.I have composed a clean, basic set of keybinds to optimize predictability, and to encourage uniformity. Consider the following classes. If they are used in correct order, then you can program your team easily and precisely.

Suggestions- Selections complement demands, not vice versa.- Use angular brackets "<>" to indicate a common term.- Finish with two periods to assert an upcoming message.- Start with two periods to complement a previous message.- Use underlines for extra emphasis, not to add style.- Avoid abundent status notes like "Equiping handcuffs".- "Gold" originates as a singleplayer term, it is slightly more conventional to use "Element" instead.

Exceptions- "Recover formation" is excepted as a status note instead of demand to avoid leadership-interference.- Spatial and temporal references (short, mid, far, OC) are excepted as demands instead of selections for continuity.