Instead of removing it, change it so we can use it out of battle. It would be infinitely more useful then!

Instead of removing it, change it so we can use it out of battle. It would be infinitely more useful then!

Do we need an even number of role skills? If an ability is functionally useless, it should either be made useful or removed.
For example, Repose, Foot Graze, and Leg Graze are borderline useless.
If Repose wasn't required for a role quest, I'm not sure where I could see a current application for it. Since most mobs in Heavensward+ dungeons are straight up immune to it.
The most I could see Foot/Leg Graze used is in open world. Unfortunately these aren't very useful for that since Brd/MCH/Dnc don't have issue killing mobs. Additionally, kiting is notoriously bad due to the short leash range of mobs in this game.
Regarding Rescue itself, it needs to be updated. With game ticks, most lethal effects will still kill the target anyways due to the slow response of the inital effect + the drag time.
It would be more useful if it didn't move them, but served as a Super-Esuna/Reraise with a short duration(6s at the most) allowing for removal/temporary debuff protection from any debuff/effect and essentially acting like a Living Dead with an auto Benediction that ends the effect. Of course a raid wipe mechanic would circumvent this.
This way it would protect against/remove knockback, confusion, vulnerability, and even weakness effects, while removing the ability to grief other players. Bump the cooldown up to 300 seconds, maybe even longer so it isn't abused, to balance the changes out. If Rescue is needed more frequently than that, especially considering raids have 2 healers, a more significant problem exists.
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.


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.

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.
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: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.
"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!
My only problem with rescue is that half the time it doesn't work. It needs to be more responsive and reliable.
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.

Agree 100% here. There are fights I've done hundreds of times where I know a KB is coming, but on BLM I'm squeezing out that last F4 before moving. Don't plan my movements for me. Also, people don't learn by getting yanked around. Let people fail, that is how they learn.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.
Of course, you'll have the people say I don't want to wipe, I just want to be in-and-out. You probably shouldn't be playing a heavy community driven game where you have to party with people then or feel free to go into solo content.
My latest rescue story...
Doing Asphodelos: Fourth Circle
The mechanic where the sword on one side of the arena casts the huge cone that covers most of the arena.
I was running towards the corner near me on the same side of the sword. For those unaware, there is a relatively large safe zone at those two corners.
Stupid healer decides to "save" me and drag me to the center of the side right next to the sword where the safe zone is MUCH smaller than where I already was.
And that tends to be my normal experience when being "saved" by them.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.
Reply With Quote





