Macro Erroneously Heals Me at Worst Possible Moments

So, my bf and I are both running into the same problem: our healing macros occasionally go berzerk and heal us instead of our targets. He's SCH, I'm WHM, and our spell macros are more or less the same:

/ac "Healing Spell" <mo>
/ac "Healing Spell" <f>
/ac "Healing Spell" <t>
/ac "Healing Spell" <tt>

We do not have <me> anywhere in the macro.

Sometimes, however, after going through the spell animation, the heal ends up hitting US instead of our intended target. This happens with mouseover on character models, nameplates, and the party list, and even when we have the intended recipient either targeted or even Focused.

Has anybody else run into this? It seems to happen at absolutely THE worst times!

Thanks for your help.

I personally prefer not to use macros for my healing, but I think I remember hearing that <tt> does not work for healing spells if you have selected an enemy; so, if you're targeting the boss and hit a heal it will hit you instead of the tank or whoever his target is. Someone who doesn't like to micro manage can probably confirm or deny.

its a bug with <tt>
if your targeting a mob, it casts on you.
If your targetting someone , and your out of range or LOS, it casts on you. (and dosnt warn you that your out of range)

remove <tt> from healing macroes and only use it for DPS attacks instead....

Omg Hiro I have not seen that FFXI Screen Shot in ages...It warmed my old nostalgic soul lol@ JP button

Quote:

---

Originally Posted by Aphrini

Omg Hiro I have not seen that FFXI Screen Shot in ages...It warmed my old nostalgic soul lol@ JP button

---

Yeah I was trudging through an old backup looking for an image and found it. Made me smile.

Quote:

---

Originally Posted by Staris

its a bug with <tt>

---

It's not just <tt>. It can happen with any* of the placeholders (<t>, <mo>, <square>, etc.) if what they're currently pointing to is an enemy. Macros behave just like casting the ability normally with whatever the placeholder is pointing to as a normal target. And the behavior for cure spells when you're targeting an enemy is to self-cast. So that's what macros do.

*Except, of course, the ones that can't be enemies (<me>, <1>-<8>, <c>, <pet>, etc.).

Basically, choose one targeting type for cures (mouseover, target-of-target, etc.) and stick with that, and just that. You'll never get fall-through logic to work consistently with these kinds of macros for healing.

Im having this same problem :/ I use <tt> as well, so ill test it tonight.

I have a similar problem and am not using <tt> in my macros, but am using <me> at the very end of my macro.

So I have:
/ac "Cure" <mo>
/ac "Cure" <t>
/ac "Cure" "Tank Name"
/ac "Cure" <me>

when running dungeons I occasionally run into an area where the cure spell heals me instead of the tank, when I am moused over AND targeting him. no idea why. its frustrating for sure. My next step was to remove <me> entirely and see if it still has a problem.

interestingly, without the tank or I moving, the next cure spell works fine.

Essentially you can't use <t> and <tt> in a healing macro. If you put <t> first, any time you try to cast with an enemy targeted the spell will heal you. If you put <tt> first, any time you try to cast with an ally targeted it will try to heal whatever they are targetting; if that's an ally the spell will heal them, but if it's an enemy the spell will heal you.

Quote:

---

Originally Posted by Menae

Essentially you can't use <t> and <tt> in a healing macro. If you put <t> first, any time you try to cast with an enemy targeted the spell will heal you. If you put <tt> first, any time you try to cast with an ally targeted it will try to heal whatever they are targetting; if that's an ally the spell will heal them, but if it's an enemy the spell will heal you.

---

I'll second that. Experimenting with <t> and <tt> always led to tears.
What I do now is have macro set up to heal <mo> then <f>. I focus the tank I'm assigned to, keep bosses targetted, heal party by mouseover on party frames. Works as expected this way.

Yes I understand the use of <t> but the erroneous healing still occurs when I have the tank targeted in those cases, I dont have enemies targeted.

I like the recommendation of the <f>, and will try editing my macros to remove <t> but still doesnt address the healing miss that I see especially when no movement changes occur and one heal hits me and one hits the tank as intended in a chain of cure spells.

I still think there is a fundamental bug at play here.

I use number targets because of this.

Since I'm primarily healing the tank I set it to <2> and just move tank to the 2nd party position for every group. Still keep a separate <mo> macro for other players though.

It has nothing to do with you being out of range, or out of line of sight, or anything like that. It's simply a bug with mouseover macros, or possibly macros in general. I've reported it many times during beta and release (it's even in the Accepted Bugs section) but the issue persists. Maybe 2.1 will fix it.

Some people are suggesting that it only happens with fall-through macros (eg. having "/ac Cure <mo> /ac Cure <t> /ac Cure <me>" all in one macro) but I don't think that's the case, since I'm pretty sure I've had it still happen even after removing all but one of those lines.

I can definitely confirm, however, that the bug occurs more frequently if you spam the macro during the GCD or if you're in the middle of an animation lock from another spell. This of course means that it's very prone to screw up at the worst times when the party is close to wiping and you're going crazy mashing buttons trying to keep people alive. As a result, I've gotten very good at pressing the button exactly once, and now the bug almost never happens for me. Maybe once or twice per Coil clear.

However I do *not* use mouseovers for emergency stuff like Lustrate or Benediction because if I misheal with those spells it usually means someone is going to eat the dirt. I also don't use it for Esuna/Leeches as the short cast time on those spells seems to make it more likely to bug out the macro.

Ah! good info, thanks Ninix