I'm pretty sure they're separate actions... They share the 20s CD, and using either grants a free (regardless of CD) use again of either one. You can Banish and then (free-)Banish, Ablution and then (free-)Ablution, or Banish and then (free-)Ablution, Ablution and then (free-)Banish.
They're already as condensed as they can be outside of using the same name for both the attack and heal and having the action vary with whether you target an ally or enemy (which you could just do via macros anyways, as long as you don't mind having less lenient queuing period).
Note also that this is just a mock-up made specifically to avoid DoTs per Ren's request.Originally Posted by Sebazy
_______________
This seems like it'd be a particularly wasteful way to go about applying Dia as a non-DoT, however. First, it still has the "Oh noes! I have to look at my TARGET's Status Bar instead of my own. Whatever shall I do?!" since it's still a debuff that should be tracked for optimal pacing (reapply per 40s, on average over time). Secondly, though, normally the decision of whether to DoT or not is based around TTK, allowing us to wisely not DoT if we want to nuke something down in less than its redemption period (enough ticks to overtake our filler).
In this case though, your nukes (double-Banish) rely on having Dia up to begin with, so it instead ends up one of the uninterestingly near-universal obligatory actions like Heavy Thrust so long as Banish will be off cooldown soon.
But, so far as meeting Ren's request, all this looks nifty. Would almost certainly be an improvement over current WHM's flow even with those strictures, though I suspect it could of course be improved upon further.



Reply With Quote




