Useful Healing Macros

[JonFarron]

Thank you!! the <mo> is amazing! having to click everyone was proving a pain =p

IKR!?

I discovered it yesterday. Before, having to click someone was driving me nuts especially in crowded places because you might keep click the wrong person. Also, attempting to click someone running from a mob? Yeah good luck... And then the target nearest PC hotkey did just what it says. Targets nearest PC, no cycle through, so I was getting frustrated. Once I found out the mouse over hotkey, I simply stuck it where I had put my target nearest PC hotkey, so now It heals whoever Im moused over when I press it. It has greatly improved my reaction times as well. SO HELPFUL OMG.

I set the mouseover macro as follows:
/ac Cure <mo>
/ac Cure <tt> (this goes next after it sees you're not moused over someone. What this does is cure the target of your target. So for example if you're attacking a squirrel, but the squirell is attacking tank, using this macro while you're targeting the squirrel will cure the tank. if you're attacking the squirell, and the squirrel is attacking you, using this macro will cure you.)

I also recommend adding a an announcement phrase that your raising someone so they don't go to town.
/ac Raise <t>
/s (Casting Spell) (Raise) (Stay there.) <t>

( "()"=translator)

[Chiyasa]

I set the mouseover macro as follows:
/ac Cure <mo>
/ac Cure <tt>
/ac Cure <me>

I wanted to use such a macro but there are two things which are really annoying.

First: Whatever you want to heal you always get error-messages in the chat saying that targeting for one of the commands is wrong (can't remember exact wording).

Second: If you want to heal a mouseover target, the cast starts but at the same time, there is an error message in the center of the screen saying something like "already casting" (can't remember exact wording).

I think these two error occur because the game tries to execute all three commands regardless of your target, global cooldown or if you are already casting. So <mo>-cast starts but at the same time the game tries to also cast <tt> which fails because you are already casting the <mo>. You can deactivate the chat-error but I didn't find a way to disable the error in the center of the screen which is annoying me the most.

So at the moment I just stick with a one-command macro with <mo> targeting to avoid these annoying error messages.

[JonFarron]

@ Chiyasa

Yeah the chat errors are a bit annoying, although I never get a message in the center of the screen. You're probably pushing it before your global cooldown is up.
I will likely make separate macros once my Naga comes in. I hate keyboard hotkeys so kind of stockpiled some macros into each other, feels like FF12 gambits xD

[Fatalmephisto]

@ Chiyasa

Yeah the chat errors are a bit annoying, although I never get a message in the center of the screen. You're probably pushing it before your global cooldown is up.
I will likely make separate macros once my Naga comes in. I hate keyboard hotkeys so kind of stockpiled some macros into each other, feels like FF12 gambits xD

You can disable the error message in the chat filters.

[Lathander]

IKR!?

/ac Cure <mo>
/ac Cure <tt> (this goes next after it sees you're not moused over someone. What this does is cure the target of your target. SO for example if you're attacking a squirrel, but the squirell is attacking tank, using this macro while you're targeting the squirrel will cure the tank. if you're attacking the squirell, and the squirrel is attacking you, using this macro will cure you.)
/ac Cure <me> (If none of the above requirements are meant (No mouse over, no target's target), it will cure you)

I'm not able to currently log in right now otherwise I'd test it myself - but does this macro also adjust to manually clicking on the names on the party frame? In otherwords, am I able to replace my main hotkeys with those permanently to be more versitle?

Thanks.

[JonFarron]

I'm not able to currently log in right now otherwise I'd test it myself - but does this macro also adjust to manually clicking on the names on the party frame? In otherwords, am I able to replace my main hotkeys with those permanently to be more versitle?

Thanks.

The goal for the macro is to not have to click people in the party menu at all. You just simply mouse over their name in the menu, and use the macro hotkey.

[Lathander]

The goal for the macro is to not have to click people in the party menu at all. You just simply mouse over their name in the menu, and use the macro hotkey.

Thank you for the clarification.

[Taemek]

I set the mouseover macro as follows:
/ac Cure <mo>
/ac Cure <tt> (this goes next after it sees you're not moused over someone. What this does is cure the target of your target. SO for example if you're attacking a squirrel, but the squirell is attacking tank, using this macro while you're targeting the squirrel will cure the tank. if you're attacking the squirell, and the squirrel is attacking you, using this macro will cure you.)
/ac Cure <me> (If none of the above requirements are meant (No mouse over, no target's target), it will cure you)

I also recommend adding a an announcement phrase that your raising someone so they don't go to town.
/ac Raise <t>
/s "Don't move, you're being raised" <t>

These work fine, but how do you disable the "Unable to use /ac "Cure" <mo> and <tt> on that target" messages?

[JonFarron]

These work fine, but how do you disable the "Unable to use /ac "Cure" <mo> and <tt> on that target" messages?

You can't at the moment. I doesn't really bother me though.

I actually ended up taking out the /ac Cure <me> from it. Often times I would be too far from the player I was targeting and it would cure me while I was thinking it was curing them... haha.

[Taemek]

You can't at the moment.

I disabled error messages in a newly generated tab for this purpose only.

I have been having issues the macro in general also as you pointed out and then some, it just feels too clunky and it is very restrictive due to the nature of the commands in it.

It becomes an even bigger issue when you are trying to heal NPC's targets. It keeps healing us instead of the <tt> if the <tt> is found to be an NPC. I failed a single player mode storyline quest for the first time last night due to this issue where I had the mob targeted and it simply would not heal my <tt>, so I had to make a fresh Cure button with no macro after that and passed it np.

I think I am going to just stick with the <mo> macro for it. If there was a command you could put in at the bottom of the list to allow it to work just like the skill itself where it was not macro'd, it would be better and we would be able to remain more mobile.