There seems to be a major bug where, if you swap two default keybinds, both keys will do whatever their default action was instead of each one doing what their new binding should.
For example, I have "Q" bound to a common event by default, and "Control" is bound to the Control key (to trigger things from other plugins).
If I rebind "Q" to another key such as "G", that works fine. Q stops running the common event, and G instead runs that event.
If I then rebind "Control" to the now-vacant "Q", that also works fine. G still runs the common event, and pressing "Q" now does what "Control" did previously.
However, when I then rebind the common event that was originally bound to "Q" to "Control" (so now, Q and Control's original bindings are swapped), pressing both Q and Control will trigger the common event, even though Q is not supposed to, as the control function is now bound to it, and Q is bound to the "control" function, not the common event.
This also happens if I just directly swap Q and Control around immediately, or any other 2 keys that have a default binding. It seems that any 2 keys with a default binding cause conflicts when swapped with each other, as if the plugin is trying to run both the default command and the current one.
This causes all sorts of issues since my game has a lot of default keybinds, so changing pretty much anything causes these conflicts.