I’m not sure if this belongs as a bug but the inconsistency had me scratching my head as to whether or not Divine Arbiter was behaving as indented.
The tooltip goes as follow:
Abilities that deal Holystrike damage deal 5% increased damage and casting abilities that deal Holystrike damage grants you a stack of Divine Arbiter.
It says “casting” so we should infer that 1 cast = 1 stack.
Then we have “crusading strike” for which it works on the auto-attack (for 1 stack) which is not casting but I guess consistent with the “use” of CS on all autos.
Judgement and HoW by themselves gives 1 stack, again consistent and fine.
Now here where it kind of stop making sense.
Divine toll gives you 5 stacks if there is 5 targets, yet it’s 1 cast.
So it’s considered 5 cast of judgement.
But then when we talent “blessed champion” and we judge 5 target on judgement cast (we apply judgement debuff to 5 targets same as Divine Toll) we still only get 1 stack.
Why is it different?
Even weirder, on HoW use, the Adjutication talent “spawns” a blessed hammer.
The blessed hammer wasn’t casted, yet he gives a stack for each enemy it hits.
Blessed Hammer is a Crusader strike replacement for Protection spec.
Again the talent “Blessed Champion” makes our Crusader strike hit 4 additional target and if blessed hammer gives a stack on each, shouldn’t CS then do the same?
Divine Arbiter cleave component always puzzled me since there’s no real way to use it consistently to cleave.
But it would make sense if the Dev team intended the stacks to work with Blessed champion to make Divine Arbiter a “funnel” damage ability useable in AoE situations.
I thought I’d bring it up here considering the team is reviewing the performance of each spec/classes in Amirdrasil and in M+ and since the interaction seems inconsistent and might be unintended.