Brainstorming Fun: Alternatives to Rescue

[MiaShino]

b]What would you replace it with?[/b] (And why is it a better option?)

First stuffs that must be stated. There is nothing that doth not involve moving another player that will ever be a better option. No matter what changes someone suggests we will lose something we had the ability to do and the versatility that accompanies it.

Imagine you are playing hmm, Starcraft 2 (have been playing this with the family much lately so tis on the mind). There is ability cast by motherships in there that creates black holes that suck up all the things. You can use this to protect allied units, disable enemy units, or even for setting up wombo combos. Now let us say we agree this is op as all heck! Tis primarily used to protect allied units soooooo replace with temp invuln shield. Alrighty! Now I have turned a highly powerful and versatile utility skill into binary boring box standard unit invuln. You cannot have one thing without the other.

Sucking up units has far more uses then giving units invuln even if it can be utilized as invuln. Invuln is binary thus used only to protect units that would parish or take damage without it. Phew! Had to say this because it is important to a Mia.

This hypothetical role action puts a Conditional Salvation buff on a player very briefly; let's say 5 seconds. If something would have killed them in that time, the buff procs and instead of dying, they are reduced to one hitpoint and slingshotted to the healer that offered them Salvation. It also includes a penalty; let's go with a 40% damage down for 30 seconds if it procs.

When we inevitably lose Rescue and let us face this we will. Am surprised we have been allowed the keeping of it for so so long already. Square hates anything non restrictive. Everything is make hp bar go down - raise allied hp bars - reduce damage by percent - etc. Easier to balance so there is understanding but I do not have to ficken like it. Your solution is the most likely one.

One; Reactive raise already exists within codebase in form of Pomander of Raising.
Two; Code for reactive skills already exists, think Excog.
Three; Prevent going below 1 hp code also already exists.

Slap all three together and you have reactive raise. We will not get reactive telewarp though because developing that would require additional time. Am willing to make wager on this can quote this Lala if I am correct in the future times. Heck number three is not relevant so can scrap that if we go with boring ol auto raise.

Now finally.. many apologies I kinda type a lot. Your suggestion is mostly dumpstered on arrival.

In higher level content (Savage+) and even most lower level content skilled players avoid anything that has potential to cost uptime/deeps. Just like avoiding old pre dps neutral Lily spells a skill that causes someone to eat 40% damage down will be avoided as much as can be. Whole reason why rescue = better is from its ability to prevent the weakness debuff and uptime loss of raising for both dead player and healer. Damage down portion has to go or be augmented or the skill goes from "Sweet! It worked!" to "Ugh, guess I will slap this on them instead of burning Swift".

How does it slingshot the player?

If it works as current Rescue does will it move player to current position or previous position upon cast?

Both have potential to be most bad. I identify that player A is not going to survive mechanics and shall experience demise. Wish to use Conditional Salvation on them but it will yeet them to me however there is kill wall/chasm between me and player A. Gotta reposition before casting or make certain I do not reposition until they experience demise which miiiight result in my going splat. It will have to function like raise so again we return to reactive raise.

Most biggest reason why it would insta flop especially in higher level content is how fricken punishing being out of position is there. One player not correctly positioned in Dragonsong Reprise results in tpk 95% of the times. If it becomes reactive raise without the yeet portion welp.. now the dead player is not in position for mechanic X so wipe time! If it retains the yeet but you must position for mechanics now you are dragging someone somewhere they should not be and that is a wipe again.

All of this is mostly irrelevant in casual content but thought twas worth the mention because current Rescue has value in both casual and high level content where this new skill would not.

In a world where Rescue must go bye bye I instead propose that it be replaced by reactive raise or interrupt with additional conditions;

Square ceases using the restrictive moniker Healer and switches the role to being called Support. Prevention is key part of being doctor after all! It is most important part actually especially when the alternative is surgery. They must stop viewing healers in this binary, restrictive, bland way they do as resource to make the hp bars go up or prevent them from going down as much. It is.. dreadfully boring. Despite this being easiest thing to balance around they are not even very good at it.

Just look at the new Ultimate! No room for triage there. Everything is insta kill so only healing needed is so scripted you could use third party tools to call it out or push the buttons for you. If this is future direction we are stuck proceeding in then we do not need more heal buttons or raise buttons.

