Should there be a toggle allowing the cast of Rescue on someone?

[Komarimono]

Titania EX when someone screws up Phantom Rune, because they will most of the time run off the side. Granted, they should've moved ahead of time, but things happen.

When she spreads her wings, you move out, when she tucks them in, you move in. It's a tight timer ya, but simply looking tells you more then the AoE marker tells and before it shows.

[Doljax]

When she spreads her wings, you move out, when she tucks them in, you move in. It's a tight timer ya, but simply looking tells you more then the AoE marker tells and before it shows.

And yet, people still screw it up, which is a valid place for Rescue to be used that can't be covered with more healing.

[PeppermintBrown]

I've just stopped using it when I heal. Every time I thought i was doing someone a favor it turned out they had it covered. LIke on Omega M/F I thought the black mage was going to die standing in his circle when the knockback was coming, but turns out he'd surecasted it. So I've just stopped using it and if someone messes up they just die.

[Komarimono]

And yet, people still screw it up, which is a valid place for Rescue to be used that can't be covered with more healing.

That's when you simply let then die. If they can't avoid the mechanics of the encounter, how can they contribute properly? Using Rescue won't help them most times anyway due to the lag it has, I've seen healers try and use it on encounters again and again, not realizing the person is already dead and they are just going to yank a corpse due to the odd delay it has.

[Doljax]

That's when you simply let then die. If they can't avoid the mechanics of the encounter, how can they contribute properly?

Because nobody ever makes mistakes. Nobody ever has lag spikes. Letting someone who is otherwise contributing to the fight die is just stupid. Moreso when the tools to mitigate these circumstances exist.

Using Rescue won't help them most times anyway due to the lag it has, I've seen healers try and use it on encounters again and again, not realizing the person is already dead and they are just going to yank a corpse due to the odd delay it has.

I've rarely had issues with it, and I play with a ping of 150-180 ms. My static's healers, who play with between 110 and 140 ms pings, rarely have issues with it. It boils down to having the situational awareness and game sense to know when it'll be required, and/or should be used. If you're 'yanking a corpse', that's generally on the healer.

[StouterTaru]

This thread makes me miss the days of O-12 pugs, with the healer trying to Rescue me from the knockback, only to miss because my Surecast was up.

[AuraAstra]

I almost never use Rescue. When I do, my criteria are:

1. Is the player a DPS?
2. Are they within 3s of being hit by a damaging mechanic (I'm not going to try to save from knockbacks because of the ability lag mentioned by others) and obviously not minded to move out of it?
3. If they're hit by the mechanic, are they going to die?
4. Have they died to avoidable mechanics and been rezzed twice in the same fight?

If the player meets at least 3 of these 4 criteria (the last is mostly a judgement call), then I'm going to Rescue them. If they subsequently choose to run back into whatever danger I just pulled them out of, that's on them, and I'm not going to waste 1/4 of my mana rezzing them again. I'd rather spend it on the other 2-6 players in my party who didn't commit suicide to troll me and waste my mana.

[Nyr-NZ]

Title. Rescue has its uses, but sometimes it can do more harm than help for a player, such as interrupting casts or sending them into an AoE. While Arm's Length/Surecast allows for temporary protection against an unwanted use of the skill, it is not always up for situations that such might happen. Sorry if this has already been posted before.

Counterargument:
A toggle permanently disabling cast of Rescue on a given player could present the following problems: It could prevent the healer from saving certain players in danger, or make it harder to find and report those that abuse the skill.

Hi, sorry to message you here, but these forums don't seem to have a direct message option and your most recent threads are on the Bug Report forums where we cannot reply (direct @X89K1). I had a question about something you wrote related to DX11 errors. You wrote this in your other thread:
"I will try certain other options suggested soon. Trying to disable more Start-ups as there is no standard option(Task Manager is replaced by Process Explorer) for that on this PC, so it comes to disabling their Start-ups via an external program known as Autoruns. This should ensure the Cleanboot is actually clean.

Anyways the method to stop the variation of Fatal DX11 Error 11000002 mentioned was done by using overclocking programs such as MSI Afterburner to set the clockspeed BELOW its unaltered values, down to the stock/factory/reference clocks for the GPU.
You can check if a Fatal DX11 Error 110000002 was GPU clock related by going into Windows Event Viewer(found under Windows Adminstration Tools for Windows 10's start menu), going into Custom Views -> Administrative Events, and seeing if an entry that includes "Display" is listed with the following description:
"Display driver nvlddmkm stopped responding and has successfully recovered."
If such an Event Viewer entry is present at the time of the Fatal DX11 Error 11000002 crash, then the error is GPU/Driver related as a result of clock instability or driver issues."

I have had both the Fatal DX11 110000002 error and the other error with all the ffxiv_dx11.exe "An unexpected error has occurred" crashes (although the latter one only happened a few times, it's mostly the 110000002 error). I went into Event Viewer and found the exact Display error you mentioned. However, I have already underclocked Core Clock the max it can go on MSI Afterburner (-502). For a while it worked okay, but with Endwalker the multiple daily crashes have returned making the game unplayable. Is there anything else you'd recommend to fix the 110000002 errors? Should I also lower the Memory Clock on Afterburner? Thanks!

[Darthgummibear]

My only problem with rescue is that half the time it doesn't work. It needs to be more responsive and reliable.

[LittleImp]

In my experience, the vast majority of the people I encounter who gloat about rescue and using it to save 'stupid' people are bad at the game, and shouldn't be allowed anywhere near that ability.

I can't even count the amount of times I've been rescue'd into a deadly aoe or had my rotation ruined for no reason while playing BLM by some healer that is already struggling to even keep their GCD rolling, let alone do mechanics for other people.

There are exceptions, but they are so few that I think putting a toggle on the ability would be great.