For some reason, the <se> tag at end of macro irks me to no end everytime I see it in my groups. Probably since it just seems so out of place.
Printable View
For some reason, the <se> tag at end of macro irks me to no end everytime I see it in my groups. Probably since it just seems so out of place.
This can be tricky if the tank has quick enough reflexes to get the enmity back before it reaches you. Depending on positioning, this could still end up sending the thing sailing past the tank. It's not a bad idea, and definitely comes in handy when a tank has clearly lost track of that mob, but is as useful as it is situational.
Running the monsters back towards the tank is at least a stable method with less room for error all around.
Honestly, macros aren't reliable for healers, even for a SCH who could macro their pet actions and other buffs. There is a slight delay between when you press a macro and when it goes off so I don't really recommend using them aside from the standard "Swiftcast + Raise + "insert text alert for <t>" w/ (or w/o) a sound effect" and I usually also have a text macro alerting my co-healer/casters that I used Eye4Eye or Virus so they don't waste theirs. Tho I do have issues with my "Swiftcast + Raise" macro not working due to lag so Swiftcast will go off but the Raise will not so I have to manually press Raise, hence one of the reasons macros aren't reliable. So basically just text macros are really the only things you need.