Cure Macro craziness with the new Fix

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>?

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

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.

Quote:

---

Originally Posted by Nalou

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>.

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.

Quote:

---

Originally Posted by Viridiana

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.

Quote:

---

Originally Posted by Nalou

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>.

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

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.

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.

Quote:

---

Originally Posted by 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.

---

Yes that's fine in a party, but i'm talking specifically in CT or during Fates when mousing over someone not in your party isn't that simple.

Quote:

---

Originally Posted by 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.

---

If i'm tabbing through enemies with the macro
/ac "Cure" <mo>
/ac "Cure" <tt>

and my mouse is over nothing, after the patch it defaults to healing <me> instead of <tt> because now if <mo> is invalid it goes to <me> instead of the next line of the macro.
Before the patch this macro works as it looks like it should, if no mouse over then <tt>.

From Reinheart's twitter feed:

Quote:

---

Minagawa-san says the issue where if you had 2 lines of macro and not working correctly will be fixed in 'hotfix' as it'll affect other parts of the game. This one is for like cure macro, 1st using <mo> 2nd using <tt> 2nd one gets ignored and cures you instead.

---

Greetings,

Below is a comment from Hiroshi Minagawa about this macro issue.

Quote:

---

Originally Posted by Hiroshi_Minagawa

I apologize for the delay in responding about this.

We’ve begun making fixes to the macro syntax process so that macros function the same as they did in 2.15.

This issue is different than the cross hotbar issue that we will be addressing with an emergency patch, and if we were to simply revert it back, bugs would arise in newly implemented features, so we will be addressing this with a Hotfix.

With the fixes we are currently working on, all of the macros you’ve made up until patch 2.15 can be used just as before.

As of right now, we have not been able to confirm whether or not macros created after patch 2.16 will be supported. Once more details are discovered I will be sure to update you all.

I apologize for the inconvenience and will be making a follow-up as soon as possible.

---

