Cure Macro craziness with the new Fix

[Emonik]

The macro I used to heal in Raids and Fates with was
/ac "Cure" <mo>
/ac "Cure" <tt>

This did exactly what i wanted it to do. I could heal party members with <mo> and then either tab around enemies healing non-party members, or stay targeted on the Boss and if he changed targets i could easily heal without having to try and click in a mass of bodies.

Yesterday's patch killed that macro. Now if i don't have a <mo> then it heals my <t>, if that is invalid it heals <me>. In other words, the first line of a Cure macro will always be satisfied, and never go to the second line.

Ok so no big deal, I can adjust. So i changed my macro to just
/ac "Cure" <mo>
This works mostly the same as you can mouse over target's target health bar and it works as an <mo>

Now this is where the craziness starts. If i have a valid healing target, here is the behavior of casting /ac "Cure" <mo>

1. If my mouse is over nothing, Cure is cast on my <t>
2. If my mouse is over a valid target, Cure is cast on my <mo>
3. If my mouse is over an invalid target(enemy, npc, out of range target), Cure will be cast on <me>

Scenario 3 is what makes no sense to me. Why <me> and not <t>?

[Nalou]

That's what every whm spell does if your target is invalid: it is cast on yourself.

[wildgalax]

exacly the same problem, they messed it up for me as well. why fix something that isnt broken, now if they dont fix it i may have to fully change how i heal since even in fights im finding myself self healing myself instead of the target i want which i never experienced before.

[Viridiana]

That's what every whm spell does if your target is invalid: it is cast on yourself.

Then that should be happening in scenario 1 as well. If the mouse is over nothing, the <mo> should resolve to nothing, which is invalid, and by your logic should then cure the player. Instead, it's being cast on <t>. Presumably, scenario 3 has a valid <t>, but an invalid <mo>; and the macro is instead resolving to <me>.

[Seppaqueas]

I am in the same boat. My macros don't work how they did. As mentioned; if their isn't a <mo>, it reverts to <me> than <f>/ Grrr.

[Nalou]

Then that should be happening in scenario 1 as well. If the mouse is over nothing, the <mo> should resolve to nothing, which is invalid, and by your logic should then cure the player. Instead, it's being cast on <t>. Presumably, scenario 3 has a valid <t>, but an invalid <mo>; and the macro is instead resolving to <me>.

In scenario 1, you mention cure is cast on your <t>, so you do have a valid target.
If your target was a monster or something you cannot cure (like in scenario 3) then the spell would be cast on yourself.

[Emonik]

In scenario 1, you mention cure is cast on your <t>, so you do have a valid target.
If your target was a monster or something you cannot cure (like in scenario 3) then the spell would be cast on yourself.

OK I get your point, even if i think it's a bit counterintuitive. So i change the macro to

/ac "Cure" <mo>
/ac "Cure" <t>

The macro still resolves with the same 3 scenarios.
In scenario 3 instead of going to the next line and healing <t> it still defaults first to <me>.

[Lafiele]

Meh, i'm old skool, I don't use <mo>

[Iymala]

I have not found any issues with my <mo> macros. Granted, I never used <t> or <tt>. I keep the boss targeted and just use simple mouseovers to heal. Yes, if someone is out of range it will default to you, but that just makes you more aware of your party. Not really a bad thing.

[Heofonum]

I don't understand the confusion. If you're "tabbing" through enemies, then <tt> is working perfectly, simply because <mo> isn't involved and the command itself won't be registered. If you're now trying to <mo> enemies for <tt> healing (changing your original style), the first line is default, making that heal invalid.... thus healing yourself.