Currently the keybindings file (keys.cfg) is not loaded by the input handler, only saved. The keys file is executed as a script later by the Command Interpreter. The keybinding saving assumes that the configuration was set up correctly and overwrites the old configuration file. Recently a workaround was added that removes the configuration file if no keybinding was saved but it is not the best solution.

Prolems found so far:

1. The keys configuration loaded too late. It is possible that the program ends - and tries to save the key configuration - before it happens.

2. The Command buffer has an upper limit in size. By adding keybindings or tooltips - keys.cfg can contain tooltips for bindings too -, keys.cfg can exceed this limit, the Command Interpreter will truncate the script to its size limit and execute a half/broken configuration.

3. There is no check for a broken key configuration. We should check at least for the most basic bindings (like "+leftmouse") to ensure that the player can navigate in the UI.

4. The saving is immediate, no backups created. On write error or 0 saved bindings the function removes the script - reseting the bindings to the defaults, losing any modifications made by the user. It also doesn't check for the most basic bindings to exists.