Question on a specific healing macro

Hi there,

yesterday I came up with a "target forwarding" heal macro for my girlfriend as she's used to this feature from playing Lotro. So the goal was to make targetted heals work on either the target itself, if a valid target (--> a player character) is the current target, or on the target of the target, if the currently selected target is a mob, so you would heal whomever is currently being attacked by that mob. This is quite useful in boss fights, as you could cast damaging spells or debuffs on the mob and still be able to heal the tank without the need to switch targets. Also in case of someone else suddenly picking up the mob's attention, the heals would directly go to the person who is now being attacked by the mob.

So, what I came up with was:

Code:

---

/micon "Vita"
/ac "Vita" <t>
/ac "Vita" <tt>
/ac "Vita" <me>

---

The idea was to always heal the current target first, if a valid target was selected, then fall back to healing the target of the current target, if no valid target was selected and then finally resort to healing oneself, if either no target was selected at all or the selected target isn't targetting anyone (e.g. when targetting a non-aggroed mob).

Unfortunately this macro doesn't work as expected. Whenever she used that macro on a mob which was attacking someone else, the heals would always be directed to her, no matter whom the mob was actually attacking.

Strangewise this macro does reliably work as expected:

Code:

---

/ac "Vita" <tt>

---

Any ideas why the first one isn't working? I'm really puzzled with this behaviour. Is this a bug?

All heals and buffs are cast on self, if there is no target selected or can't be applied on the selected target (not friendly npc).
I can't check right now, but there is probably a setting (there is one on most MMOs) where you can turn this self-cast thing on and off, since it is usually just a preference.

Seems to work for me.
If you don't have a mouse over, it will cure whoever you're targeting. If you don't have that it will cure yourself.

Code:

---

/micon Cure
/ac Cure <mo>
/ac Cure <t>
/ac Cure <tt>
/ac Cure <me>

---

Quote:

---

Originally Posted by draftzero

Seems to work for me.
If you don't have a mouse over, it will cure whoever you're targeting. If you don't have that it will cure yourself.

Code:

---

/micon Cure
/ac Cure <mo>
/ac Cure <t>
/ac Cure <tt>
/ac Cure <me>

---

---

But does this also work if your mouse is currently not over any target (e.g. you just click the macro icon in your hotbar) and your current target is a mob and not a player character? That's the functionality I was trying to implement with my macro.

Quote:

---

Originally Posted by Thycin

All heals and buffs are cast on self, if there is no target selected or can't be applied on the selected target (not friendly npc).
I can't check right now, but there is probably a setting (there is one on most MMOs) where you can turn this self-cast thing on and off, since it is usually just a preference.

---

Good call, I'll check the game settings myself once I'm out of the office. If there is such a setting, that could very well be the root of the macro's misbehaviour.

Quote:

---

Originally Posted by Vodomir

Good call, I'll check the game settings myself once I'm out of the office. If there is such a setting, that could very well be the root of the macro's misbehaviour.

---

Let us know the result, because if there is such a preference, the macro you are making will be really useful for me!

I tend to take most <me> out of my macros due to the fact it seems, if you hit the key before the spell refreshes the macro tries the first lines and by the time it gets to <me> the spell is ready and casted on yourself :(

Quote:

---

Originally Posted by Exphryl

I tend to take most <me> out of my macros due to the fact it seems, if you hit the key before the spell refreshes the macro tries the first lines and by the time it gets to <me> the spell is ready and casted on yourself :(

---

confirmed... when u cast spell back to back u often end up being the target of the spell if u have the <me> target as the last macro... removed it from all my MO macro and now it workd much better... if i need to heal myself I just deselect taret by clicking on empty screen...

Quote:

---

Originally Posted by Thycin

Let us know the result, because if there is such a preference, the macro you are making will be really useful for me!

---

Unfortunately there is no such setting, thus the macro will never work as intended. The problem lies within the innate funtion of targetted heal spells. If you cast a heal spell on a non-valid target, the spell will always apply to the caster. Looks like there is no way to make this macro work -.-

I sort of go the old school MMO, without mouse over and it works very well in dungeons. But I use mouse over for fates and stuff since those not in my party tend to run around like headless chickens. I wish the targeting system was easier to use

The order matters I believe. The <tt> has to come before the <t>. If <t> is first and you are targeting a mob, it will find that it can't cast on the mob and default to you (seems like some kind of in-game code or possibly a setting for cure spells -- that if you cast a cure or physick while targeting a mob, it will think you must mean to cast on yourself). But with <tt> first, if will check the <tt> and then the <t>. For some reason, this also works if you are targeting the tank. It will check the <tt> and find it cannot cast on the mob, but then it will check the <t> (tank) and cast on them. It won't just default to you -- possibly because the use of the <tt> does not auto-trigger the "oh you must mean to cast on yourself" default.

/micon Cure
/ac Cure <tt>
/ac Cure <t>

People will be tempted to put /ac Cure <me> at the end, but I would caution against. If you are out of range, you will cure yourself thinking you are curing the tank while casting.

I logged a bug about this, feel free to give it a thumbs up, or comment on it or something, not sure what good that does.

Basically, the issue is a macro will EXIT/LEAVE/RETURN when the following conditions are met: Invalid Target, Not Enough Resources.

However, if an ability is on cooldown, it will skip to the next line, which is the expected behavior for the previous two cases. Unfortunately it doesn't work like that right now. I'm assuming this is an oversight, and that the macro system simply works like this because of the way action erroring was originally designed. I'm hoping we will get a fix, considering that right now macros are absurdly useful for melee and useless for mages.

I use this for raid bosses for cure and regen on ps3 just change the number for what target you what to cast for


/ac "cure II'' <1>
/wait 3
/ac regen <1>