Two Raid/Combat QoL Suggestions (Raise and Foe Requiem)

[Zyneste]

I'm sure there are other necessary QoL changes but these are pretty high on my list.

Raise

Raise, Ascend, VerRaise, and Resurrection all give the same effect of raise. Once you have a raise you don't need another. So why is it that the server still lets you cast raise on targets that have one already?

Losing a GCD, 15%-25% of your MP and burning swiftcast are all pretty big losses, but to do these things when they have been done 1 second before you is just anger inducing. Having the buff for raise should have a similar effect to being in a cut scene and reject the cast of others trying to raise the same target.

This has been an issue for as long as the skill has been a thing, so I'm just not sure why it wasn't addressed, other than maybe to create a false difficulty between communication of your party.

Foe Requiem


The second thing I want to bring up is Foe Requiem. Its a great skill, made better in 4.0 with the removal of the MP competition from old Army's paean and old Mage's Ballad. In places like raids and Eureka it has a habit of pulling bosses early, at no fault to the bard. They're just being a good bard and using their entire tool kit.

Why couldn't Foe Requiem be modified to only affect mobs who are within the radius AND have emnity with the bard. So casting prepull wouldn't cause the bard to accidentally pull the boss or to accidentally pull nearby enemies during light grind in eureka.

Anyone else think the same as me or know any other glaring QoL for the Combat system? Lol

[CorbinDallas]

Prepulling with Foe is the bards fault though, they need to time it better on the countdown. I agree with the raise thing though, it's annoying, macros don't solve anything either.

[BillyKaplan]

Once you have a raise you don't need another. So why is it that the server still lets you cast raise on targets that have one already?

To pamper that "raise strangers" achieve.
More commonly though you're going to see two people trying to raise the same person before the first Raise buff was ever cast. That's a race condition not even on the side of the servers, but the players, one that cannot even be mitigated by the use of macros and what not. And then what do you suggest happens? it's one thing to give you back your MP (which still will be tricky because of server ticks), but it's nigh impossible to give you back the swiftcast.

In places like raids and Eureka it has a habit of pulling bosses early, at no fault to the bard.

It absolutely is the fault of the bard, either for using the skill incorrectly, or being ignorant of how it works. I tanked in-progress an Aurum Vale once. The former tank left after the BRD kept agroing the first room in its entirety with Foe's. The guy didn't seem to realize he was the one agroing everything until the end of the dungeon. He was using his entire kit; he was still not a very good brd.
Good brds, and players in general, should know what their skills do, and radius those skill have. And I disagree that a BRD using Foe's before anyone pulled is a good brd. They're just burning their mp at best. to which you'll probably say 'well it shouldn't eat mp unless it's affecting anything!' to which I'll say - at what point do you realize you've moved from QoL to buffing the skill to the point of breaking it? Part of using Foe's Requiem is to know when to use it. It's not rocket science not to hit it in a room full of mobs before your tank/s grabbed them all.

Now I wouldn't really mind seeing either of this. I just don't think it'll happen because of a mixture of server limitations and, well. Dumbing the gameplay down too much.

[Paladinleeds]

Now, I could see the first one being useful especially for someone hardcasting raise. But, if you're swiftcasting it, then yeah, it's pointless. You won't get Swiftcast back which is how raises are mostly done by players (not so bad for RDM with Dualcast). So it'll still draw complaints of "But I lost my Swiftcast to that!" - to which I'll just say "Suck it up buttercup". As for the latter, Billy said it better than I could. It is literally just a "Git gud" issue.

[Zyneste]

Prepulling with Foe is the bards fault though, they need to time it better on the countdown. I agree with the raise thing though, it's annoying, macros don't solve anything either.

Yoshi P specifically apologized for fights like Sophia where a bard who did not specifically place themselves at the corner of the arena, would pull the boss, even if they backed up from the original starting spot.

Places like Eureka cause a bard to not even use the skill because of how tightly packed all of the mobs are. Are the any other skills in the game that can potentially pull a mob 40 yalms from the target?

Its silly and needs adjusted.

[Zyneste]

Now, I could see the first one being useful especially for someone hardcasting raise. But, if you're swiftcasting it, then yeah, it's pointless. You won't get Swiftcast back which is how raises are mostly done by players (not so bad for RDM with Dualcast). So it'll still draw complaints of "But I lost my Swiftcast to that!" - to which I'll just say "Suck it up buttercup". As for the latter, Billy said it better than I could. It is literally just a "Git gud" issue.

Yeah you won't get swiftcast "back" but you can spend it on something else and continue to keep your DPS up. I'm not asking to get swiftcast "refunded" just not consumed by raise if its already in effect.

Also raise your hand if you heal or RDM/SMN in savage content. (Or EX. anything like that is fine.)

[Paladinleeds]

Places like Eureka cause a bard to not even use the skill because of how tightly packed all of the mobs are. Are the any other skills in the game that can actually pull a mob who is potentially pull a mob 40 yalms from the target?

And maybe you just need to better position yourself in Eureka, and if you can't position yourself better, just don't use it. Like Billy said, part of it is knowing what it does and how best to use it. For some areas that can mean there's no good time to use it, so don't. It's an AoE ability, just like the others, just with a pulsing aura essentially (that differentiates it from others). So again, I see no needs for adjustments.

Also raise your hand if you heal or RDM/SMN in savage content.

o/ - WHM main in Savage. Going back to Savage again in 4.4 (currently on break due to static falling apart)

Yeah you won't get swiftcast "back" but you can spend it on something else and continue to keep your DPS up. I'm not asking to get swiftcast "refunded" just not consumed by raise if its already in effect.

That was meant more as an explanation, rather than trying to call you out there, so I apologise if I came across that way! Communication/social disability can really cause an issue at times. haha - but yeah, while it is true you can use it to keep your DPS up, most abilities on healers are GCD-length cast time or less, so you don't really gain anything, and still lose the Swiftcast. So it still becomes an annoyance.

[CorbinDallas]

Yoshi P specifically apologized for fights like Sophia where a bard who did not specifically place themselves at the corner of the arena, would pull the boss, even if they backed up from the original starting spot.

Places like Eureka cause a bard to not even use the skill because of how tightly packed all of the mobs are. Are the any other skills in the game that can actually pull a mob who is potentially pull a mob 40 yalms from the target?

Its silly and needs adjusted.

Again, said bard needs to time the activation of the song better, Yoshi and his apologies be damned. Just get good.

[Zyneste]

Again, said bard needs to time the activation of the song better, Yoshi and his apologies be damned. Just get good.

Didn't answer my question but thanks for your opinion! A yes or a no was all I was looking for. :]

[BillyKaplan]

Yoshi P specifically apologized for fights like Sophia where a bard who did not specifically place themselves at the corner of the arena, would pull the boss, even if they backed up from the original starting spot.

1. Source plz.
2. SE sometimes apologizes for things that are not their fault. A player's subpar performance is absolutely not something they should apologize for, they gave us all the tools to be able to perform at at least a certain level. Anything more or less is on us.