Come wotlk, I plan to quad box it up. One thing that I am trying to figure out is how can I send commands to one window but not the other 2. So that my two dps chars can attack, but my two healers dont.
Come wotlk, I plan to quad box it up. One thing that I am trying to figure out is how can I send commands to one window but not the other 2. So that my two dps chars can attack, but my two healers dont.
Conditional macros ftw
Example - 2 mages, 2 priests
(Mages)
#showtooltip Frostbolt
/assist main
/cast Frostbolt
(Priests)
#showtooltip Heal
/cast [modifier=alt] [target=dps1] Heal
/cast [modifier=ctrl] [target=dps2] Heal
Just make sure that if you are binding it to a number key that that key is not in use already, or just disable the default key binding
I think that macro is right, but just test it and check macro wiki![]()
Thaurissian (Oceanic PvP - Alliance)
- Cybelor (Hunter)
- Lock/Mage (Slagathör/Pïmples)
- Pally/Shaman (Krossfari/Cätäclysmïc)
- Warrior/Priest (Façepalm/Phäge)
First I love keyclone, its a great runtime.
What the above assumes is that you understand that keyclone is "broadcast to all" by default. So when you login you press 'B' and all your characters open their bags for example. It then wants you to put all your accounts into a keymap state that is cryptic if you wanted to play any, except the main character first person.
So this means that if you want [1] to be frost bolt on the mage, you need to remove the [1] binding from the other characters. Then if you want [Ctrl-1] to be flashheal on the healer you need to remove [Ctrl-1] binding from the mage. Now you get to play wow in "vulcan neck pinch" mode.
Unraveling this default nature of keyclone isn't very documented outside of a few forum posts (and it seems in those posts they might have unconventional keybinding methods). Its a great runtime maximizer, keyevent generator and multiplexer, but configuration of keymaps / hotstrings it suffers from at the moment. Again more so from documentation that anything else.
Sample hotstring setups similar to the maximizer setups would likely fix this, though keyclone's configuration separation is an issue for making this work since whitelists and what not are independent of the keymap files.
Connect With Us