Please Please Please Remove Esuna From CrossRole

[Fannah]

All this BS with buffing one healer to the heavens, while pruning the living crap out of the others isn't getting it done, and the devs would have to be deaf, blind, and dumb to not be aware of this.

You are allowed to read what I've written before. They put in "Action role" all skills being a basic tool for everyone sharing a same "role" and not having difference whatever is the class you are currently playing. Every tanks should get Provoke, every MCH/BRD should get Refresh (restore MP) and Tactician (restore TP). Then you can get rid of some of those basic tools to get something fitting more the current situation if you know what you're doing.
It's not devs' fault if people are bad enough to don't pick Esuna when needed, as it's not their fault people see the current system as "boo, this is not part of my class anymore, and it's not mandatory according to SE's system". You can select it, it's part of your class that's all. And I believe those who don't get Esuna when needed would not have use it anyway. I saw several fights where we died because the healers didn't cleanse the debuff. And guess what, it was part of their base kit.

So as it was before, you just have to communicate to make sure the healer you're playing with will use this spell for X or Y fight. In an MMO, improving your communication skills is as mandatory as getting Esuna.

[Hyperia]

Adding an extra slot to the Role selection would go a long way to allowing for better customization. Having to cast protect, remove it and then continue just irritates groups due to the wait on the swap.

[Riyshn]

They put in "Action role" all skills being a basic tool for everyone sharing a same "role" and not having difference whatever is the class you are currently playing. Every tanks should get Provoke, every MCH/BRD should get Refresh (restore MP) and Tactician (restore TP).

The difference being that with the Healer role skills, 4 out of 10 of them are things that all of the healers already had anyway, and had to be removed/nerfed from everyone to put in the role skills.

[Fannah]

Lol, Machinist could already :
- restore MP
- restore TP
- stun 2 sec
- silence 1 or 2 sec
- heavy 40% 12 sec
- binding 12 sec
- regain 400 TP

We had 7 out of the 10 current action role skills which were already part of us... But now we can only use 5. So at least, you can take 4 as before and get a new one.

So what's the problem? You can still pick the 4 important skills. If SE wanted you to be able to pick other skills for your overall healing system, they would let you do so. If they didn't, it's planed. You can remove some of those skills when you know what to do to pick other ones fitting more the situation.

The difference being that with the Healer role skills, 4 out of 10 of them are things that all of the healers already had anyway, and had to be removed/nerfed from everyone to put in the role skills.

Bard with same skills Machinist had :
- restore TP
- restore MP
- bind target
- silence target

--> The difference being that with the ranged dps support role skills, 4 out of 10 of them are things that all of the ranged dps supports already had anyway, and had to be removed/nerfed from everyone to put in the role skills.

[Riyshn]

Was more responding to the comment that all Tanks need Provoke, which was only removed from PLD.

And healers don't really have a choice. We've got Swiftcast (mandatory), Protect (mandatory), Lucid Dreaming (mandatory), Largesse (nearly mandatory), Esuna (mandatory or useless depending on fight), Surecast (Mandatory or useless depending on fight designs), Cleric Stance (nearly worthless), Break (nearly worthless), Rescue (potentially useful depending on fights), Eye for an Eye (Unreliable mitigation is unreliable). 4/5 of our slots are already decided, because these are very core parts of a healer's kit, and the last will be decided based on individual fights. There is no options here, no room for different playstyles. You either take the 4 plus one depending on which one is dictated by the fight, or you are severely gimping yourself. While it does suck that BRD/MCH lost their built in bind/silence, you can usually do just fine without those. (Agreed on Refresh and Tactician, though. It really does feel like chaning from cross-class to role actions has created as many problems as it solved.)

[Mikazuki_Aura]

Adding an extra slot to the Role selection would go a long way to allowing for better customization. Having to cast protect, remove it and then continue just irritates groups due to the wait on the swap.

What wait?

First, hardcast Swiftcast, then...

/macrolock
/macroicon Protect
/aaction Esuna off
/aaction Protect on
/ac Protect <wait.1>
/aaction Protect off
/aaction Esuna on

I've never encountered a situation in which I needed the Swiftcast before its CD regenerated after doing this at the start of a dungeon. There's no wait time, this can be done while running. I suppose you could do this with a 3 second wait, non-Swiftcast macro version as well, if you really dislike using SC for some reason. Or if you're swapping from a different class into a SCH and need your SC for Summon.

Though in the first place I don't really know why Protect still exists. It's entirely uninteractive and non-optional. Stoneskin would have been a far better skill to keep.

[AmelieR]

snip

To be fair, I didn't know it was possible to swap role skills on the fly in a dungeon with a simple macro until I stumpled upon it in this forum. You can even include Swiftcast in the macro.

/macrolock
/macroicon Protect
/aaction Esuna off
/aaction Protect on
/ac Swiftcast <wait.1>
/ac Protect <wait.1>
/aaction Protect off
/aaction Esuna on

[Mikazuki_Aura]

It's not the only case in which swapping role skills is good either. BRD and MCH have that party movement speed skill whose English name I'm not familiar with (green icon thingy) which can only be used out of battle.
Swapping role skills can only be used out of battle. There's an obvious synergy here.

Consequently, while having that skill around is pretty much compulsory to waste less time, leaving it as a permanent skill bar addition is pretty odd, and sacrifices utility you could otherwise have.

[Aomine1992]

This is silly lol I've leveled my AST to level 70 and I substituted Esuna for cleric because like before you barely used it unless you were in one of those 24mans with the doom mechanic...or the low level dungeons pre 50

Anything after that you don't really need it, a good healer isn't going just just have esuna when you don't need it a good healer adapts to the situation....the leveling dungeons to 70 do not call for esuna except for the last boss of castrum when he puts that nasty dot on the tank...the rest is completely avoidable, the healer shouldn't be punished because some people can't move correctly...

But like I said it's very situational so during a fight like the first boss in the "fist" dungeon I will have it because people always seem to get hit with the paralyze...

[AmelieR]

the healer shouldn't be punished because some people can't move correctly...

Said the... dragoon? o.o Jokes aside, the same applies to damage taken due to avoidable AoE. It is your job as a healer to correct the little mistakes your party made because they can happen. They will happen. To fail is human. Well, the big mistakes though... you can't correct everything. Doesn't mean you have to pick Ensuna for every dungeon when you know there will not be any debuff worth removing.