Can Raise be fixed?

[Brightshadow]

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.

[Kurando]

Have you tried using a macro to inform your Party you are using raise? I mean i generally double check after using Swiftcast that no one else is going to do the Rez first, because if they do I can atleast use it for an aoe buff or something.

Technically any Rez is a temporary status effect and each time it's reapplied resets the timer, which can be used strategically in some situations.

[BillyKaplan]

Macros aren't a fail-safe way to inform the party. There's the enemy lines that mess it up, system messages, maybe your FC or linkshells spamming you, and not even sound effects are a guarantee since the game might be muted.

[Kurando]

Well it's kind of basic communication to be fair, unless you are playing with a static or on voice chat or whatever it really should come as no surprise if a another player makes your intended rez unless. Sure Macros aren't perfect but it's one way to inform the party rather than having to fix one minor status effect because some people get prissy that they waste MP (which unless you are doing content where MP is too valuable to lose then it's easily gained back again, it's really not the end of the world...).

It's annoying when another of the same job overwrites my buffs that have only just gone up (Litany, Devotion etc) but it happens you know, should they be blocked from being used until the timer expires? It's no different to Rez.

[BillyKaplan]

When you're in a full party, most often 24 player raids, you can have up to 7 players who can raise and not all of them will be able to communicate. That's a lot of mp going on that one poor soul who might not even be present there to accept the raise. And if it keeps happening, as it tends to happen in 24 player raids, your party's fubbernuked

[Kurando]

Unfortunately that's 24 man raids for you, and Eureka is even worse in that most players seems to be fight over who gets the rez out first to the dead target. Wasting a bit of MP in those raids sometimes cannot be avoided, you could do an alliance wide macro but again it may not work correctly or someone might ignore it/not see it. If nearly 7 players keep trying to jostle for the rezzes then eventually someone needs to use common sense and either just stop and let someone else do it, or say something about it in the party chat. MP management is really something that should be learned while progressing through the game, but I suppose that is a little too optimistic isn't it.

[Claviusnex]

Unfortunately that's 24 man raids for you, and Eureka is even worse in that most players seems to be fight over who gets the rez out first to the dead target. Wasting a bit of MP in those raids sometimes cannot be avoided, you could do an alliance wide macro but again it may not work correctly or someone might ignore it/not see it. If nearly 7 players keep trying to jostle for the rezzes then eventually someone needs to use common sense and either just stop and let someone else do it, or say something about it in the party chat. MP management is really something that should be learned while progressing through the game, but I suppose that is a little too optimistic isn't it.

The situation isn't going to be helped by having your own raise macro. The problem is none of the other players use a macro so everyone is working in the dark. If you display your party you will see a raise status by the player but there is often enough lag that you will still have multiple players attempt to raise. This is why the system is the best one to handle the decision of which raise executes and which is ignored.

I'm not saying it shouldn't be in the system, if enough players request it then that's fine, but what I'm saying is there is plenty of ways to communicate actions. Clearly MP management DOES have something to do with it otherwise no one would complain that they have wasted MP in doing so (like OP's thread), don't disregard something that was in the original post.

Well technically a player doesn't have to rez anyone, or they can do nothing but rez every single dead target they find... it's called a playstyle, but that's really for a different thread. Anyway, duplicate rezzes happen for whatever the reason, and communication is an option that's all. But going back to what I said earlier about overwritten status buffs, why should a player doing their job (let's say using Battle Litany) be punished because another player does the same thing at around the same time? Wasting a cooldown is no different to wasting MP on a rez, so if there ever was a fix for this "raise issue", then surely it should be across the board and not just on one thing.

I'm not that concerned about MP usage. It has more to do with wasted CD's. I waste one on a DPS because of duplicate raises and a few moments later need to raise a healer but it I'm on CD so have to cast a long raise and hopefully not die standing still for an eternity. Yes this could also occur where I was the only one doing the raises but in DF content it is more likely caused by duplicate raises.

[BillyKaplan]

Which is exactly why the request is to take that responsibility away from the players who have no easy way of handling it, especially in pugs, and put it on the system. MP management has nothing to do with it. Casting raise on a dead member of your party is what you're supposed to do, especially if no one else in the alliance communicated their intent of raising the same target as you. So why should you be punished for doing your job?

[Vaer]

They could just add a accompanying debuff called "Recently Resurrected: This player has been recently resurrected." This will stop players from being able to cast raise on said person while the debuff is active. The debuff is removed if the player cancels or accepts the raise or if the raise is somehow removed either due to dcing, etc. Make the debuff 10s or longer whichever works better. It should also not affect Healer LB3 (it should have priority so even if you have that debuff you still get the benefits of HLB3/auto raise).

It might not stop all cases due to how animations and buff/debuff activation work, two people casting it at the exact same time might still go through but it might stop some of the cases.

[Kurando]

I'm not saying it shouldn't be in the system, if enough players request it then that's fine, but what I'm saying is there is plenty of ways to communicate actions. Clearly MP management DOES have something to do with it otherwise no one would complain that they have wasted MP in doing so (like OP's thread), don't disregard something that was in the original post.

Well technically a player doesn't have to rez anyone, or they can do nothing but rez every single dead target they find... it's called a playstyle, but that's really for a different thread. Anyway, duplicate rezzes happen for whatever the reason, and communication is an option that's all. But going back to what I said earlier about overwritten status buffs, why should a player doing their job (let's say using Battle Litany) be punished because another player does the same thing at around the same time? Wasting a cooldown is no different to wasting MP on a rez, so if there ever was a fix for this "raise issue", then surely it should be across the board and not just on one thing.