Apr 18th 2011 10:58PM ...That was meant to be in reply to the first post which was debating mouseover vs. target healing, but w/e.
Apr 18th 2011 10:56PM It's worth noting that if you're using a mouseover setup, you'll still be able to use normally-targeted healing whenever you feel like it. A correctly written* mouseover macro will still cast on your target if you don't have a friendly mouseover target, or whatever focus conditionals you end up using.
There is still the possibility of accidentally mispositioning your mouse over a player/nameplate/raidframe when you intend to cast on your target. This is a fairly legit concern, and is definitely a good reason that a mouseover setup can't be called superior-in-all-cases to a target-only healing style.
I'd say it is pretty close to 100% superior though, as long as you intend to use mouseovers for at least half of your normal healing.
On an unrelated note, my solution to the Inner Focus problem is an opt-out conditional. My GH-IF macro would look like this:
#showtooltip Greater Heal
/cast [nomod:alt] Inner Focus
/cast Greater Heal
...this automatically uses your underused cooldown when it is available, but gives you the ability to opt out of using your cooldown by holding the alt key if you have a pressing reason to save it (e.g. end of a trash pull right before a boss). It's handy to do the same with macros for using trinkets automatically too.
* Correctly written, in this case, refers to adding a pair of square brackets [ ] at the end of all the conditionals, fwiw. This is something that a macro-writer should be adding automatically to all macros using conditionals, because it essentially tells the game to "try using the spell normally" if all the other conditionals evaluate to be false/invalid.
For example, the lifegrip macro in the article (/cast [@mouseover] Leap of Faith) will FAIL if you don't have a friendly mouseover, even if you have a valid target. You can fix this by changing it to:
/cast [@mouseover,help] Leap of Faith
...which will try your mouseover first, but still LG your target normally if you don't have a mouseover. Those two little brackets are pretty helpful for writing macros that don't misbehave.
Apr 12th 2011 11:59AM I bet the mount-less question from last Queue was probably a worgen druid using flight form and running wild.
Mar 16th 2011 3:27PM FAIR WARNING: I am not at my computer, and am reconstructing all of this from memory, so not all of this may work as advertised, but I'm highly confident that I am remembering all this correctly.
The rebuke behavior you want is this:
This rebukes your opponent if you have a living,hostile focus, else rebukes whatever you have targeted.
For the focus behavior, I really don't know what you mean. You say you want a macro that "Set focus on my target" and then you say "if focus does not exists and I use rebuke on the target, this can't add this target to focus", which seems to be two exactly opposite statements. Either you want the macro to automatically add your first target as the focus or you don't. I'm thinking you really mean the latter, but I'll answer both because I'm bored.
Anyway, if you want the macro to set your Rebuke target as the focus, and remember it for the rest of the fight without ever setting another target as a focus, use:
otherwise you may want to use a modifier key, like so:
...which will set whoever you're rebuking as your focus whenever you hold down ctrl, but leave your old focus (including no focus) when you don't hold ctrl. The downside to this is that it can't be used if you have a keybind for ctrl+(key).
More likely, you just want a separate keybind for setting and clearing a focus, so you can focus whoever you want whenever you want. I'd probably use this:
This should clear your focus if he is dead or no longer exists, or if you hold alt, and focus your mouseover if you have one or your target if you have no mouseover--unless you're holding alt, in which case it clears your focus regardless. Remove the [@mouseover,nomod:alt] term if you don't want to use mouseovers, but you really should try it this way since this is super useful, letting you swap focus without targeting anything. You can use mouseover over the character himself, or his nameplate.
One quick disclaimer: I pretty much just PvE, and I'm not sure how this stuff works with an arena opponent that isn't visible to your client. If the focus macro clears your focus incorrectly when you hit the focus macro while your opponent is stealth/shadowmeld/invisible, you may want to remove [noexists] leaving just [dead]. Though I can't imagine why you'd be hitting your focus macro when you don't want to clear your focus or set a new one in the first place, so you probably want to leave [noexists].
Mar 16th 2011 12:55PM Writing simple macros is easy, but writing smooth, functional macros is a bit harder. There are a few things that are missing from this article that should really have been mentioned.
First of all, all macros should really start with #showtooltip unless they're character limit constrained. This shows the spell icon on your bars, the tooltip when you mouseover the spell, and most importantly the cooldown and range indicators. By default it shows the first spell or item in the macro, but you can force it to show anything by naming the spell directly after. So for example:
/use Soul Casket
/use Chaos Bolt
...shows the tooltip for Shard of Woe, which isn't very helpful for your main Chaos Bolt macro. Instead, write it as:
#showtooltip Chaos Bolt
/use Soul Casket
/use Chaos Bolt
Note also that /use 13 and /use 14 will use your first and second trinkets, respectively, so you can use whatever you have equipped.
Secondly, it's important to add  after any set of conditionals that isn't necessarily always true or always false. if you write the macro (from the article):
/cast [nomodifier] Crusader Strike; [modifier:ctrl] Divine Storm
...this will cast CS if you have no modifier at all, DS if you have ctrl down, and *nothing at all* if you are hitting shift or alt for some reason. If you change it to:
/cast [nomodifier] Crusader Strike; [modifier:ctrl] Divine Storm
...this will CS with no modifier at all, DS with crtl, or DS under any other circumstances. Since this is sort of stupid, you could equivalently rewrite it as:
/cast [nomodifier] Crusader Strike; Divine Storm
..without changing functionality, or write it more practically as:
/cast [modifier:ctrl] Divine Storm; Crusader Strike
Which will DS only with ctrl, and CS under all other circumstances, which it probably the behavior we're really looking for.
It's also very important when using [@focus], [@targettarget], and [@mouseover] macros to put in ,help/,harm and ,nodead terms in order to keep the macro from malfunctioning when you mistarget something. For example, as a holy paladin you might want a macro that Judges the targettarget (i.e. the target your tank is targeting), except when you have a mouseover. But if you write it like this:
/use [@mouseover][@targettarget] Judgement
...it will fail any time your mouseover is a friendly, when you clearly intend for it to judge the tank target. If instead you write like this:
/use [@mouseover,harm,nodead][@targettarget,harm] Judgement
...it will only try to judge your mouseover if your mouseover is an enemy that isn't a corpse. Note that the [@targettarget,harm] term stops you from trying to judge the (friendly) target of a hostile mob, if you're targeting one, which would also cause the macro to fail. With this ,harm conditional, the macro will see the helpful targettarget and move on to the , which lets it judge your harmful target.
Similarly, with focus macros, without ,harm and ,nodead modifiers a macro may malfunction when your focus dies and you need to cast on something else. Consider:
/use [@focus] polymorph
If your focus dies and you want to sheep something new, hitting this macro will fail because you're trying to sheep a corpse, even though you added the  to the end to let it try to cast on something else. If instead you write it like this:
/use [@focus,harm,nodead] polymorph
...It will cast on your target (through the ) anytime your focus is either helpful or a corpse. (Some people skirt this problem by writing a macro that clears the focus when the focus is dead, this works as well.)
It's also helpful to write focus macros that have a condition to override the @focus when you need to. You can do this with either a modifier key or a mouseover command, which will let you keep your focus intact, but sheep something else when you need to. This would look something like this:
/use [@mouseover,nodead,harm][@focus,nodead,harm] polymorph
This lets you sheep your mouseover if you have one, then it tries your focus, and then sheeps your target if you have neither a hostile mouseover or a hostile focus.
To do this with a modifier (on your current target) instead, it would look like this:
/use [mod:ctrl][@focus,nodead,harm] polymorph
...this casts on your target with the ctrl key down, or else casts on your living, harmful focus, and then casts on your target if you have neither a valid focus nor the ctrl key.
Jan 24th 2011 3:16PM @scooter
On behalf of Americans everywhere, thank you for taking that little parenthetical aside from an otherwise reasonable post to stereotype an entire country as selfish and narcissistic.
Jan 16th 2011 8:18PM Even when your opponents manage to break out of a 4-cap, your point lead by the time they recover is usually big enough that the game is pretty hard to lose.
Jan 9th 2011 3:04AM "It's difficult to compare 135 intellect versus 65 crit or haste to the 80ish intellect provided by most of the other crafting professions, but rest assured that it is better."
It's not difficult at all to compare them, and LW is the best profession by far for mages and every other class in the game. IDK how you can claim to be writing a profession guide without making this unequivocally clear.
Jan 5th 2011 11:18PM @rhabella
My pet idea is for most/all spirit items to just have an equal amount of hit on it without counting against the stat allocation. Since healers and dps receive negligible benefit from hit and spirit, respectively, there isn't really much of a problem with letting them have the incorrect stats.
It's sort of like how back in BC some weirdly itemized feral and ret pieces would have a tiny bit of intellect on them, and would still manage to be reasonably good for warrior or rogues.
Jan 2nd 2011 1:23PM can has?