How would you feel if Raises were instant and OGCD, but had a 60s CD?

[Eorzean_username]

This is something I was wondering about for a while, and seeing the (really good) Phoenix Down suggestion thread made me think of this again:

I know that some people love being the hero that keeps raising their Alliance Raid again and again, etc...

But I've talked to other RDM/SMN/Healers who kinda wish they didn't feel obligated to drop their rotation and sloooooooowly pick people up, or risk being seen as "not a team player"... even though they could just swap to a Raiseless Job and never be guilted about it.

Personally, I'm kind-of in the middle. I don't mind "saving the day", but I do start to get exhausted after a while when there's days where I really just want to shoot Verthunders, not stop every 20 seconds to Dualcast Verraise again while running my rotation on Lucid vapors.

I honestly find myself sometimes deliberately not queuing for certain kinds of content as a Raise-capable Job, because... I just... want to be left alone and do my rotation. Does anyone else have those kind of days?

And, it's kind-of weird that an entire Role Action — "Swiftcast" — is basically reserved entirely for just one Spell in most content. And if you actually spend that Role Action for a different utility purpose out of habit or impulse, you usually feel guilty about it shortly thereafter, as you sit there hard-casting yet another Raise.

How would you feel if Raises were split into two Spells:

• An out-of-combat Raise
  • Spell (GCD)
  • 8 second cast
  • No cooldown
• An in-combat Raise
  • Ability (OGCD)
  • Instant cast
  • 60 second cooldown

...allowing Raising Jobs to:

• Freely use Swiftcast for non-support purposes without potentially dooming a pull
• Freely continue their rotation without desyncing or disruption, even if someone needs to be Raised
• Not feel obligated to fix every single problem people create, because there's a hard limit on how many Raises can go out per minute

• "But then you'd be pressured to stack Raise DPS during prog to maximize Raises available"
• "But now some Alliance Raids will be too much trouble to clear"

Hmmm. Well, if these concerns become an issue, you could:

• Put a hard limit on how many in-combat Raises can be received per minute, via a partywide debuff, so that there's diminishing returns on stacking Raise jobs

or

• Allow the long-cast GCD Raise to be used in-combat, but make its cast time unaffected by Swiftcast (but now you're back to feeling obligated to sit there sloooooooowly hard-casting Raises)

or

• Just give every job Raise as a General Action like Limit Break and Sprint, so that every Job is now equally-capable of saving the day

[SaberMaxwell]

I'd prefer if raises were limited. It's like you say, as a rdm main there is a pressure to stop doing your job (dps) and instead raise someone, and God forbid you put it off because they died in your burst window where you've got 12.7-38.1 seconds of melee burst (depending on burst/2m/potted burst) where dropping at any point kills your entire burst.

I've seen harassment happen over it, not only to me but peers who play the job as well. I didn't pick red mage for its ability as rez mage, I picked it because I like the generator / spender gameplay combo'd with rhythmic stop/go to the beat of the fight gameplay.

As well, if prog becomes harder due to raise limitations...good? Prog doesn't need to be something one can just zombie their way through. This change honestly gives easier access to quick raise among the minimum 2 players than we have now. Yes I could see teams start trying to stack raise casters as an alternative, but you'd be forfeiting a melee slot (and a lot of damage) to do so and might miss enrage (definitely miss it in relevant content if ever 4 raises/min are needed). So it'd be a noobtrap crutch at that point imo.

[ryouma17]

any reason to remove swiftcast from my hotbar is a good idea to me, as a controller user i gotta pick an choose which abilities i use and dont use

[Gothicshark]

How would you feel if Raises were instant and OGCD, but had a 60s CD?

This is not World of Warcraft. So No. It was a bad design choice in WOW, it would be a bad design choice here.

[Coletergeist]

I personally think raising as it is now, works fine.

[SenorPatty]

Funnily enough, this rez design that is being suggested is what I actually expected when I came to this game. I've played so many mmos that had similar design, some putting a maximum amount of raises, some making raise once per battle or other variants. We have healers and two other jobs that rez so yeah, this is more than fine.

[Iscah]

I am fine with it as it is.

If you're a healer, it's your job, and as RDM you have a flexible rotation that can neatly throw raises between (and primed by) attack spells.

Far from resenting it, I miss having the ability in lower levelled content.

[Nihility]

raising works fine as it is but it's kind of annoying.
for skillful content an instant cast with a cooldown would work a lot better and be more meaningful but for lesser content like the 24 mans... In all honesty it feels like a lot of the player base has just fallen into this idea that they can just not learn any mechanics at all ever and expect to just be ressed over and over and over.

but then again if ressing was limited it would actually force people play better than 'not even trying at all' if they wanted to do stuff like 24 mans that effectively give endgame gear from extremely mechanically easy fights.

so I suppose I just talked myself in to being for the idea. An out of combat trigger for no cooldown should be a very easy thing for any studio to include anyways

[hagare]

Eh it's fine.
Now, if only verraise raises the white mana bar

[Kes13a]

I dont have any problems with how raising is now.

I do not feel that its inconvenient or "break my rotation" because as a healer, or a job with a raise ability.. healing, its part of my job. as an rdm, its a convenience if the healer is hard pressed or is low on mp. I dont play summoner so cannot address that.

basically, I am not a fan of the idea to change it into what you have outlined. in any of your case scenarios