Favorite rez macro texts?

[galbsadi]

Macros are not suited for combat. So you find the people who've learned this and don't use a raise macro to generally be at least a notch above average.

Typically I would agree, but in this case we're talking about macros that are basically still just the one action, but with an announcement that quite frankly can help prevent other issues.

Example: a resurrection macro in content with multiple healers saves another healer from burning their own time and/or swiftcast to rez the same person (and I've lost count of how many times before using macros myself I'd go to rez somebody, pop my swiftcast, and then another healer rezzes the person with no announcement whatsoever...boom, wasted swiftcast, 1min CD).

Example 2: the DRK ability Living Dead saves them from a fatal blow, but they need to be healed to 100% afterwards or they still die. That's useful information, because otherwise I'd probably assume a tank at 90% is in good condition and might not heal them that last 10%...then they go splat.

Example 3: if you're doing PUG content and use a healer LB3, a macro could potentially alert an otherwise inattentive DPS that they are now alive and can do stuff so they don't just stand in bad and die again.

[Gemina]

Example: a resurrection macro in content with multiple healers saves another healer from burning their own time and/or swiftcast to rez the same person (and I've lost count of how many times before using macros myself I'd go to rez somebody, pop my swiftcast, and then another healer rezzes the person with no announcement whatsoever...boom, wasted swiftcast, 1min CD).

A rezz announcement from a healer is training wheels for the other lesser experienced healer. In such a situation I guess it's OK, but healers need to eventually rely on monitoring the status bars, and identifying the icons as they pertain to them. A wasted swiftcast is no one's fault except the player that wasted it. Take accountability.

Example 2: the DRK ability Living Dead saves them from a fatal blow, but they need to be healed to 100% afterwards or they still die. That's useful information, because otherwise I'd probably assume a tank at 90% is in good condition and might not heal them that last 10%...then they go splat.

What matters is the DRK is returned 100% of his Max HP. Not restored to full. No announcement from the DRK is needed because he's sitting at 1HP. This is WELL below even the tightest thresholds of the game's best healers. If the healer can't see to cure bomb the hell out if the DRK, it's on them that the DRK dies to LD.

Example 3: if you're doing PUG content and use a healer LB3, a macro could potentially alert an otherwise inattentive DPS that they are now alive and can do stuff so they don't just stand in bad and die again.

If anyone needs notification that a healer LB3 just went off, they should get their eyes and ears checked.

[galbsadi]

A rezz announcement from a healer is training wheels for the other lesser experienced healer. In such a situation I guess it's OK, but healers need to eventually rely on monitoring the status bars, and identifying the icons as they pertain to them. A wasted swiftcast is no one's fault except the player that wasted it. Take accountability.

Either you have macro'd swiftcast to your raise or you're failing to account for the timespan between hitting swiftcast and another raise showing up on a status bar. It happens. I've seen it happen numerous times. (Granted, typically it happens in large-scale content where I can just rez some other person who chose to stand in bad, but it still happens.)

What matters is the DRK is returned 100% of his Max HP. Not restored to full. No announcement from the DRK is needed because he's sitting at 1HP. This is WELL below even the tightest thresholds of the game's best healers. If the healer can't see to cure bomb the hell out if the DRK, it's on them that the DRK dies to LD.

Fair enough. I typically don't play DRK enough to have paid that much attention to that particular ability.

If anyone needs notification that a healer LB3 just went off, they should get their eyes and ears checked.

You do realize that you probably just accurately described a substantial portion of people in DF, yes? I mean, how many times do you still see people to this day not stand behind rocks on Behemoth?

[Gemina]

Either you have macro'd swiftcast to your raise or you're failing to account for the timespan between hitting swiftcast and another raise showing up on a status bar. It happens. I've seen it happen numerous times. (Granted, typically it happens in large-scale content where I can just rez some other person who chose to stand in bad, but it still happens.)

Neither is the case. I don't have either SC or any rezz macroed, yet I'll get the rezz off faster than a SC+rezz macro with a 1 sec wait between skills will allow. The window between my SC and rezz is lightning fast because the skills are not macroed together so I can actually queue either SC, rezz, or both. That is why I beat nearly all macro using PUG healers to the punch. You will literally miss my rezz if you blink. Another healer would have to use their SC almost simultaneously to get their SC inside this window.

You do realize that you probably just accurately described a substantial portion of people in DF, yes? I mean, how many times do you still see people to this day not stand behind rocks on Behemoth?

All the time. Same with those who place the rocks inside his hit box, resulting in no place on the field to shield meteor. But I'm not sure how that applies to rezz macros and tying SC to them. This mechanic just reinforces that players need to be paying attention to the field, not their chat boxes.

[Jollyy5]

The window between my SC and rezz is lightning fast because the skills are not macroed together so I can actually queue either SC, rezz, or both. That is why I beat nearly all macro using PUG healers to the punch. You will literally miss my rezz if you blink.

That.

For example, back in ARR while doing Titan EX, you could resurrect a player mid-air if they got killed by Landslide, would've been a lot more difficult with a macro.

I also like to get back to healing/DPSing without clipping into GCDs too much, not to mention that I like to keep Swiftcast available for other things.

[miraidensetsu]

What matters is the DRK is returned 100% of his Max HP. Not restored to full. No announcement from the DRK is needed because he's sitting at 1HP. This is WELL below even the tightest thresholds of the game's best healers. If the healer can't see to cure bomb the hell out if the DRK, it's on them that the DRK dies to LD.

The info is yet important because of how LD works. There are 2 phases: when he is with Living Dead active and with Walking Dead. Both appears on the DRK's status bars.

While it's with Living Dead buff, the healer can safely ignore him (or must resist the urge of healing the tank), because he won't die, but instead will get the Living Dead buff while he have the Living Dead buff. While he's with the Walking Dead buff, he is invincible for 10 seconds. If the DRK don't receive healing equivalent of 100% of his HP, he will die. If he does, the Walking Dead effect fades. The healer(s) must plan their actions to ignore that tank for some seconds after he gets the Walking Dead buff and top him up just before the 10th second after WD is up by any means available. It's a good idea to save the oGCD heals for that final seconds.

In that case, the healer can know by looking at the DRK's status bar. But if DRK says to the healer(s) that he will use that action, that would be a great idea, because that will one more clue to the healer(s). If after that the tank still dies, it's on the healer.