A lot of the main issues with SCH are not being addressed with Endwalker

[Shurrikhan]

< Mixed up posters >

Listen, the only way that you can make it so that you aren't shoehorned into using E.Drain before Aetherflow gets off of CD is if they make Aetherflow a Charge Ability

You have a full minute to spend your Aetherflow charges. If it is absolutely impossible to have any circumstance worth spending your Aetherflow on other than a last-second ED spam to dump charges, you're looking at either (A) a must-top-off-everyone-instantly cohealer or (B) a much, much larger issue in the game's damage intake tuning.

This indirect-at-most concern is not something you sacrifice weave-space, offensive spell potency, and actual choice for.

I'm cool with allowing 2 charges of Aetherflow. I'm cool with automatically losing Aetherflow and generating stacks every 20 seconds so long as they're bankable up to 5 and charge up to 3 out of combat (and begin instances at 3 stacks). I'm just not cool with turning Energy Drain into a more awkward Aetherflow.

E.Drain vs Heals has become an illusion of choice in EW. The mere existence of Aetherpact negates the actual choice involved in whether or not you use an Aetherflow Stack to heal or DPS because no matter what, that stack is ultimately being used to heal with Aetherpact at the end of the day.

That there is eventual further healing attached to both among the damage-dealing spender and the healing spender does not remove the difference between that initial damage or healing.

Energy Drain is not inseparable from Ruin II in particular; it merely requires weave space, just like any other oGCD. Energy Drain is no more balanced around Ruin II than are Lustrate or Excog. Broil providing that weave space as of EW does not remove any and all reason or ability to use Energy Drain; arguably, quite the opposite.

So stop trying to remove E.Drain. It's as much a Healing Tool as any other Aetherflow skill is.

I'm not. You're the one who suggested (albeit in just 2 of 3 takes) that it be turned, effectively, into a target-dependent Quick Reload. I'm asking to keep it an actual dump/damage option, instead of merely an obligatory resource-generation cast.