What I meant about "colliding" is that if you bind say... button "1" to a button on your new possess bar, it'll UN-bind the one that currently exists. So, to get around that, you need to create a paged bar with your currently-in-use "1" button and a possess state with another keybinding of "1". That way it won't collide and un-bind.Ok I am very confused now. When I did the check posses state thing it started a new bar. From that point I was lost. I use the keyboard buttons 2 & 3 for my two dk macaroon buttons. The default buttons for vehicles and stuff are like 1-5. When you are talking about them coliding you mean I am using the same keys for my dps macaroon macro buttons right? I am very new to macaroon so there is a ton of stuff I dont know about.
So, since you use buttons 2 & 3 for your DK, you can use buttons 1, 3, 4, 5, 6, 7, 8, 9 for your "posess" bindings no problem (just create a new bar and give it a "possess" state).
If you ALREADY have buttons bound to 1, 3, 4, 5, 6, 7, 8, 9 and you don't want to create new bindings for your "possess" state, then you'll have to use a paged bar (that is, give it buttons on its "normal" stance and give it buttons on its "possess" stance so that the keybindings don't overwrite each other -- the keybindings can be the same on each page of the bar, it doesn't matter, since they won't "collide").
Whew, hopefully I made more sense that time. It's been a long workday, sorry. >.<
Connect With Us