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

[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.

[Warlyx]

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

[Squrilruler]

Good fucking luck programming this. It will never happen.

[Skivvy]

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.

[Squrilruler]

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.

[Skivvy]

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.

[Akuryu]

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.

[PenutButter]

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.

[cgbspender]

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.