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

[Nevaldus]

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.

[Elusana_Celah]

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.

[abzoluut]

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.

[LalaRu]

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.

[ruskie]

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.

[JimboTCB]

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.

[LineageRazor]

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.

[DracotheDragon]

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.

[LineageRazor]

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.

[DracotheDragon]

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)