Yeah, it definitely should never happen when you've got someone targeted but it does. It's so stupid!
The problem with mo is there is no feedback from the server to tell you you've tagged the guy. I'm used to clicking the party list to heal (used to use F1-F5 in FFXI) and it's more precise. i don't want to let a pixel or lag ruin my day.
Yeah... does it also do this if target goes out of range or LoS after you start cast?
Seems like it does... like you lose your target and hit yourself. Not sure, though.
There could be another case......
Because the macro only check once....
If u accidently pointing at a mob or object, ur macro will fail and end up healing urself with or without <t> line in between..
It could be any object like doors or sometimes a rock that dont have HP and name..
I've found this happening A LOT with Leeches, but have noticed it with heals as well. I also use <mo> macros, but I'm not sure that would matter if you've got the auto-target self if target is unavailable (or however it's worded) option checked. I'm pretty sure the game checks if the target is available to heal, if they are not (because of range, obstructions, or w/ever) it will automatically target you.
I tried, but just to found out I have already addicted to it.Because it allows u to heal others without deselect tank. So if u want to heal tank,just move ur mouse away from names, instead of looking up in the table again. That's a huge improve of respond speed, especially when u have a crap geared tank in the party...
My suggestion is, put both macro and original into the bar, so u always has a way to guarantee delivery.
For my WHM, I keep the macro for Cure, but removed Cure II...SCH seems to have much more resistance to backup these kind of failure, because u can just let pet AI auto heal others or keep focus on tank...
Also, check ur system performance. If ur CPU load reaches 100%, try to turn off some physic effect or FXAA(minimum, but still helps) to lower it...