Can Raise be fixed?

[Celef]

Or put basically :

Could we stop casting spells when they'll be inefective ? like raise on someone already raised or even spells on already dead mobs
Can believe we stil waste tima en MP on casting useless spells....

[Vstarstruck]

Or put basically :

Could we stop casting spells when they'll be inefective ? like raise on someone already raised or even spells on already dead mobs
Can believe we stil waste tima en MP on casting useless spells....

SE would need to change the netcode for that, the reason you can still do actions or cast stuff on dead monsters is because the servers are slow in confirming something happened.

[KisaiTenshi]

As the title suggests, can the raise spells be fixed so that if the target already has the effect, it cannot be reapplied by someone else. It's annoying as hell to waste swiftcast and the high MP to raise someone that already has it on.

Use the Swiftraise party game macro that tries every player after the player you targeted. If there's nobody to raise, then you've only wasted Swiftcast.

There should never be a circumstance in the game where you need to constantly be raising the same player, but it happens. Particularly co-healers in 24-player content, who get stuck in a loop of "recover, use refresh-die-recover-no mp to do anything-die on the next mechanic"

[Lukha]

I'll never understand people who actively argue against reasonable QoL requests. What's the point? Is it just to be contrary, or do they feel like the dev team somehow needs their protection from people asking them to do their job?

This would be a great fix to make, if they could find the time for it. Anyone who plays a Healer regularly has said a few curses over a wasted swiftcast. Macros don't really help if you both go to raise at the same time, or if there are multiple people down and you both target the same person.

[KisaiTenshi]

I'll never understand people who actively argue against reasonable QoL requests. What's the point? Is it just to be contrary, or do they feel like the dev team somehow needs their protection from people asking them to do their job?

This would be a great fix to make, if they could find the time for it. Anyone who plays a Healer regularly has said a few curses over a wasted swifter. Macros don't really help if you both go to raise at the same time, or if there are multiple people down and you both target the same person.

And what would you suggest, a refund of MP on any cast that fails? That is what this boils down to. If you cast raise/resurrect/etc on a player, there is already an icon that says they have a raise pending. It's not the developers fault players are unwilling to look at the player in the party before they start casting. The issue is really that Swiftcast is even a separate thing. Bake Swiftcast into raise, and have the swift part function like a proc, if you aren't raising someone every 60 seconds, it'll always be there.

[InkstainedGwyn]

I'll never understand people who actively argue against reasonable QoL requests. What's the point? Is it just to be contrary, or do they feel like the dev team somehow needs their protection from people asking them to do their job?

At least it's usually the same people, and once you see the pattern you can put them on ignore and then go back to actually discussing things that might or might not improve the game. My forum experience got a lot better after I started doing that.

[Vstarstruck]

I'll never understand people who actively argue against reasonable QoL requests. What's the point? Is it just to be contrary, or do they feel like the dev team somehow needs their protection from people asking them to do their job?

This would be a great fix to make, if they could find the time for it. Anyone who plays a Healer regularly has said a few curses over a wasted swifter. Macros don't really help if you both go to raise at the same time, or if there are multiple people down and you both target the same person.

Few things with this one, first of all people may resist a QoL change if it does not match their self interest, and Se is part to blame on this. "Server limitations" is hard over and over so people may feel the need to "fight" for their QoL wants over another because "Server limitations"

Having some kind of pop up is a bad idea since the game is slow with menus and such. I really do not have an idea how to address this from a programing standpoint other then do not cast raise right away, see if someone else does first, a sec or 2 not long then use it.

Have you tried not having your party members die?

Honestly it's part of the skill of the game.

Watch the other healer cast bar.
Watch to make sure target doesn't have effect yet.
Communication.

Having people not get oneshoted is part of the game too but that happens, healers cannot completely prevent someone from dying. (rescue has a recast too)
swiftcast raise has no cast bar
server latency and besides you both could hit it at the same time.
rarely works in pugs.

[hynaku]

One good thing about rdm can duel cast raise or your heal then raise to short it. But feel sorry for healers they only get swift cast with long cd. They should make it cancel spell if monster is dead or player has raise effect on them.

[JunseiKei]

One good thing about rdm can duel cast raise or your heal then raise to short it. But feel sorry for healers they only get swift cast with long cd. They should make it cancel spell if monster is dead or player has raise effect on them.

Bleh. I'd rather hard-cast a raise than have the RDM raise.

I'd rather SE just gave the healers a combat res that is instant and takes no MP. Can or cannot have a set number of uses (if no restriction on the number of available uses, place it on a cooldown, since most healers treat ressing as impossible without swiftcast anyway).

[CrystalRainbow]

Have you tried not having your party members die?

Honestly it's part of the skill of the game.

Watch the other healer cast bar.
Watch to make sure target doesn't have effect yet.
Communication.