Log in

View Full Version : macro modifier not being passed through keyclone



khabel
09-30-2008, 03:38 AM
This is the macro on my slave

#showtooltip regrowth
/cast [modifier:ctrl,target=soland] [target=evissica]regrowth

It works fine if I manually use it on my slave but for some reason the modifier is not being passed through keyclone when I use it on my main, ctrl is not on my do-not-pass list

Faradyn
09-30-2008, 03:02 PM
i had a similar problem, it tured out the key "A" was on the do not pass list. So i canged it to say f1 and it worked fine.

elsegundo
09-30-2008, 03:10 PM
try using rctrl or lctrl

Elgert
10-31-2008, 03:00 PM
Did you ever find a solution to this problem? Got the same issue here ;( (tried lctrl and rctrl)

Tynk
10-31-2008, 03:39 PM
two things.
1: The explicit key will ensure if a is on your dnp but ctrl-a is not that keyclone still passes ctrl-a
2: WoW functions odd with key passing. if you are using ctrl-a passed to wow, make sure that a is bound to something, or it will just assume a.

elsegundo
10-31-2008, 04:25 PM
though it might not be the case, i always put my targets first with the logic being, target soland IF mod is pressed.
/cast [target=soland, mod:ctrl] [target=evissica]regrowth



or you can do this:

/cast [target=evissica, nomod] [target=soland] regrowth

does the same thing.


one other thing... are yo using macaroon?

Kaynin
10-31-2008, 06:11 PM
It's most likely the key you bound this macro to, lets say it's for example 1, is still being bound in your ingame wow keybindings as ctr-1.

So it's not that keyclone isn't passing it, but probably that WoW doesn't recognize the keybinding as the macro. Double check your keybinding lists and make sure the button you bound it to doesn't already have a ctrl-button bound somewhere else.

elsegundo
10-31-2008, 08:03 PM
what exactly is ctrl+1? isnt that petactionbar button 1?

Elgert
11-01-2008, 08:17 AM
DOH! I was using "4" as my heal-the-tank button (ctrl=renew, alt=PW:shield, normal=lesser heal) and was sure that the ctrl+4 keybind was onbound. It turned out that I had unbound ctrl+2 ...
Now I just need to setup a sheep macro, then Ragefire Chasm will be punished!


Btw - thanks for all the answers - makes me believe that I can actually get this thing going :-)

moosejaw
11-02-2008, 02:34 AM
I have to go through the binding list and unbind all those extra action bar binds blizz puts in by default. Now that those lists are kept server side (for blizz bindings) I'll to repeat this on every character since I can't duplicate the bindings file anymore. What a pain in the a$$. I do keep a few bindings in place: B to open all bags, mouse zooms, most of the move commands etc. But I remove most of those bindings.

Save yourself some trouble later and just unbind all that crap blizz put in. You know you won't need those extra action bar binds. Most of us use a bar mod anyway and those binds won't be applicable. Just keep the things you will really need.