QoL for healers regarding Raise

[Pinen]

Needing Swiftcast to use Raise... it really sucks that it's wasted on the off-chance someone else raises your target first. I know people get around this by using chat macros, but this seems like a clunky solution (and sometimes very spammy).

The problem lies, I believe, with the tick delay on the server... IIRC there's a few-second window where someone might be raised but we can't see the buff icon yet, so unless the raiser spams chat, we have no idea whether to hold out or cast. I'd love to see something similar to any of the following changes:

1) Rework the Raise spell so that it auto-uses Swiftcast if it's up. Raise shouldn't work if your target isn't KOed or is rezzing. Even better, make it a toggle-able check box in Character Settings.

2) Allow Swiftcast to be executed while you're hardcasting Raise to complete the spell instantly. The combo would be Raise > Swiftcast and you wouldn't be able to raise non-KO'ed members or rezzing members.

3) If, due to server lag, you're executing Raise and your raise gets invalidated, roll back the swiftcast (if you used it) and Raise cooldowns.

I know people work out rezzing priorities and such in 8-mans and raids, but in content like The Hunt it gets quite a bit chaotic and I've wasted many swiftcasts trying to revive. Any thoughts?

[Risvertasashi]

Some of these seem like they might be difficult, from the technical side, for SE's devs to do. But all the same, I would love a more elegant solution to overlapping rezzes, or those cases where you caught it before overlapping the rez but you did already pop swift.

[Malmstrom]

Or!

Make the RDM do it.

[Risvertasashi]

Or!

Make the RDM do it.

Clearly you've never encountered the grey "I don't rez" RDM

[SieyaM]

I am pretty sure Raise doesn't work on a live or currently rezzing target already, but they do have to have already accepted the rez and been consumed by the glowy little rez ball.

[Cithaerias_pyropina]

A rudimentary fix, although probably not easy to program, could be to have the person who has the resurrection buff be untargetable. It wouldn't solve wasting swiftcast for a raise. But it would prevent someone from using swiftcast on a raise when someone already has the res buff.

[NobleWinter]

Nothing like seeing two glowy wake up calls hit the same person.

[Kraniel]

Small QoL idea, but i 100% agree to this. While wasting Swiftcast only is annoying but not too bad, when you also waste MPs over a raise, it becomes a bit too much in my opinion.
However i don't see a viable fix for this, since the raise buff only applies after the animation is finished.
(It would look something like "When trying to use raise on player X, check if player X has already been targeted by another player who is currently casting raise", which probably isn't reliable)

Some sort of "refund" system, like OP said, could be a good temporary solution at least.
So you would get back your MP/Swiftcast only if you tried to use raise on a target that has accepted the raise from another player or something.

I don't really see this being a high-priority item on SE's roadmap though ...

[Gemina]

One thing they could do that wouldn't fix it entirely but still be better than now is give Swiftcast back to the caster if the duration expires, and shorten its duration to 3 seconds. It wouldn't hurt to shave 5-10 seconds off the CD either.

Rezzing in this game is like a Mexican standoff for sure. Even SMN and RDM get in on the action. I am really not sure how to get around it mechanically. As a healer, you just kind of have to be aware when a player is KOd and fight the reflex to immediately SC+rezz.

[PondHollow]

How about:

If you raise someone who's already being raised, you receive a charge of 3 casts on Swiftcast.

3 might be too much or too little; I'm sure the devs can work out some compromise. It would be calculated to neatly make up for the time spent without creating an incentive.