What we need are more skills like Rescue and Expedient. That is final stipulation for me! Remove three+ heal buttons from every healer and replace them with unique skills similar to Expedient. Something beyond |Reduces damage by %| or |Heals by X amount of potency|.

If they do this I would begrudgingly accept the removal of my Rescue. No no they do not have to move someone like Rescue just.. be anything other then another mit/shield/hp go up button. Anything is more unique then that. I want support closer to Lucio from Overwatch (He was my favorite! Will shill for Lucio).

[Calysto]

Here's an idea :

New "general" action : HALP!!!
-give the user a halp buff for 2s
-make a big marker appear above target head
-recast 60s ?

Rescue :
-enabled ("trigger" effect) when a party member is under halp buff
-pull party members within 30' to you if they have halp buff and remove it
-recast 30s-90s ? maybe with charges

Solve some problems and create others.
The healer won't pull you to your doom anymore, but if you want to be saved you better beg

[Packetdancer]

First off, I definitely agree that Rescue hypothetically has a number of interesting uses. I have frequently used it for uptime cheese in Susano, for instance; before the pull, I mention "Hey, if anyone other than me gets the knockback and stack marker, don't run after them; I'll just rescue them back into melee range as the knockback goes off." Folks go "Cool, sounds good." And we do that. Yay?

