Please only allow one res to be cast on a person at a time

I always cringe when 3 healers cast res on the same person all at once.

This is something I can definitely get behind. Broadcasting macros don't exactly help when all of you are actually on the ball and end up casting it within milliseconds of each other.

Whats worse when all the healers use seiftcast raise on 1 person lol.

For once I support Lilyarel. Casting raise on a person with a Raise icon near their name should be the same as casting it on a person that's alive - it should be blocked.

I agree and signed. I suppose the best strategy atm us to maybe give a result order of who res's first, second and so on. After politely speaking with the healers.

Quote:

---

Originally Posted by mrmelgibson

I agree and signed. I suppose the best strategy atm us to maybe give a Res order of who Raise first, second and so on. After politely speaking with the healers.

---

Fixed.. on my phone and can't edit for some reason.

Excellent Suggestion

Outside of coil, it doesn't matter much. In Coil, communication is key. There is no issues lol.
"I'll get first raise unless I call you for it"
"I can't raise, can you get him?"
"My swiftcast is down"
"Hard rezzing"
etc

Quote:

---

Originally Posted by Skeith-Adeline

Outside of coil, it doesn't matter much.

---

Leviathan EX >_>

Anyway yeah I support this. It wouldn't be too hard to add, but it wouldn't save healers from blowing their swiftcast. They'd just have the opportunity to use it for something else. Like a medica II, or stoneskin, or Succor, or whatever :P

Quote:

---

Originally Posted by Skeith-Adeline

Outside of coil, it doesn't matter much. In Coil, communication is key. There is no issues lol.
"I'll get first raise unless I call you for it"
"I can't raise, can you get him?"
"My swiftcast is down"
"Hard rezzing"
etc

---

Some ppl can't type that fast in fights.
Whether its due to being on controller , slow typing or just not comfortable, something worse might happen imstead one dead guy on the floor.
Only i'll get first rez and u get 2nd seems likely to happen before the initial pull.

I love this idea, +1 from me.

It should work the same as casting Protect/Stoneskin on someone who is watching a cutscene, where it just cancels your cast.

I dunno how useful this will be. I mean I'm still going to waste my swiftcast before the game tells me I can't ress that person anyways. Meaning I wont' be able to ress the next person who dies for 60 seconds unless I get some downtime to cast the ress or the next person has died before my swiftcast duration is over >_>

Though it would save MP waste which has happened to me a lot. So this idea can't hurt anything.

Quote:

---

Originally Posted by Yumi_umi

Whats worse when all the healers use seiftcast raise on 1 person lol.

---

This feature would not take that away. You'd still need that 5 seconds of communication between healers before a fight. Else people would still pop SC and the raise just would not be casted, saved MP though which is nice.

However, this sounds to me people will get even lazier. The game helps them when this could be easily heard, seen and communicated within seconds. What's next, "allow one stoneskin", "allow no cures when someone is 100% HP", "allow one virus", "allow one storm's path/eye", "allow one dragon kick"? Well you've got the picture.

It cannot be helped. The first successful ress will proc, and other healers just have a miss on res.
If they were casting (aka no swift) they just can easily interrupt, if missed on ress and swift chewed, no luck even if res being blocked by the game, because the issue here is have your swiftcast gone for nothing.

I will always wait a few seconds before poping swift for a rez - but it depends on the other healer as well. If it's someone I know/trust I won't even look at rezing most of the time, if it's random df then I'll wait a few secs and if I don't see a swift on them I'll cast.

How is this going to work in practice? Unless it prevents you ressing someone while a res is already being cast, you're still going to get multiple people trying to res the same guy (and probably having already blown their Swiftcast to do so), and if it's done so you can't even begin to cast a res on someone who has one being cast on them, I can see an awesome new way for people to troll CT raids even more than they already do.

Losing Swiftcast is bad. Wasting MP is bad. Losing Swiftcast AND wasting MP is horrible.

Protecting against wasted Swiftcast is difficult, but protecting against wasted MP from a pointless cast SHOULD be easy. You're already blocked from casting raise on people that aren't dead - just extend that block to also include dead people who already have the Raise buff on. This is something SE really should do.

The only way I can think of to protect against wasted Swiftcast would be to restore Swiftcast's cooldown if Swiftcast is not used before its timer expires - but that might be overly generous. Saving abilities to use at the right time is part of the strategy of playing a game like this, not just for healers but for any job with buffs on cooldown timers. I'm not convinced this is something SE should do.

Quote:

---

Originally Posted by Brianmj

For once I support Lilyarel. Casting raise on a person with a Raise icon near their name should be the same as casting it on a person that's alive - it should be blocked.

---

OHHHH THE AMOUNT OF TROLLING I CAN SEE.

no seriously image it 6 healers in WoD and the main tank is dead everyone tries to res him but someone casts slow raise and cancels then slow raise and cancels D: and with the way most people act in WoD, i would imagine this on at least twice per run.

Quote:

---

Originally Posted by DracotheDragon

OHHHH THE AMOUNT OF TROLLING I CAN SEE.

no seriously image it 6 healers in WoD and the main tank is dead everyone tries to res him but someone casts slow raise and cancels then slow raise and cancels D: and with the way most people act in WoD, i would imagine this on at least twice per run.

---

I don't think that anyone is suggesting that you be blocked from casting raise if someone else is in the process of casting raise. You are only blocked if the person has the raise buff on them - raise has already successfully been cast.

So what if you start casting raise, and someone else finishes before you do? You should get the INTERRUPTED message and the spell should abort without casting, just like as if you're casting a nuke on a mob who dies before the nuke finishes casting.

