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