Duke3D: inconsistency with "bind" console command and the mouse controls
It appears that using the
bind console command to set up mouse controls assigns a hidden gamefunc to the mouse button that does not replace the binds in the mouse config menu, but instead takes precedence over them.
For instance, go to the mouse config and set the "Left" action to "Move Forward". Then go ingame, type
bind mouse1 gamefunc_fire in the console, then click the left mouse button. You will notice that you now have primary fire assigned to the left mouse button, but if you visit the mouse config, the menu will still state that it is assigned to "Move Forward".
unbind mouse1 removes the
gamefunc_fire keybind, but leaves the "Move Forward" keybind active.
This is potentially a leftover from older eduke32 builds, as the "mouse1" bind is actually written into "settings.cfg" if defined this way, while the mouse bindings seen in the menu are written to "eduke32.cfg".