Azeroth paid a terrible price to end the apocalyptic march of the Legion's crusade-but even as the world's wounds are tended, it is the shattered trust between the Alliance and Horde that may prove hardest to mend.

• World Of Warcraft Target Macro

• A world where you’re the hero of your own epic story and new adventures await you around every corner. To begin or continue your journey, all you need is a subscription. From the shattered world of Outland to the frozen wastes of Northrend, you’ll encounter deadly dragons, descend into ancient dungeons, forge unbreakable bonds of friendship, and maybe even discover the perfect fishing hole.
• @target,help will cast Rejuvenation on your target if they're friendly, @target,harm will cast Moonfire on your target if it's an enemy. As with modifier key macros, #showtooltip will show the icon and tooltip of whichever spell meets the current conditions. In this case, Rejuvenation if your target is friendly and Moonfire if it's an enemy.

Hello all, I'd like to have a discussion and see all the different angles on this subject. Some of you may know they recently added a few new macro commands, /cast @Player and /cast @Cursor will cast target spells at your character/cursor.

I.e: Unholy Death Knights can now use that command to drop Death and Decay as if it were consecrate. But they left out /cast @Target. I can totally understand how it would have implications that impact high rated pvp more than anything, but is the end result really that severe? Good players can already cast whatever they want wherever they want. However, I'd like to come at you from the controller community.

World Of Warcraft Target Macro

Yes, we made the decision to play with a controller, some of us (much like myself) don't have much of a choice due to an injury. While we can do most everything keyboard and mouse players can do, anything pertaining to targeting or using the cursor is more difficult.

/cast @player helped us beyond measure with certain spells and abilities, mainly death knights and shamans and the like, but now the ranged is left out and still has to work harder to drop their ground aoes. What I was hoping to achieve here is discourse on the topic and find out through a community wide discussion if adding a /cast @Target command would be too strong to consider adding. I can certainly see it making a few pvp aspects more achievable, but is that really a bad thing, and if so, is it bad enough to outweigh the good it can do for the pve side of things and the controller community(we may be small compared to the entirety of the playerbase, but we're definitely here unless/until blizzard stomps us out, I genuinely hope they don't.). 11:29 AMPosted by The only thing new was @cursor conditional - @player has existed for a long long time now (perhaps since the beginning). Coincidently, the default behavior of any spell is to cast it, believe it or not, ON YOUR TARGET and this has existed since the beginning too.

To get this default behavior in your macro include a blank conditional. For example: #showtooltip /use @mouseover,harmSpell It gets even simpler if you have no other conditions to test for.

Then its simply: #showtooltip /use Spell That does not work for spells that require you to place your target, which is that the entire request for '@target' is for. 11:46 AMPosted by That does not work for spells that require you to place your target, which is that the entire request for '@target' is for.Which is what the new @cursor took care of #showtooltip /use @cursorSpell With Ground Target.and if you simply want the default behavior or casting a spell that is a direct target (i.e.

At a person) use the @mouseover. It literally can't get much simpler than that as this mouse over works on ALL frames.

Raid frames, boss frames, pvp frames etc. #showtooltip /use @mouseover,harm (change 'harm' to 'help' if its a heal or other friendly spell) The @target IS THE DEFAULT BEHAVIOR OF ANY SPELL. If you have multiple conditions use a blank conditional to get this DEFAULT BEHAVIOR that has existed since the beginning of macro's. 11:46 AMPosted by That does not work for spells that require you to place your target, which is that the entire request for '@target' is for.Which is what the new @cursor took care of #showtooltip /use @cursorSpell With Ground Target.and if you simply want the default behavior or casting a spell that is a direct target (i.e.

At a person) use the @mouseover. It literally can't get much simpler than that as this mouse over works on ALL frames. Raid frames, boss frames, pvp frames etc. #showtooltip /use @mouseover,harm (change 'harm' to 'help' if its a heal or other friendly spell) Yes, @cursor works, and so does @player. But, for example, take my Fury of Elune. High damage, targetted AOE. @player will immediately drop it on me, no targeting circle required.

Not useful unless I am in melee. @cursor will bring up my targeting circle, which is no different that how it works when not in a macro.

How often is my cursor exactly where I want the spell to be, when I cast it? Not very often.

@target would drop it on my current target, no targeting circle required. 12:01 PMPosted by @player will immediately drop it on me, no targeting circle required. Not useful unless I am in melee. Yes, which makes the macro conditional highly situational for ranged dps. Melee can utilize it very well. As I said in my OP, /cast @Player Death and Decay will now drop DnD as if it were consecration. No targeting marker needed.

It just drops it. Same with totems and any ground-based aoe spell. The desire for an @target conditional is for the ranged classes.

For a warlock /cast @target Rain of Fire to drop RoF on the enemy in 1 button click. And to reiterate, I'm coming from the controller community. Our control over our cursor is far more limited than using a mouse.