In Theorycraft Wiki’s WW Monk rotation, step 10 Bonedust Brew has conditions that strongly imply that it is a single-target high-priority ability, since it is coming quite high on the priority list with a condition of having less than 3 targets in range. However, it is also defined with the quickly recognizable characteristics of an AoE ability in Theorycraft Wiki’s various rotations:
is a cooldown saved for AoE AoE count = 3 AoE radius = 8
So, which one is Bonedust Brew, an AoE ability saved for 3+ targets or a single-target ability used as a priority with less than 3 targets in range?
I realize that the step says to save it if it won’t cooldown by the time an AoE need hits, but if it is an AoE ability, then why isn’t the AoE step higher up the priority list? Something like, “Use it with 3+ targets or if there are less than 3 targets in range but it will cooldown before the next AoE need arises.” This would make much more sense with the characteristics I quoted above.
The problem here is that if I design a WA or TMW icon that shows when the ability is off cooldown with a condition like “there are < 3 targets in range,” and this is the only programmable condition there as “or the ability will cooldown before the next AoE need arises” must be left to user judgment as far as I know, then such a design will be counter-productive and repetitively confusing for the user. Putting the 3+ targets condition higher on the list of priorities would work better as part of programmable conditions for a rotation.
And part of the reason I’m posting this is that I haven’t seen this sort of thing in all other AMR Theorycraft Wiki rotations that I studied.