1. Open "Configure Keybindings" UI.
2. Locate the action you want to change.
3. Click the action's left column so it changes to "Set new keybind".
4. Press the key/button you want to bind.
5. Click Apply.
6. If the action has an existing binding in the right column, the new binding disappears from the action's left column and is combined with the existing binding in the action's right column as a chorded binding.
7. Delete the action's right-column binding.
8. Click the action's left column.
9. Press the key/button you want to bind.
10. Click Apply.
11. The new binding disappears from the action's left column.
12. Repeat steps 8-10.
13. Finally, the bind is created properly.

Here's roughly what currently happens:

• If the right column has a bound key or button, a new key or button that you attempt to bind in the left column will be removed from the left column and combined with the right column's existing binding as a chorded bind.
• If the right column is empty, a new key or button that you attempt to bind in the left column will disappear from the left column the first time you click Apply.
• Repeating the bind-Apply sequence will work the second time.
• If you close the options, the state of the code is reset. So many users go through this sequence several times before they figure it out, or give up altogether:

1. Bind a key.
2. Click Apply.
3. Exit options without realizing that the new bind disappeared after clicking Apply.
4. Test bind in-game and realize that nothing happens.
5. Open options again and repeat sequence.

Please note: this broken behavior is immediately obvious upon the most simple attempt to modify keybindings. The most cursory test of the keybindings UI would have revealed it to the developer before release.