test content
Logo
What is the Arc Client?
Install Arc
Keybinds are messed up something horrible...
heero139
Member Posts: 125 Arc User
When I logged in after Season 8's patch, I noticed some of the UI functions were showing key binds on them (need/greed/pass, for instance) where I had previously removed the key bind.
Loading my old keybind files did not fix it, so I figured I'd reset the entire key bind menu, and rebuild everything again. Wouldn't be the first time something changed that made UI display of key binds break for me.
Now, my UI is showing me some kind of frankenstein combination of my key binds and default ones... somehow it seems to think I have the same key bound to multiple functions.
Fortunately, as far as I can tell, the key binds when activated actually function correctly, so the glitch seems to be limited to the UI display of key binds in the key binds menu and the UI tray/buttons which display key binds on them.
Also, if I /bind_save_file now, it doesn't show key aliases in the file, it shows a the key codes like this:
0xc8 "(null)"
0xd0 "(null)"
0xcb "(null)"
0xcd "(null)"
0x2d "(null)"
0x1b "+aim"
0xef "++autoforward"
0xf9 "(null)"
0x5d "(null)"
0xc7 "(null)"
0xc9 "(null)"
0xd1 "(null)"
0xcf "(null)"
0x4a "AdjustCamDistance -1"
0x4e "AdjustCamDistance 1"
0x30 "(null)"
0x61+0x60 "(null)"
0x5f+0x5e "(null)"
0x4f "(null)"
0x50 "(null)"
0x51 "(null)"
0x4b "(null)"
0x4c "(null)"
0x4d "(null)"
0x47 "(null)"
0x48 "(null)"
0x49 "(null)"
(etc.)
I think this might mean that the problem is somehow related to the change made to make numpad enter and enter register as two separate keys, and the UI hasn't caught up to those changes yet.
small edit:
kind of weird, only a few key binds are displayed wrong on a character until I make a change to the keybinds then change maps or relog, once I do that, then all the keybinds start displaying incorrectly.
Loading my old keybind files did not fix it, so I figured I'd reset the entire key bind menu, and rebuild everything again. Wouldn't be the first time something changed that made UI display of key binds break for me.
Now, my UI is showing me some kind of frankenstein combination of my key binds and default ones... somehow it seems to think I have the same key bound to multiple functions.
Fortunately, as far as I can tell, the key binds when activated actually function correctly, so the glitch seems to be limited to the UI display of key binds in the key binds menu and the UI tray/buttons which display key binds on them.
Also, if I /bind_save_file now, it doesn't show key aliases in the file, it shows a the key codes like this:
0xc8 "(null)"
0xd0 "(null)"
0xcb "(null)"
0xcd "(null)"
0x2d "(null)"
0x1b "+aim"
0xef "++autoforward"
0xf9 "(null)"
0x5d "(null)"
0xc7 "(null)"
0xc9 "(null)"
0xd1 "(null)"
0xcf "(null)"
0x4a "AdjustCamDistance -1"
0x4e "AdjustCamDistance 1"
0x30 "(null)"
0x61+0x60 "(null)"
0x5f+0x5e "(null)"
0x4f "(null)"
0x50 "(null)"
0x51 "(null)"
0x4b "(null)"
0x4c "(null)"
0x4d "(null)"
0x47 "(null)"
0x48 "(null)"
0x49 "(null)"
(etc.)
I think this might mean that the problem is somehow related to the change made to make numpad enter and enter register as two separate keys, and the UI hasn't caught up to those changes yet.
small edit:
kind of weird, only a few key binds are displayed wrong on a character until I make a change to the keybinds then change maps or relog, once I do that, then all the keybinds start displaying incorrectly.
Zekkie@h33r0yuy
0