Raise... Please don't allow it to be cast on someone who already has Raise on them

When players get knocked out, they can have multiple Raises cast on them. For example, maybe the WHM instantly Swiftcast Raise on the BRD who just died. BRD doesn't accept, so a little while later the SCH casts Swiftcast Raise on the BRD as well. SMN gets the same idea at the same time, so both cast Raise within a couple seconds of each other. This BRD now has 3 Raises cast on them, even though really only the first one has "taken effect".

It would be nice if someone already had a Raise on them, that they have not yet accepted, that it wasn't possible to cast Raise on them anymore until the previous one wore off. It's an incredible waste of MP, especially for a SMN, whose MP management becomes perilous after more than a Raise or two.

At the very least, a very obvious cue that they already have Raise on them would be nice. I mean, I already blew my Swiftcast. I have to throw away a huge gob of MP, too?

I think this more boils down to party coordination as opposed to an in game issue. Make a macro with a sound to say you have raised the perhaps. Anyone else who casts it then is just being silly..

i get you dont want raise stacks but what about raise and resurrect?

SCH and SMN are both mentioned in the OP. It's quite clear that Raise and Resurrection are both implied to be under the same blanket term of 'Raise'.

Quote:

---

Originally Posted by Heavy01Mk2

i get you dont want raise stacks but what about raise and resurrect?

---

resurrect gives the raise effect. even says so when you cast it on someone. it shouldn't stack either

Quote:

---

Originally Posted by pikster

I think this more boils down to party coordination as opposed to an in game issue. Make a macro with a sound to say you have raised the perhaps. Anyone else who casts it then is just being silly..

---

That is true, but if you've got three people with quick reflexes (as most end game content requires) they're still going to all cast it simultaneously anyway, along with three noisy macros going off.

Pikster got it. It's called communication in parties. Lacking so much, can't even reply to hello when we start.

so yes, as he said, like me, I macro it with <se.1 to 16> Raise <t> /p Raising <t>

After that, its out of your control.

Waste and management of MP is through the group effort.

PUGs will be your worst nightmare, but at least with a macro like this, if the guys only wants to stay down and leech the kill, at least you'll know ^^

When I'm SMN, I state that I wil be the first one to raise. WHM need their MP on better things than someone who got 'LAG' ;)

Have fun.

Quote:

---

Originally Posted by Wildsprite

resurrect gives the raise effect. even says so when you cast it on someone. it shouldn't stack either

---

i think you missed my point. i was being stupid.

Also don't let us Virus the Virus Immune or Benediction the dead.

Don't let Surecast be wasted on numerous instant casts like Fluid Aura.

Also please make it so when you die, you get raised automatically and make all of the enemies' attacks do zero damage. And I want a pony.

XI (you know that ancient game that people love to see brought up) had managed to make this happen. For yeaaars, you could waste raises on people who already had it cast on them, but then they finally fixed it. Was awesome. These are the things that really make me scratch my head when I try to figure out why they weren't implemented in XIV. It's just a tiny thing, but saves massive frustration.

Also, if someone dies, why is my cure still going off on them? If a mob dies, why will my spell still continue to cast and only gives me the "interrupted" message at the very end of the cast?

Quote:

---

Originally Posted by Skivvy

XI (you know that ancient game that people love to see brought up) had managed to make this happen. For yeaaars, you could waste raises on people who already had it cast on them, but then they finally fixed it. Was awesome. These are the things that really make me scratch my head when I try to figure out why they weren't implemented in XIV. It's just a tiny thing, but saves massive frustration.

Also, if someone dies, why is my cure still going off on them? If a mob dies, why will my spell still continue to cast and only gives me the "interrupted" message at the very end of the cast?

---

bad thing is it was that way in this game until yoshi added in all of his changes for arr. you couldn't cast raise if it was already on the dead player.

Quote:

---

Originally Posted by darkstarpoet1

bad thing is it was that way in this game until yoshi added in all of his changes for arr. you couldn't cast raise if it was already on the dead player.

