Changing key bindings
Okay so a lot of scripts require key bindings for them to work. However since they are mostly bound to alphabet or number keys, so it might cause problems as I installed plenty of them and it could interfere with each other. I tried binding to keys like [ ] \ ; ' , . / - = but it won't work, so how can I bind it to those keys? Or, it would be better if I could press Ctrl before pressing the required key, so how to do that as well?
@FinnMcMissile I don't think you put those in the config if that is what your are doing for example if I wanted the numpad addition I would do "Add"
@NotCrunchyTaco Well umm, different scripts have different ways of binding keys, some require virtual-key codes, some require key code values and some require you to just press the key itself. My issue is with the third one. This is an example of it:
So I can't simply just put [ or ] or ; and etc. behind it as it won't work, tried typing virtual-key code and key code value, didn't work as well, so I am hoping to find a way to bind to those keys.
@FinnMcMissile some of those keys have names that may not seem obvious. You can find them here: https://msdn.microsoft.com/en-us/library/system.windows.forms.keys(v=vs.110).aspx
I'm not sure but I think [ would be OemOpenBrackets
@stillhere I tried, it does seem to be working, but not for all keys, e.g. OemBackslash, when I tried that nothing happened, but it works fine with Oemplus and Oemcomma (haven't try out the other ones yet) Still, is it possible to make it only work when pressing CTRL beforehand? Cuz my another mod (passenger mod) seem to only work with letters...
@FinnMcMissile the thing about some scripts is that they only look for one Key value, so the only way to have two or more keys is if you edit the source, unfortunately. Maybe it's possible to use SHIFT and a key, for example the question mark (OemQuestion), though I doubt it would work.
@stillhere Unfortunately, even the SHIFT key has to be detected like this:
if (e.KeyCode == keyActivationKey && e.Modifiers == Keys.Shift)
So you're right, you would need to edit the source to add that ability.
Never mind then, I guess knowing how to bind to Oem keys and all that is good enough, thanks!