Quote:

---

Originally Posted by LineageRazor

I don't think that anyone is suggesting that you be blocked from casting raise if someone else is in the process of casting raise. You are only blocked if the person has the raise buff on them - raise has already successfully been cast.

So what if you start casting raise, and someone else finishes before you do? You should get the INTERRUPTED message and the spell should abort without casting, just like as if you're casting a nuke on a mob who dies before the nuke finishes casting.

---

ohh i see, i misinterpreted :3 and i thought the game did do that (or is that if they take the raise before the spell finishes)

Quote:

---

Originally Posted by DracotheDragon

ohh i see, i misinterpreted :3 and i thought the game did do that (or is that if they take the raise before the spell finishes)

---

The Raise buff only appears if someone finished casting Raise/Resurrection on the person, not while the spell is being casted. It stays there until the dead person accepts the raise prompt.

Good fucking luck programming this. It will never happen.

Quote:

---

Originally Posted by Squrilruler

Good fucking luck programming this. It will never happen.

---

They had it working in XI, I don't see why they couldn't get it programmed for XIV.


And just to clarify, I mean that once someone has the raise buff on them, it's not even possible to start casting the raise spell on them.

Quote:

---

Originally Posted by LineageRazor

Losing Swiftcast is bad. Wasting MP is bad. Losing Swiftcast AND wasting MP is horrible.

---

this , blocking rez is a good idea , losing Swiftcast meh , u are saving it anyway for that REZ

i would love to see something to cancel the swift and get 30s back or something like that

I kind of agree with the post back on the first page... outside of coil does it really matter? Good teams in coil will have a line of communication, likely voice chat. If nothing else they'll have a rez order established. There is no other content in the game where you wasting a few seconds casting rez, or losing a bit of MP, is going to make any meaningful difference. It's a minor inconvenience, but it's not like the tank is going to get 1 shotted in World of Darkness because every healer decided to simultaneously hard-cast a raise.

Honestly the biggest waste in multiple raises is the loss of your swiftcast, and the ideas proposed here still won't help that.

Quote:

---

Originally Posted by Skivvy

They had it working in XI, I don't see why they couldn't get it programmed for XIV.


And just to clarify, I mean that once someone has the raise buff on them, it's not even possible to start casting the raise spell on them.

---

While that is possible, what would it accomplish that is helpful? That you can't use your wasted SwiftCast on a Rez? Isn't the point of this to STOP the waste of abilities? This does nothing. Don't add it. Waste of resources.

Quote:

---

Originally Posted by Squrilruler

While that is possible, what would it accomplish that is helpful? That you can't use your wasted SwiftCast on a Rez? Isn't the point of this to STOP the waste of abilities? This does nothing. Don't add it. Waste of resources.

---

I can't tell you how many times both healers in a group have swiftcast + raise on the same target, so now someone is out the MP for a raise. Most of the time the MP loss isn't a huge deal, but it's still annoying nonetheless. Even if this should be filed under a QoL issue, it doesnt mean it's worthless to fix.

Quote:

---

Originally Posted by Yumi_umi

Some ppl can't type that fast in fights.
Whether its due to being on controller , slow typing or just not comfortable, something worse might happen imstead one dead guy on the floor.
Only i'll get first rez and u get 2nd seems likely to happen before the initial pull.

---

Voice, not speech.

SE already said they're against making mechanics play the game for you. If both healer raise the same person (especially if at least one is hard rezzing) then the fault lies with them. This is hardly an issue if you play attentively.

Let s just stop dying. Mana saved, swiftcast saved, problem solved.
If players actually watched the fight, the number of death would be lessen x10.

Need more Upvote Buttons.

The problem does not exists.

Maybe I've worded wrong before, but stop casting a skill require zero effort and frankly I don't see the need to program the game to see a miss when you click on ress skill.

The real issue OP maybe wants address, is have three healers burning their swiftcast for a ress, and two of them being wasted.

Well, there are no means to avoid it: healers can cast swiftcast for any reason and it cannot be blocked just because someone died. I really don't care to have a miss on res because someone is ressing, but my swiftcast gone and done.

Quote:

---

Originally Posted by LalaRu

The problem does not exists.

Maybe I've worded wrong before, but stop casting a skill require zero effort and frankly I don't see the need to program the game to see a miss when you click on ress skill.

The real issue OP maybe wants address, is have three healers burning their swiftcast for a ress, and two of them being wasted.

Well, there are no means to avoid it: healers can cast swiftcast for any reason and it cannot be blocked just because someone died. I really don't care to have a miss on res because someone is ressing, but my swiftcast gone and done.

---

The lost MP from the raise is still a big problem. If you're having a messy fight in DF or PF, or WoD, and you're low on mana, having a wasted res is awful.

This is why all healers need Rez Macros. I've been getting very annoyed in groups because I waste my Swiftcast due to other healers not having a special macro.

Quote:

---

The lost MP from the raise is still a big problem. If you're having a messy fight in DF or PF, or WoD, and you're low on mana, having a wasted res is awful.

---

If you have low mana and other healers around, just don't ress. Don't burn your few remaining mana unless it is necessary to avoid a wipe.

Quote:

---

Originally Posted by LalaRu

If you have low mana and other healers around, just don't ress. Don't burn your few remaining mana unless it is necessary to avoid a wipe.

---

I kinda have to agree here. If you have 3 healers and your worried about mana loss, you have bigger concerns. Not a problem outside coil. In coil, communicate. That's part of raiding. Its an MMO. Its not meant to be played alone and without communication.

And yes, I have wasted my fair share of Swift Casts on healer to silly things like regen. I deal with it.