@Renathras.
Ultimately the best solution there is a [moving] conditional available to macros and to un-neuter macros, but in either case, it was just a spitball means of pointing out how you could retain full control over the timing of those Lily heals without having to spend even a single button on them. Yes, it could "punish" unintended movement-based cancels in that spitball form... but no more so than too-early movement or hitting the wrong buttons would be already. Between using a Lily earlier than intended because you messed up your controls (which you could as easily do by hitting Solace instead of your intended button already) and altogether wasting a GCD... the latter is usually the worse.
On the whole, you've already heard my spiel: have healing GCDs grant gauge that can be used to rush cooldowns, with a couple new non-curative cooldowns being added to WHM. No Misery, just indirect potency recovery, perhaps with returns that increasingly diminish over use and then recover over time. Let summoning a Tornado to wreck and CC enemies while hastening nearby allies' movement speeds or a Quake to again damage and CC while providing cover to allies, at greater frequency as healing intensity increases, be sufficient.

Originally Posted by
Supersnow845
I don’t really see the validity in the idea that people are unhappy with how few damage options healers have then go “glare with 50% falloff and delete holy” is a good thing
No one has been asking for that. Thus far the requests have only been to give Holy a place also in ST rotation (and perhaps Glare, too, a place in AoE rotation, even if indirectly / only a bit more in that Dia is "included" in AoE during the dungeon gather), thereby increasing the number of actions available both in ST and AoE... but just without adding needlessly to button count.
It simply comes down to...
- "If spending a button on X offers zero additional complexity, QoL, or control... why spend a button on it?", and
- "If you already have dead buttons that can be easily repurposed to the effect desired, why instead leave those buttons dead and add a new one atop them?"
That's it. That's the extent of the logic being questioned here.