Bind quirk with shift keys

[Shenanigunner]

Again, in reworking my bindfile system, I discovered an ugly little quirk that I am 99% sure is a change from some prior implementation.

 

It used to be — and I am pretty sure I tested this thoroughly — that unassigned combination keys would do nothing (not trigger a base-key bind, that is), or would do so only with SHIFT. That is, if you have P bound to something, CTRL-P, ALT-P and sometimes SHIFT-P would do nothing if undefined. (Undefined = empty bind string == ' CTRL+P "" ')

 

Now, any undefined shift key combination will actuate the base bind. Unless you have bind assignments on the shift keys, or specifically bind them to "nop", the shift keys will actuate whatever you have bound to the unshifted key. That is, if you have P bound to "em poopface" then CTRL- ALT- and SHIFT-P will all poop, too.

 

This is distressing if you use any complex combination of binds and relay on, say, CTRL-O to do something important and hit CTRL-P instead; it will be as if you'd hit P directly.

 

No really good solution, as to nop out all four keys for a whole bindset makes the file far too large to load, in line count if not bytes. I guess careful practice would be to nop out selected combinations that might have a disastrous effect from an adjacent key-miss.

 

Btu then, I'd like to have a running conversation with the Devs about the quirks of the bind parser anyway...

[macskull]

Is this behavior unique to bindfiles? I'm testing this ingame right now. I use a Logitech G600 and my default bind scheme is binding the side buttons to "shift+numpad#," and just pressing the numpad numbers isn't doing anything. Pressing shift plus the numpad number works as expected. I manually enter my binds vice using a bindfile.

[Shenanigunner]

Other way around. If you have NUMPAD3 bound to "em dance3" then a null SHIFT- CTRL- or ALT- will also activate it. Downward to the base key, not upward to the shifts.