This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Classic Theme
Thottbot Theme
TOTT
Post Reply
Return to board index
Post by
RedwoodElf
because he wants a 'force' option. In your situation I could be targeting a hostile mob who has a tank targeted, but I want to toss my tricks on a rogue who is not my focus. Your macro makes this impossible, or at least impossible without manually targeting the rogue (ie. it won't work if you want to cast it onto a person's raid frame).
I'm pretty sure putting before allows you to cast it on someone who isn't your focus, by targetting them, or targetting a mob that is targetting them...so how does that make it impossible?
I'll paint you a picture :P
Player = Rogue 1
Target = Boss
TargetTarget = Tank
Focus = Rogue 2
Tank has a sizable threat lead, thus the optimal usage of tricks is on Rogue 2. This is all well and fine for your macro, but midway through the fight Rogue 2 dies. Rogue 3 is still alive, but was not initially your TotT target. With your macro, the ONLY way to tricks him now is to physically target him, thus you lose your target are on the boss.
If you have a failsafe (ie. a conditional that casts on mouseover or forces the target cursor), you can use that to target Rogue 3 from your raid frame while never dropping your target.
I fail to see any mouseover conditional in Squirldude's macro, however, so how is this relevant?
Post by
Wanderingfox
because his macro has what is essentially a in the first cast.
If the /cast tricks of the trade fails (ie. you can't cast tricks on your target) the default behavior for the UI is to provide you with the selection cursor. This is the same thing that happens when you try to cast a buff with no target. That means if he has a hostile target selected and tries to right click his macro (or the optimized one I provided earlier) it will give him a selection cursor while keeping his hostile target.
If you tried this with Wildthorn's macro, the conditional would fail, but due to an oddity in the macro engine, since there's another part of the cast sequence, the macro holds off on providing the targeting cursor.
If you tried this with your macro, you'd see a similar issue. The macro would simply fail out without providing you a way to manually target it.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.