---

I had no idea! My time in 1.0 was very short lived >>;

Quote:

---

Originally Posted by Skivvy

I had no idea! My time in 1.0 was very short lived >>;

---

i was the opposite i spent more time each day on 1.0 than i do currently. there were many good things 1.0 did, but it was a disaster outside of those. i stayed and played so much because i loved the group i played with and they made the game enjoyable. sadly, most of them have quit since the game came back out.

If a (dead) player get a ress he will have a buff icon for that. Just check it before clicking on skill, to avoid the waste of a swiftcast.

When someone has raise on them, it should have a glowing phoenix down feather floating on top of them. This way the raisers know someone already has raise. Not only will this help in battle but also wouldn't waste people's time after fates or if they see someone on the road while on choco and they dismount, sometimes even change to healer just to raise and in the end person already has it.

I understand the whole issue of group coordination and such, but I personally don't understand the problem of adding something like this for the sake of convenience.

I wish they would allow paladin to raise while in a conflict.

It does not make sense to be locked out of the option to raise for paladin.

Quote:

---

Originally Posted by LalaRu

If a (dead) player get a ress he will have a buff icon for that. Just check it before clicking on skill, to avoid the waste of a swiftcast.

---

Works on paper, doesn't work when three people swift-raise at the same time (the point of OP).

Quote:

---

Originally Posted by HeroSamson

I wish they would allow paladin to raise while in a conflict.

It does not make sense to be locked out of the option to raise for paladin.

---

They will never do that. The reason for this is it would make paladin's favored over warriors as party members(tanks) since they have the useful utility of raising party members, leaving warriors who have no such skill to cross class on the wayside

This, this, this. Even with communication I always end up casting it at the same time as someone else. I have a macro that makes a noise and says "Resurrecting <insert name>" and yet as soon as my Res goes through, I see the animation of someone else casting a res. I always say, when I'm on SMN, I'll handle first Res, and will call out if my Swiftcast is on CD. And yet, some people just ignore that and go ahead and raise. It would save people a lot of stress etc if an error message came up saying that you can't cast it just yet.

If I see a SMN or SCH in the party and I'm a WHM I'll let them first raise and will wait a while before I'll trigger swiftcast. But I have seen this happen often... I will trigger swiftcast and then SCH and SMN will do so at the same time(the animation is hard to miss)... I'll let then one of them cast it and I'll do an AoE heal or protect if the person get's up fast.

Quote:

---

Originally Posted by LalaRu

If a (dead) player get a ress he will have a buff icon for that. Just check it before clicking on skill, to avoid the waste of a swiftcast.

---

And if you have two people casting at the same time? The other person's raise landing just before the one you cast does?

Quote:

---

Originally Posted by Skivvy

Also, if someone dies, why is my cure still going off on them? If a mob dies, why will my spell still continue to cast and only gives me the "interrupted" message at the very end of the cast?

---

The cure still goes off or the nuke because computers and specifically network connections are NOT instantaneous. This same thing happened in FFXI if the monster/char died right at the end of your cast. As long as the game requires a mix of local and server side inputs you're going to run into these little issues simply because sometimes one signal will arrive before another. "Fixing" it would likely create situations where you're interrupted while the monster is alive on your screen or a cure would drop and the person would still die because it only looked like they were still alive on YOUR screen.

This is a game where attacks can be performed on enemies that have already technically been defeated, and things like Hallowed Ground can be used while in the process of taking an attack that will deplete your HP to zero (in which case you will die anyway and your HG recast will still get used up, as we all know)

This is a big difference from how things ran in FFXI, where actions were executed instantaneously regardless of their animation length. The instant a target takes an attack that would KO them, they cannot be the target of any other actions, or waste any cooldown abilities in a vain attempt to save themselves.