But Rescue is janky and unreliable, and the vast majority of interesting uses are thus impractical. Outside of the aforementioned "grab your co-healer and bring them to safety while they're in LB3 animation lock", I almost never see Rescue used in savage or extremes. (I won't say I don't see it at all, but it's extremely rare.)

One; Reactive raise already exists within codebase in form of Pomander of Raising.
Two; Code for reactive skills already exists, think Excog.
Three; Prevent going below 1 hp code also already exists.

Slap all three together and you have reactive raise. We will not get reactive telewarp though because developing that would require additional time.

Buff/debuff-based 'zip to this spot' code actually also already exists in the game; it was a fairly key element in phase 2 of E12S last tier, with a number of "Relativity" mechanics that forced you to resolve multiple mechanics in a specific order without the mechanics happening, at which point you would be rewound to the positions snapshotted at the time the countdown had expired for that step. That would (in theory) not be terribly hard to repurpose.

Am willing to make wager on this can quote this Lala if I am correct in the future times. Heck number three is not relevant so can scrap that if we go with boring ol auto raise.

Now finally.. many apologies I kinda type a lot. Your suggestion is mostly dumpstered on arrival.

In higher level content (Savage+) and even most lower level content skilled players avoid anything that has potential to cost uptime/deeps. Just like avoiding old pre dps neutral Lily spells a skill that causes someone to eat 40% damage down will be avoided as much as can be. Whole reason why rescue = better is from its ability to prevent the weakness debuff and uptime loss of raising for both dead player and healer. Damage down portion has to go or be augmented or the skill goes from "Sweet! It worked!" to "Ugh, guess I will slap this on them instead of burning Swift".

As someone who raids savage, I would argue that if the alternative is "you died" (thus 90 seconds of rez weakness), the 30 seconds of damage down is, while not ideal, still the preferable option. And without that damage down -- with no downside to the ability -- you turn Conditional Salvation into functionally "Holmgang, but the healer can put it on anyone."

Which is interesting, I won't lie, but two healers able to functionally apply Holmgang to any party member... that strikes me as having a reasonably high chance of very quickly becoming a thing predominantly used for Large Cheesing where mechanics are concerned.

(And I personally would prefer not to encourage more things like the P1S "braindead" tank damage down strat for Intemperance. Why is this a thing.)

How does it slingshot the player?

If it works as current Rescue does will it move player to current position or previous position upon cast?

Both have potential to be most bad. I identify that player A is not going to survive mechanics and shall experience demise. Wish to use Conditional Salvation on them but it will yeet them to me however there is kill wall/chasm between me and player A. Gotta reposition before casting or make certain I do not reposition until they experience demise which miiiight result in my going splat. It will have to function like raise so again we return to reactive raise.

That one's easy enough to fix: if the buff is triggered and slingshots the player, grant them 5 seconds of Transcendent, as though they'd just been rezzed. (Transcendent being the temporary invulnerability to all damage you have immediately after rez.) This would let them still be brought safely to the healer's side even across the bad, and give the healer a moment's breathing space to heal them up again as well.

(Hell, even if nothing else about Rescue changes, I'd argue that giving them Transcendent for the duration of the Rescue-slide would do wonders for reducing people's annoyance with it, since at least you wouldn't be dragging them through death zones and potentially killing them regardless.)

Most biggest reason why it would insta flop especially in higher level content is how fricken punishing being out of position is there. One player not correctly positioned in Dragonsong Reprise results in tpk 95% of the times. If it becomes reactive raise without the yeet portion welp.. now the dead player is not in position for mechanic X so wipe time! If it retains the yeet but you must position for mechanics now you are dragging someone somewhere they should not be and that is a wipe again.

Oh believe me, as a healer main, I am painfully aware of how one person being out of position causes large problems in a lot of higher-end content. In the current savage tier, for instance, much of P4S phase 1 is basically "Proper Positioning: the Fight", while phase 2 is basically "Proper Positioning II: Position Faster, with Tethers".

But I have seen Rescue used very, very rarely to correct positioning in high-end content, because there's rarely time. Are you going to run to the person's spot, Rescue them there, then move back to your own spot? Rescue is not reliable enough -- or fast enough -- to run to the right spot for a position-based mechanic, Rescue, then run back to where you need to be in the vast majority of cases.

(Disclaimer: I will admit there are exceptions. I had one run of P4S in PF not long ago where a DPS had been disoriented by rez and happened to be standing in my orb spot, and was clearly tunnel-visioning as they did not seem to notice both of us were there. So I ran to theirs. If I had stayed there, we both would've been popping the wrong orbs and would die, but since they were specifically out of position in my spot I was able to use sage's Rescue + Icarus trick to switch our spots in time. However, I'd argue this -- and almost any situation where you use Rescue to correct positioning in savage, save for rescuing your co-healer from LB3 animation lock -- is an edge case.)

And if someone is dead for the mechanic, that often also causes it to fail. Someone's dead and can't soak a tower? Welp, that's a massive raidwide. One of the healers is down? Now it's time for the fun guessing game of "who gets the other stack marker". One of the DPS is dead for Darkened Fire in P3S, and it was DPS the fires were dropped on? Better hope the random person selected to receive the fourth fire is their tank/healer partner, 'cause otherwise that fire gets dropped smack on top of another one, the two tether, and you all die. Etc.

The number of situations in which someone being repositioned would be worse than someone being dead for the mechanic is, I suspect, not a large one. (Though I'll admit it is also a non-zero value. The Flare/Stack/Donut/Spread mechanic in Endsinger EX would be one; while still telegraphed when someone is down, the mechanic does not actually go off if the targeted player is KO'd at the time. Having a DPS with Flare alive but zipped to where the healers and tanks are stacked would end Poorly.)

Conversely, the number of situations in which someone being repositioned but still alive is better than death is probably a bigger number. Especially since Conditional Salvation could save someone from, say, P4S rot/tethers if they have the wrong thing; Rescue can't really do anything there except ensure they die in a different spot.

(Well, okay, you might be able to Rescue them to you if you are specifically supposed to have the tether they have, and then run away with it, but given how wonky Rescue is, I'd not place high odds on being able to do that and get far enough away afterwards that the tether-blast doesn't kill them anyway. And if it's a tank who has a tether when they shouldn't, that means you shouldn't either, so Rescue would just actively make things worse by bringing the "this will kill tanks or healers" blast straight to you.)

I don't think Conditional Salvation is necessarily the ideal solution -- or even necessarily the right solution. And it definitely doesn't allow some of the creative uses Rescue would, though it does also allow you to save people in places that Rescue wouldn't.

But if we were going to replace Rescue, I think Conditional Salvation wouldn't be a bad option as one possibility. And I don't think the issues you mention having with it are ones that are insurmountable.

[Nethereal]

I want to point out that if rescue just instantly teleported you, it would be too easy to keep going and run into things. The brief time sliding actually lets you register you've been moved so you can shift gears accordingly.

Sounds like a skill problem.

Teleport or not, not being able to move for 0.5 seconds/ 1 second half s enough time for to understand what’s happening.

The teleport/retrieval orbs was more of a visual thing to begin with since as someone getting grabbed it was effectively the same animation as getting grabbed as far as your screen was concerned.

The only time it would be hard to stop is if you were extremely zoomed in.
In Tera they also displayed on the screen if you were locked on from a party member, it also played a sound.

[MiaShino]

First off, I definitely agree that Rescue hypothetically has a number of interesting uses.

Watching friends use it blows the mind at the times. It really really does! Any skill that can move self or players brings me happiness.

But Rescue is janky and unreliable, and the vast majority of interesting uses are thus impractical. Outside of the aforementioned "grab your co-healer and bring them to safety while they're in LB3 animation lock", I almost never see Rescue used in savage or extremes. (I won't say I don't see it at all, but it's extremely rare.)

Have been watching some groups doing current tier and Dragonsong and almost never see it. I did count many many times it could have been used though. I wish to say this has more to do with not thinking about it or being unwilling to risk messing with the other player. Same same for the last extreme. Sooooo many times Ferro could have done some stuffs with few clever Rescues. Juuuuuust in the recent vod there were three times the Ninja (think it was the Ninja) failed to get into position after the two tethers and Ferro could have easily done drive by Rescue to put them in the correct position.

Buff/debuff-based 'zip to this spot' code actually also already exists in the game; it was a fairly key element in phase 2 of E12S last tier

I almost forgot to remember that! Can just retroactively put this as Four; annnnd nope nope cannot imagine it would be difficult to repurpose. Well.. it should not be at the least.

As someone who raids savage, I would argue that if the alternative is "you died" (thus 90 seconds of rez weakness), the 30 seconds of damage down is, while not ideal, still the preferable option. And without that damage down -- with no downside to the ability -- you turn Conditional Salvation into functionally "Holmgang, but the healer can put it on anyone."

Aye, agreed. It must have some "drawback" to balancing it. Am not much of the fan of harsh negative re-enforcement because it always feedback loops into "Guess I will avoid this at all costs and reluctantly use it if I must". I do not much care for how raising works in FF14 land either for this reason but that is whooooole other can of worms. 40% damage down is rough though especially if it happens during buff windows. Youch! Perhaps a vuln up on the target instead or excog like effect so it cannot be used to cheese one shot mechanics? Boy is game design not fun huh!

Which is interesting, I won't lie, but two healers able to functionally apply Holmgang to any party member... that strikes me as having a reasonably high chance of very quickly becoming a thing predominantly used for Large Cheesing where mechanics are concerned.

Mmhmm! Heck yeah it would be. Am already thinking of ways I could cheese things with it. Tank invuln is already incredibly powerful especially Holmgang with the shorter cooldown. Can already see the healer takes mechanic and 40% damage down strats because welp, our damage output is less so less total detriment to party deeps.

(And I personally would prefer not to encourage more things like the P1S "braindead" tank damage down strat for Intemperance. Why is this a thing.)

My uncle is one of the extended family mmo veterans and as he places it; "If they can find ways to ignore mechanics they will every time."

That one's easy enough to fix: if the buff is triggered and slingshots the player, grant them 5 seconds of Transcendent, as though they'd just been rezzed. (Transcendent being the temporary invulnerability to all damage you have immediately after rez.) This would let them still be brought safely to the healer's side even across the bad, and give the healer a moment's breathing space to heal them up again as well.

Am more concerned with the way movement skills work in FF14. All of them even jumps are only accelerated direct line movement. Sooo dragoon cannot backflip over ledges, they will plummet like ten thousand pounds of sadness. Square should really fix this anyway and allow certain movement skills to circumvent falling into pits like Swtor did. Hmmm now that am mentioning this.. if Rescue pulled you over holes or failed to pull full distance if the player would fall that would resolve massive point of contention.

(Hell, even if nothing else about Rescue changes, I'd argue that giving them Transcendent for the duration of the Rescue-slide would do wonders for reducing people's annoyance with it, since at least you wouldn't be dragging them through death zones and potentially killing them regardless.)

Movement skills have some of the wonkiest fricken snapshotting probably due to low server tickrate. Target of Rescue is moving significantly faster then they would normally be allowed to move. Server only snapshots every 300ms (best of the luck timing that in the mind!). If they are passing over mechanic during the 300ms window they will be snapshot in the mechanic and die upon arrival (I rescued a corpse again.. yay). Temperence would be amazing addition to Rescue. Have seen friends mastering this and it is something. Do not ask a Mia how because I am not big brained enough for that!

But I have seen Rescue used very, very rarely to correct positioning in high-end content, because there's rarely time. Are you going to run to the person's spot, Rescue them there, then move back to your own spot? Rescue is not reliable enough -- or fast enough -- to run to the right spot for a position-based mechanic, Rescue, then run back to where you need to be in the vast majority of cases.

Was going to mention the Icarus + Rescue to change places but you got it. That trick gives me the happy chemicals. Maahhh.. the more I think about that the more I miss my Sorcerer. Just.. just look at this skill; https://torcommunity.com/database/ab...a6/phase+walk/

This is an ability healers have. Healers! Properly timed you could cheese mechanics with this by being in two places at once but it took fair degree of skill.

(Disclaimer: I will admit there are exceptions. I had one run of P4S in PF not long ago where a DPS had been disoriented by rez and happened to be standing in my orb spot, and was clearly tunnel-visioning as they did not seem to notice both of us were there. So I ran to theirs. If I had stayed there, we both would've been popping the wrong orbs and would die, but since they were specifically out of position in my spot I was able to use sage's Rescue + Icarus trick to switch our spots in time. However, I'd argue this -- and almost any situation where you use Rescue to correct positioning in savage, save for rescuing your co-healer from LB3 animation lock -- is an edge case.)

Yup yup! Perhaps I am the strange one but I live for these moments and know I am not alone in this. Fricken love watching friends/family find these rare instances where they can make a skill shine. As stated previously I still feel these moments are more rare because others are generally pre-positioning in higher end content and on average (pffff) more skilled players. Or are not thinking about it. Follow the dance > go to your waymark > return to set position > etc can become monotonous. The mind is filled with doing the set routine so without even realizing you stop thinking about ways to improvise.

And if someone is dead for the mechanic, that often also causes it to fail. Someone's dead and can't soak a tower? Welp, that's a massive raidwide. One of the healers is down? Now it's time for the fun guessing game of "who gets the other stack marker".

Aye Akh Morn says hello! That is other rant shall not get into but am not a fan of the way Square designs more "difficult" encounters. Too much "we wipe now" not enough "this is bad but I can recover". Would love to see them lean more into what Swtor did well. Did you know you can cloak the whole party and walk past entire flashpoints (dungeons) in there? Tis neat! Or rescue skip by platforming onto various objects? Or reduce certain mechanics by using optimal movement tech? Could go on and on and on..

The number of situations in which someone being repositioned would be worse than someone being dead for the mechanic is, I suspect, not a large one. (Though I'll admit it is also a non-zero value.

This has caused more thinking to occur. Would it be too powerful if your skill allowed you to cancel the yeet part by pressing the button a second time? That would probably neutralize many issues and I could have said this at the beginning of my post and saved much of the typing. Ohhh well. Too late now!

But if we were going to replace Rescue, I think Conditional Salvation wouldn't be a bad option as one possibility. And I don't think the issues you mention having with it are ones that are insurmountable.

Certainly not! Hmm. Actually would not mind just fricken having this skill as healer going with my last conditional for "Pls add more unique buttons for the healers!". Could say umm how about Fairy lands on target and saves them for the Scholar one. Sage deploys their Nouliths. White Mage remembers the forgotten art of water manipulation (think creating a wave then woooooshing the target). Astro had time manipulation magic so pretty darn easy to explain how they could do it. Still lore friendly too! Mia approves.

If this thread does anything it demonstrates why game development is done by teams (usually) and not individuals quite well indeed.

Shall stick with what I said at end of other wall of words and letters. Do not feel replacing Rescue is the correct answer even with a skill that is almost as good without giving us something extra in return. Perhaps your Conditional Salvation skill could be one of those additional skills.

TL;DR - You can take my Rescue but give every healer three unique skills in return. Brownies are tasty but would have appreciated it if you did not take my cookies away.

[Packetdancer]

Congratulations, I think you may be one of the only people I've met that can out-do me for post length. (I'm not sure whether this counts as a good thing or bad thing, but it's definitely a thing.)

Gonna keep my own reply succinct for once, though, because I want to go get a snack prior to raid.

Have been watching some groups doing current tier and Dragonsong and almost never see it. I did count many many times it could have been used though. I wish to say this has more to do with not thinking about it or being unwilling to risk messing with the other player.

I'm gonna guess a combination of "this content is kinda dicey" and "Rescue is basically an enormous pile of unpredicable behavior and janky timing that happens to have been given a name and a button you can add to a hotbar."

My uncle is one of the extended family mmo veterans and as he places it; "If they can find ways to ignore mechanics they will every time."

He ain't wrong, either.

Am more concerned with the way movement skills work in FF14. All of them even jumps are only accelerated direct line movement. Sooo dragoon cannot backflip over ledges, they will plummet like ten thousand pounds of sadness.

I agree this is irritating. It's doubly obnoxious because the NPCs can use the skills in that fashion. If you use Thancred in trust mode, there's at least one dungeon where he will Shukuchi across a death pit to skip the mechanic. (As a gunbreaker, no less. So evidently he still has access to the cross-class skill system!)

Movement skills have some of the wonkiest fricken snapshotting probably due to low server tickrate. Target of Rescue is moving significantly faster then they would normally be allowed to move.

To be fair, a lot of online games have terrible movement gotchas. Most are just better at counteracting (or at least concealing) them than FFXIV is.

(This is on my mind of late because I've gone back to doing game dev -- this time in my spare time instead of a day job -- and am in the middle of doing a parkour-influenced movement system which works in multiplayer. My network prediction and correction code works, but I desperately want to find a better design so that it is not pain to add new traversal moves to the locomotion system. I half-jokingly regret whichever recent life choices led me to this place.)

Too much "we wipe now" not enough "this is bad but I can recover". Would love to see them lean more into what Swtor did well. Did you know you can cloak the whole party and walk past entire flashpoints (dungeons) in there? Tis neat! Or rescue skip by platforming onto various objects? Or reduce certain mechanics by using optimal movement tech? Could go on and on and on..

Yep. I did play SWTOR, and quite enjoyed Flashpoints.

It has actually been years, but I do seem to recall that in 1.x it was actually also a viable option to sleep certain enemies to sneak past them. (I may be misremembering, though.)

But that sort of aggro management and crowd control only really is relevant in solo deep dungeon runs these days.

If this thread does anything it demonstrates why game development is done by teams (usually) and not individuals quite well indeed.

My old saying back when game dev was my day job was "Nothing should be designed by committee, but everything should be refined by one." It was half-joking, but not entirely. Having one vision/voice designing the core of something makes it more coherent... but having lots of eyes on it and discussion about it afterwards helps refine it into something better.

[TaleraRistain]

Give target party member a 500% speed increase for 3 seconds. Bind yourself in place for 3 seconds.

A healer standing in a safe spot can still aid someone who is in a sticky situation. A healer who has run ahead of the tank in a dungeon can still help the tank to catch up. If it cancels animation lock, a healer could also use it to help a dps get to safety / get back to dps'ing after a limit break.

What the healer would not be able to do is intentionally pull someone where they don't want to be, like an aoe or off a ledge. Some healers pat themselves on the back for "saving" a melee dps by pulling them away from boss without realizing there was another safe spot in melee range. That would also be prevented by this change.

I like this idea. It puts agency back in the other player's hands rather than having it removed by someone else. Packetdancer brings up a good point about healer LB3 but the argument could be made there that Rescue is being used as an exploit, since the animation lock is intentional design and means a healer either should be making sure they're in a safe spot or their party should be prepared to sacrifice them for the LB3. And I don't think it's a strong enough argument to negate turning Rescue into something that doesn't allow one player to control another.

[Sebazy]

Give target party member a 500% speed increase for 3 seconds. Bind yourself in place for 3 seconds..

Any particular reason behind the healer being rooted for 3 seconds beyond your clear hatred for the role?

[Rein_eon_Osborne]

Give target party member a 500% speed increase for 3 seconds. Bind yourself in place for 3 seconds.

I can already see how this can be used to ‘grief’.

See BSF’s action: Lost Impetus. Ever met those player who actually got killed by running into death zones because they never expected the speed boost?

[Droxybrobotnik]

Here's an idea :

New "general" action : HALP!!!
-give the user a halp buff for 2s
-make a big marker appear above target head
-recast 60s ?

Rescue :
-enabled ("trigger" effect) when a party member is under halp buff
-pull party members within 30' to you if they have halp buff and remove it
-recast 30s-90s ? maybe with charges

Solve some problems and create others.
The healer won't pull you to your doom anymore, but if you want to be saved you better beg

Brilliant. We'll have the ff14 version of being a medic in team fortress 2