I'm not the one suggesting that. I've only suggested removing Dissipation and making Aetherflow a charge ability so that you don't feel compelled to spend all your Aetherflow stacks within a minute to give you some breathing room to effectively bank your charges, if you so choose to do so. Damage intake is a massive problem in this game as far as healers are concerned and with each expansion offering more and more support to every class to further reduce it, damage intake just become less and less of an issue, hence the need for skills like E.Drain to exist in the 1st place.
The choice of healing vs damage is entirely dependant on an encounter and if you have still have Aetherflow stacks available as Aetherflow comes off CD. It's a loss in healing potency regardless if you use E.Drain or refresh Aetherflow with stacks remaining, only that 1 option at least refunds some of that lost potency vs simply letting it go to waste entirely. Removing E.Drain is a greater loss in Healing potency because of the existence of Aetherpact making any potentially lost stacks a bankable heal. The illusion here is that, people believe that E.Drain is taking up some spot that would be used for healing when in actuality, its saving you from losing that healing potency entirely by allowing you to put Aetherflow on CD immediately instead of delaying it for however long it takes until an opportunity pops up for you to burn that Aetherflow stack.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.
That was GrimGale, not me.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.



Reply With Quote