I don't understand how this is different from the old behavior...cure spells always defaulted to the player if an invalid target was targeted. This is SE's "smart targeting" of cure spells (I guess it's solo-friendly).

EDIT: Well, I do understand how totally ignoring subsequent lines would be bad, but not why the smart-targeting working this way is new. Though I would love smarter smart targeting.

Quote:

---

Originally Posted by Nalou

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

---

yep, exactly why my pet macro didnt work how i wanted it to.. i wanted to spam embrace while DPSing in less healing intensive areas.. so i made this macro:

Quote:

---

/micon "Ruin II"
/ac "Ruin II" <t>
/ac "Ruin II" <tt>
/pac "Embrace" <t>
/pac "Embrace" <tt>

---

my plan was that i could target mobs or the tank and still ruin something and embrace the tank..

Logic of the Ruin:

check first instruction
valid target? yes - cast
valid target? no - check second instruction - cast

but unfortunately the logic of this macro on the faery is:

check first instruction: <t>
is that a valid target? yes - embrace the target
is that a valid target? no - embrace self (faery)

so the macro still works as i intended it to do if i basically choose one or the other.. so.. if i wanted to target the tank it would be

Quote:

---

/ac "Ruin II" <tt>
/pac "Embrace" <t>

---

and if i wanted to DPS mobs without targetting the tank it would be

Quote:

---

/ac "Ruin II" <t>
/pac "Embrace" <tt>

---

interesting enough, besides now curing myself when I have no target my macros on whm still work exactly the same

Quote:

---

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

---

when I have a target but no mouse over I heal the target, but when I'm mousing over someone I heal them instead (mousing over a mob and I heal myself)

Quote:

---

Originally Posted by Kayokane

interesting enough, besides now curing myself when I have no target my macros on whm still work exactly the same



when I have a target but no mouse over I heal the target, but when I'm mousing over someone I heal them instead (mousing over a mob and I heal myself)

---

You can remove the second line from your macro and it will behave the same.

However it's the part of your post in ()'s that is my issue. If your mouse is over something invalid it should heal your target first, then if no target you.

But mostly I'd like it to go back to the old way where multiline healing macro's worked. And it looks like that's what going to happen.

Quote:

---

Originally Posted by Camate

Greetings,

Below is a comment from Hiroshi Minagawa about this macro issue.

---

Thank you for this

This is why I don't use macros.

Quote:

---

Originally Posted by Bufkus

This is why I don't use macros.

---

I use to not use macros either and tbh most of the time they are no different from healing without macros, but they come in handy that 1/1000 time where you want to heal someone while still targeting the MT and need to have the boss focused to see the one really annoying ability coming up (though honestly I don't think a situation like that is actually in the game yet)

I have the same problem OP. This is my Cure Macro:

/ac Cure <mo>
/ac Cure <f>

With my tanks focus targeted, pre-2.16 Cure would always default to healing my tank. If I needed to spot heal, I would mouseover and Cure that person. Post 2.16, I always Cure myself unless I mouseover. Curing this way frees up my primary target so I can watch for enemy cast bars and swap targets easily if I have the opportunity to DPS. Now I can't do any of that.

I used this macro when the game first launched.

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

but due to lag and other issues that macro was ineffective, so I resorted to deleting the second and third line of the macro. Now with 2.16, /ac "Cure" <mo>, works exactly like the macro I first used and I do not wish for SE to change it back to the way it worked before 2.15.

I'm pretty sure the reason (especially for healers) for the non-self targeting macro pre 2.16 is to give you an indication of your heals being out of range. That's why most end-game healers use macro to prevent healing yourself. In my opinion, when I pressed my heal macro and the cast failed, immediately I knew it's out of range and I can react to it. I'm not sure the reason for the macro change when there is <me>.

Another thing is <f> doesn't work anymore (in my case unless i did it wrong). If I placed <f> on first line it works but any other lines will not work.

/ac Cure <mo>
/ac Cure <t>
/ac Cure <f>

Above is what i used before, I can heal focused tank without targeting the tank while I can mouse over to heal or heal a specific target. Still works but the <f> doesn't work for me anymore, it just trigger self heal when no <mo> or <t> is present.

When will be able to input buffer macros?

Quote:

---

Originally Posted by Darkoon

I used this macro when the game first launched.

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

but due to lag and other issues that macro was ineffective, so I resorted to deleting the second and third line of the macro. Now with 2.16, /ac "Cure" <mo>, works exactly like the macro I first used and I do not wish for SE to change it back to the way it worked before 2.15.

---

Except this isn't completely accurate. Now if you have a target, and hit your "Cure" <mo> macro, if your mouse happens to be moused over something invalid it will heal <me>.

Such as AV if you have the Tank targeted and leave your mouse hovering on the Fruit and hit your Cure macro it will heal <me> instead of <t>
Or if you have your tank targeted and an add happens to walk where your mouse is hovering it will heal <me> instead of <t>.

This is the problem I am trying to point out with this post.

Quote:

---

Originally Posted by Emonik

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>?

---

As far as my understanding goes, this happens because the game assume that since you are targeting an invalid target (i.e. an enemy) it heals you because that's the way it's coded. Just like when you are soloing, if you hit a heal while targeting an enemy, it's not going to try to heal the enemy. Instead this assumes you meant to heal yourself. Same goes for an NPC. NPC's don't need heals. However, the target out of range is weird. It should at that point see an error and drop the macro completely or go to target unless your target is out of range too. Then it would just not work. Hmm...

They just fixed the macro, now <mo> no longer give <me> as default but return invalid, just like the old days :cool:

Edit: The lag still set in, but at least you can make 2 line of macro instead of 1

so far looks fixed, thanks se, finally get enjoy healing again.

I do not welcome this "fix". <mo> no longer heals the way I want it to.

Quote:

---

Originally Posted by Darkoon

I do not welcome this "fix". <mo> no longer heals the way I want it to.

---

That sounds like a personal problem, because there's very little the current macro system can't do. What exactly do you want your macro to do?