Macro Limitations
-
- Posts: 183
- Location: Under a Boat by the River
Macro Limitations
Alright, I'm thinking of going for a total keybind revamp on my Rogue, mainly to conserve bar space and more importantly, macro space. Macros are rather limited in TBC.
So, I thought of macroing some stuff in a single bind, enabling the use of normal, focus -and- mouseover use of said ability. In a single bind.
For example, an ideal kick macro should (in the way I prioritize them) -->
a) Kick your mouseover target if mouseover target exists and if you press it WITH modifier.
b) Kick your focus target if focus target exists AND if a) doesn't apply and if you press it WITH the SAME modifier.
c) Kick your current target, if you press it WITHOUT modifier.
Just give me an example for Kick and I 'll build the rest on my own :)
In case you don't understand my description, just read the following, it's written in a more simple manner (maybe). In other words...
The macro should (for ease of explanation let's say Kick is is binded on "1" and modifier used is Shift) -->
Press "1" --> Kick current target.
Press "Shift+1" --> Kick Mouseover targer. If Mouseover target does not exist --> Kick Focus Target.
So, I thought of macroing some stuff in a single bind, enabling the use of normal, focus -and- mouseover use of said ability. In a single bind.
For example, an ideal kick macro should (in the way I prioritize them) -->
a) Kick your mouseover target if mouseover target exists and if you press it WITH modifier.
b) Kick your focus target if focus target exists AND if a) doesn't apply and if you press it WITH the SAME modifier.
c) Kick your current target, if you press it WITHOUT modifier.
Just give me an example for Kick and I 'll build the rest on my own :)
In case you don't understand my description, just read the following, it's written in a more simple manner (maybe). In other words...
The macro should (for ease of explanation let's say Kick is is binded on "1" and modifier used is Shift) -->
Press "1" --> Kick current target.
Press "Shift+1" --> Kick Mouseover targer. If Mouseover target does not exist --> Kick Focus Target.
Re: Macro Limitations
#showtooltip
/cast [mod:shift,@mouseover,exists]Kick
/cast [mod:shift,@focus]Kick;Kick;
Might work, cba to test.
/cast [mod:shift,@mouseover,exists]Kick
/cast [mod:shift,@focus]Kick;Kick;
Might work, cba to test.
Balls, Cube, Deems, Google [Bot]
-
- Posts: 183
- Location: Under a Boat by the River
Re: Macro Limitations
Well, "@" doesn't work in TBC so I'm replacing that with "target=" .
Also, the [mod:shift,@focus] Kick;Kick syntax should be equivalent to
[mod:shift,@focus] Kick
[nomod] Kick
if I'm correct? Not very experienced with multiple command macros.
Anyway, currently I've tested the following (and it doesn't work fully) -->
#showtooltip Kick(Rank 5)
/cast [mod:shift][target=mouseover][exist] Kick(Rank 5)
/cast [mod:shift][target=focus][exist] Kick(Rank 5)
/cast [nomod] Kick(Rank 5)
Also, the [mod:shift,@focus] Kick;Kick syntax should be equivalent to
[mod:shift,@focus] Kick
[nomod] Kick
if I'm correct? Not very experienced with multiple command macros.
Anyway, currently I've tested the following (and it doesn't work fully) -->
#showtooltip Kick(Rank 5)
/cast [mod:shift][target=mouseover][exist] Kick(Rank 5)
/cast [mod:shift][target=focus][exist] Kick(Rank 5)
/cast [nomod] Kick(Rank 5)
Re: Macro Limitations
#showtooltip
/cast [mod:shift,target=focus][mod:shift,target=mouseover,harm,exists][nomod] Kick;
remove line in bold if you don't want want modifier to be a requirement for the mouseover
/cast [mod:shift,target=focus][mod:shift,target=mouseover,harm,exists][nomod] Kick;
remove line in bold if you don't want want modifier to be a requirement for the mouseover
Last edited by Deems on 17 Mar 2013, 20:04, edited 3 times in total.
Google [Bot]
-
- Posts: 183
- Location: Under a Boat by the River
Re: Macro Limitations
Obviouslynot.jpeg
Doesn't work. Both your and Cube's have the same problem as mine :S
When pressed with modifier, macro actually does nothing.
The req's for mouseover kicking should be [target=mouseover] [exist] and [mod:shift] (or mod:alt, in my personal case)
Likewise, for focus kicking should be [target=focus] [exist] and [mod:shift] again.
and for normal kicks only req per se should be [nomod] or something.
So, mouseover should get prioritized over focus.
Doesn't work. Both your and Cube's have the same problem as mine :S
When pressed with modifier, macro actually does nothing.
The req's for mouseover kicking should be [target=mouseover] [exist] and [mod:shift] (or mod:alt, in my personal case)
Likewise, for focus kicking should be [target=focus] [exist] and [mod:shift] again.
and for normal kicks only req per se should be [nomod] or something.
So, mouseover should get prioritized over focus.
Last edited by QuantumVoid on 17 Mar 2013, 20:06, edited 1 time in total.
Re: Macro Limitations
works for me
make sure the shift modifier keybind is unbound (shift+1 in your case?)
make sure the shift modifier keybind is unbound (shift+1 in your case?)
Google [Bot]
-
- Posts: 183
- Location: Under a Boat by the River
Re: Macro Limitations
Hmm, might be that, haven't actually checked, thanks for the idea, brb testing =)
Edit 1: Removed any conflicting binds.
Same stuff.
Also, the macro seems to Kick mouseover or focus target if in range, even without modifier pressed.
Edit 2: K, brb testing Post #8
Edit 1: Removed any conflicting binds.
Same stuff.
Also, the macro seems to Kick mouseover or focus target if in range, even without modifier pressed.
Edit 2: K, brb testing Post #8
Last edited by QuantumVoid on 17 Mar 2013, 20:15, edited 1 time in total.
Re: Macro Limitations
#showtooltip
/cast [mod:shift,target=focus,mouseover,exists][target=mouseover,harm,exists][nomod] Kick;
try this instead
/cast [mod:shift,target=focus,mouseover,exists][target=mouseover,harm,exists][nomod] Kick;
try this instead
Google [Bot]
-
- Posts: 183
- Location: Under a Boat by the River
Re: Macro Limitations
Pasted it was you wrote it -->
Uknown Macro command: mouseover
Anyway the problem with previous ones (and this one ofc) is that it seems like that -->
If mouseover/focus exists, the macro doesnt give a flying fuck wether you have modifier held down or not.
Uknown Macro command: mouseover
Anyway the problem with previous ones (and this one ofc) is that it seems like that -->
If mouseover/focus exists, the macro doesnt give a flying fuck wether you have modifier held down or not.
Who is online
Users browsing this forum: No registered users and 1 guest