Heals targeting self

[Dyssyd]

I've been having my targets deselect and reselect themselves really quick if I hold down my left mouse button after targeting and let it go. Maybe something similar is happening to you at the same time you happen to be casting a heal, causing the heal to go to you instead of your target?

Just a thought.

[Fiosha_Maureiba]

I don't use macro, but if the tank dies or becomes deselected from being too far or what have you, the heal will target myself.

If I'm using say like the gamepad and I don't confirm the target I'm healing, after the first heal, the target will snap back to the primary target. If no primary target selected, the game will just heal myself. I thought this was an intended mechanic, so I've been using it to target myself sometimes.

[JonFarron]

I use mouse over macros, and this happens to me all the time. It's very frustrating on my WHM. (Less painful on SCH because I have Embrace macrod to my Physick and Adlos, so fairy usually heals them while I'm here wasting a cure on myself.)

Face target does help a lot though, so you can quickly cancel and recast. Like if you're healing the tank, and didn't face towards them, that's a red flag. Lol

[DxWings]

/ac "Cure" <f>

This is the only macro I use for a WHM for curing Tanks. And it works for me flawlessly.

Even when manually targeting to heal, my heals still go through to the target I'm trying to heal, no problem there.

The only way I've got this problem to occur is using a macro that failed to execute, such as:
/ac "Cure" <tt>
/ac "Cure" <t>

or using no macro but attempting to heal a hostile target.

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

These macros will not execute at all if these conditions aren't met.

If you have no target, just casting a Cure(No macros) spell will not execute. However, Physick, on the other hand does execute even if you have no target.

[Teleniel]

If your current spell-target is an enemy, no-target, or a dead player... then your heals will default target to yourself.
If you are using macros that have a VARIABLE-target (<t>, <tt>, <mo>, <bt>, <f> etc) this might be happening in the line order execution.
If you are using macros that use SINGLE targets (<pet>, <1> / <me>, <2> etc.) this is less likely, but still may happen if you attempt to cast on a dead target (I believe non-existant targets still fail)

[Kinseykinz]

Again, you are all missing the point.
You are in a Duty, DDing or maybe curing another party member when you realize, time to cure the tank. So You target the tank.

The tank is targeted.
The tank is in range.
The tank STAYS in Range and STAYS targeted as you cast Cure, but it does NOT cure on them, it hiccups and cures you. It happens with or without macros.

I don't know what causes it other than to say, it seemingly only happens when I switch from the mob as my target to the tank or from the tank to a party member for a targeted cure and don't wait a second. Basically, what I think is happening is some of us, have faster reaction times than the game and are switching targets and casting cures before the games delay catches up with us (IE lag). So for the SAME reason some people go 'DUDE I was out of that plume!...and you in fact see on video, they were on their screen, occasionally, in the heat of the moment, the same thing can happen with a Cure...that the game didn't process the switch in target but DID catch that you are casting a new spell'

No, we're not too dumb to see that we don't have the tank targeted.
No we're not all using macros.
No we're not talking about when someone runs out of range... yes the same 'effect' happens, but that isn't what is being discussed.

And no: Having to write Macro's to circumvent the issue isn't an answer. I'm faster than your macro..the only reason it is working is because the macro adds in the 1-2 seconds of delay you need for the data center to catch up to the information you are sending.

I don't record my gameplay, but if there are WHM's having this problem who DO...can you record a couple instances of it happening and maybe post what those videos both here and in the bugs forum? It might be the only way to maybe get closer to remedying the issue. But until people can actually see I think it's going to be a 'your macro is wrong' debate, and not an oh...yeah wish that would stop happening too conversation.

[alhandra]

snip.

i experience this often, i do not use any macro's but have this happen quite frequently. the latest of which caused a wipe in t4 that subsequently ended the run early =(

[xAlice]

I am also concerned about this issue. I tend to heal myself at random when I have tanks targeted, focus targeted, facing them AND mouse over on them. I dont really know where to even begin trying to figure out where the issue is. Theoretically, if my tanks are on target, focus target, AND my mouse is over focus target, I should actually be healing said person. Yet, here and there a really important heal gets wasted on me. Is it really the mouse over that has become an issue? Didn't really notice it pre-2.1 patch.


Can someone explain more about the "face target" macro though? I'm a little confused. Does that mean that heals with this function will heal the Focus target?

Edit: I've a theory. What if the server registers one target at a time because "target's target" is merely a function that exists in game client only? Just to clarify though, while I don't dps in T4, it does still happen. It's possible that other variables had caused the issue in T4 and that I just haven't picked up on it.

[Bixby]

Can someone explain more about the "face target" macro though? I'm a little confused. Does that mean that heals with this function will heal the Focus target?

No, it just makes your character turn and face your target. It's the same as hitting the F key or having the setting turned on to automatically face your target with every skill. JonFarron was saying you can use it (sometimes) to tell if you're casting on the right target, since you'll (sometimes) turn around, whereas self-healing will keep you facing the same direction.

I suspect there might be a little bit of delay between clicking on someone and having them registered as a valid target. Have you ever tried targeting someone who's not quite in range (the run back from a wipe in CT, for example)? Sometimes the client seems like it's trying to target them, and then realizes it can't and gives up. I think I've had it actually put the little yes-really-targeted outline around them in the party list for a split second before switching back. There might be enough of a disconnect for this to be the issue when there are no macros in play. You click the player, then click your keybind, then the client decides the target is valid, but you're already self-casting.

[Taika]

Are people reporting these issues using self-cure as one line in their heal macro (after <t> or <mo> or whatever)? I only have <mo> macros for all my heals (one line only, no alternative target options at all) and have never experienced this issue.