This is something that would need to be addressed in this game if they want to do the sort of thing that you are asking for. Even if they were to tweak the Raise status so that you couldn't cast on someone that already had it, I'm sure it would not be able to do anything about multiple people swiftressing at the same time, because examples of this sort of thing occur almost every single time you fight something in this game. Basic example: hitting a near-death target with both an auto-attack and a weaponskill at nearly the same time, when either one or the other is sufficient to KO the target. In FFXI, only one or the other would occur; one would prevent the other from happening. This game will allow both to occur, and it will even show you the damage both actions did as a means to prove it.

Quote:

---

Originally Posted by necrosis

And if you have two people casting at the same time? The other person's raise landing just before the one you cast does?

---

Can't do much there because communication delay would likely still cause both of you to cast, especially if they're both Swiftcasted. Statuses are applied at the end of a cast so the second person's cast can finish in the time between the end of the first person's cast and the application of the "Raised" status.

Quote:

---

Originally Posted by Alukah

Works on paper, doesn't work when three people swift-raise at the same time (the point of OP).

---

wouldnt change a lot, you' get 3people use swift cast, one raise and the two other get a "can't cast " msg then an instant cast for their next spell.

3people trying to raise one player at the same time is just bad teamplay

1) yup, macro does not help with people using swift cast

2) last i knew, using a macro made the use of raise and swift cast unreliable ( did not go off ), but maybe thats fixed now


now of course, what we do is, just agree who has 1st 2nd and third raise. And honestly, after 3 raises, its a crap shoot after that since we are likely dead anyway

Sounds like we just have to live with the issue :( Bummer!

For all of those talking about communication, that's completely feasible for a static/close group, but in DF? I'm happy if I manage to get a "hello" from people. Maybe the tanks discuss who is MT, and then we're off :/

Quote:

---

Originally Posted by Hik0

wouldnt change a lot, you' get 3people use swift cast, one raise and the two other get a "can't cast " msg then an instant cast for their next spell.

3people trying to raise one player at the same time is just bad teamplay

---

While not ideal, this would still be an improvement over two people wasting a ton of MP for nothing. A wasted Swiftcast is bad, but a wasted Swiftcast plus wasted MP is so much worse.

Sure, communication is great, but being prevented from raising the raised would still be a nice feature for when communication doesn't happen, or someone panics, or whatever.

Quote:

---

Originally Posted by Hiruke

At the very least, a very obvious cue that they already have Raise on them would be nice.

---

they get a buff on them saying they have a raise waiting to accept, I've never missed it.

I like when I am in a random PuG and I swiftcast+Res someone WITH A MACRO MAKING ANNOYING SOUNDS IN CHAT yet my partner healer still proceeds to start and finish hard casting a resurrect. Looking at the buff/debuffs on the party frame must be hard for some people.

In cases like this, I think it'd be nice to make it so people can't cast resurrect on someone with the buff already. It'd save my sanity. xD

Quote:

---

Originally Posted by Elim

I like when I am in a random PuG and I swiftcast+Res someone WITH A MACRO MAKING ANNOYING SOUNDS IN CHAT yet my partner healer still proceeds to start and finish hard casting a resurrect. Looking at the buff/debuffs on the party frame must be hard for some people.

In cases like this, I think it'd be nice to make it so people can't cast resurrect on someone with the buff already. It'd save my sanity. xD

---

I'm probably one of those people that annoy you then. I rarely ever play with sound on (don't want to wake the baby), and when I'm healing, I don't tend to watch the party chat very often since my eyes are generally glued to the party bar or the ground. However, I DO know and look for the raise icon before casting. There will always be those times though that both healers swiftcast + raise around the same time, and can't do much then.

Quote:

---

Originally Posted by Elim

I like when I am in a random PuG and I swiftcast+Res someone WITH A MACRO MAKING ANNOYING SOUNDS IN CHAT yet my partner healer still proceeds to start and finish hard casting a resurrect. Looking at the buff/debuffs on the party frame must be hard for some people.

In cases like this, I think it'd be nice to make it so people can't cast resurrect on someone with the buff already. It'd save my sanity. xD

---

Something else to account for is delay, your raise might show a bit late on their screen.