Please do not allow the renewal of the Raise buff on a dead player

[snuggans]

you already know what i'm talking about: someone in the raid dies, 2 or more people swiftcast-rez that person, the end result is that a bunch of people have just wasted 20% of their MP + swiftcast trying to rez one person. why not just give an error message to everyone except the first person who landed the rez?

on a related note, i tried the basic "i'm rezing <t>" macro to inform everyone else who i'm rezing in order to avoid the above situation, and i found it to be inconsistent: occasionally the rez doesn't trigger, but the message always does, so i scrapped it and now i'm using the Raise action plus a macro with only the message. very cumbersome

[Kurando]

Macros generally are enough, but it's up to you and other players to play attention on what is happening. Personally I give it a few seconds before throwing out a rez as someone else might do try to do it first and I get to avoid issues of wasting MP, but these things happen so it's no big deal if something overlaps. Rez is a temporary buff though so if you use another, the timer gets reset on the player and that's why there is no error message, not that there couldn't be, but that's the way it is at the moment.

[Seraphor]

on a related note, i tried the basic "i'm rezing <t>" macro to inform everyone else who i'm rezing in order to avoid the above situation, and i found it to be inconsistent: occasionally the rez doesn't trigger, but the message always does, so i scrapped it and now i'm using the Raise action plus a macro with only the message. very cumbersome

First, you need a <wait.1> in between any actions, if you're combining Swiftcast and Raise into the same action.
Secondly, you need to hard-target whoever it is you're rezzing, if you only soft target, then they can be deselected between the message and the action.

[Gemina]

First, you need a <wait.1> in between any actions, if you're combining Swiftcast and Raise into the same action.
Secondly, you need to hard-target whoever it is you're rezzing, if you only soft target, then they can be deselected between the message and the action.

Yup, and just another reason why I don't use macros. They always end up biting me in the bum. This is what happened to me quite frequently when I tried a rezz macro. I will always express that such macros are not necessary, because you have no idea how your co healer's chat log is set up. If they've never applied filters, then the text is going to vanish as quickly as it shows up. IOW, there is a high chance it is going to get missed anyway and the problem will persist in PUGs. To rezz properly, you need to be paying attention to the status bars, which as a healer you should be doing anyway. You need to look for the rezz icon next to the player you want to rezz to see if it's already been done, and if it has not, the next thing you need to look for is to see if any player capable of rezzing is currently hard casting it. If the condition on both of these is 'no', then rezz the player.

OP, if you insist on using a rezz macro then tie the text to rezz itself and leave swiftcast completely out of it.

[gtasthehunter]

Could add wait.5 after the message you're about to swiftcast+raise and if someone else raises can change the target or cast a heal or something another thing I hate is during raids and someone dies all the way on the other side I seem to find them right away can't raise them and swiftcast runs out... there needs to be an easier way to find these faster! HP bar should still show up flashing or something or a color chosen by the player just for dead players!

I want a macro that can target players with 0 HP on ps4 it is really hard to cycle thru so many players out of the party that is! Namely needed in 24 man raids and Eureka! Even with a mouse, it can be hard when so many are walking over dead players I end up targeting the one moving around instead of a dead player!

[Tempest222]

Honestly that seems like a good qol thing. The reality is pugs are not going to be communicating enough to make sure they don’t overlap rezzes, and most people are not going to use any sort of macro to attempt to inform the party who they are rezzing, and that doesn’t always work anyway. I’ve frequently double rezzed a person even after waiting a few seconds to see if someone else was planning to get it, because obviously someone else must have had the same idea, and we both jumped on it at the same time. I’ve also double rezzed along side a person using a macro because my rez went out at the same time they were making their attempt.

[kidalutz]

My favorite thing is when both us healers are dead because people brought explosions over on top of us thinking that it would magically save them I guess and when it happens the two RDMs are still DPSing away on Omega then us Heals get blamed for the inevitable wipe.

[Risvertasashi]

why not just give an error message to everyone except the first person who landed the rez?

Probably the same reason benediction (or hallowed ground, etc) will go on cooldown even without having done any healing (or saving the tank from that buster).

I don't think SE has the technology to prevent overlap. No, I'm not joking. There's a noticeable delay between activation -> effect, and in the case of 2+ people doing at the same time, the effect wouldn't have registered yet and so I don't think it could block a subsequent rez.

[Zeromon]

There might be a way to fix this, but I doubt it. While overlapping rez may feel bad in most content wasting 20% MP really isn't that big of a deal. To avoid this I just wait a few second before rezzing. If there are multiple people dead I rez the ones lowest on the party list. I find that most people rez from top of party list to bottom of party list so this works most of the time.

[Canadane]

on a related note, i tried the basic "i'm rezing <t>" macro to inform everyone else who i'm rezing in order to avoid the above situation, and i found it to be inconsistent: occasionally the rez doesn't trigger, but the message always does, so i scrapped it and now i'm using the Raise action plus a macro with only the message. very cumbersome

Yeah macros are generally terrible for all battle content, raising included.
btw there's no zed in raise or resurrection.


However, back on subject, generally speaking a double or triple or 5x raise (thanks, RDMs) isn't the worst thing in the world. Because in situations where this happens, it's usually ocntent that doesn't matter. If it happens ins say, Savage or Ultimate, you already know who is going to be raising who, and when.