Modifier Key for Hot bar binding Help

[Symmone]

So the standard modifier key for hotbar 2 is CTRL.
I would like to know how to add/remote or change the modifier key!

Thank you in advance!!

Sym

[Kitfox]

System → Keybind → Hotbar

[xJimmehx]

Exactly the post above^ or type "/keybind" then look through the tabs for different types of bindings til you find what you want.

[Symmone]

I am familiar and comfortable with the keybind section and where to find what I need. However when I get to Hotbar2 (which has CTRL as the native modifier) I cant seem to change it.

For instance, I click on the space I want to edit, then I press the key combination I want (such as SHIFT and 1 at the same time instead of the native CTRL+1) but it never works. It gives me an error that 1 is already designated on hotbar 1.

Am I doing that wrong? How do I get the SHIFT and 1 button to go together? It never seems to recognize Im pressing SHIFT and just recognizes 1 and then tells me I have that bound elsewhere already.

So my question is literally, how do I do that? Not where to find the options.

[EveK]

Sounds like you're doing it correctly. The question then becomes why it's reading you pressing Shift-1 as you just pressing 1.

Also, it's worth noting that you technically aren't describing the modifier key process correctly. You don't press them at the same time. You press the Shift key first. While you're holding the Shift key, you then tap the 1 key. And then you can release the Shift key. PROBABLY what you're doing anyway, but just in case this is the issue... =)

[Peacecow]

Ah Ah I think the prob you got is that when the hotbars are on default, shift+# will change your hotbar1 to hotbar#.
So that when you wanted to keybind shift+1 to hotbar2, it said that hotbar1 already has that keybind.
At least that's what happened to me :P

edit: oops never mind. ignore me. I misread orz

[Symmone]

I figured it out! Thank you all!

I was getting the error for swapping between hotbars.

[EveK]

Glad you got it. In hindsight, I should have realized that the message that it was bound ON hotbar one sounded wrong since it tells you what function it's bound to, not on what hotbar. =)