Macro stopped working since 1 week before 9.1.5

The following macro was working fine until the week prior to 9.1.5 dropping. Now it gets stuck on the divine toll spell with an ‘Invalid Target’ message being displayed. If I replace divine toll with judgment, it works, so there is some new odd issue happening specific to Divine Toll when used in this manner. If there is some new way that this has to be done, please advise. The purpose of the macro is to allow final reckoning to be cast wherever the mouse cursor is the next time the key is pressed after divine toll has fired off.

/castsequence [@cursor] reset=110 Seraphim,Unchained Gladiator’s Badge of Ferocity,Avenging Wrath,Divine Toll,Final Reckoning,Seraphim,Unchained Gladiator’s Badge of Ferocity,Divine Toll,Final Reckoning

1 Like

From some other posts, I gather that there was a change to Divine Toll just prior to 9.1.5 that now allows it to fire at your cursor but only if there is an actual target there, otherwise it returns ‘invalid target’. Perhaps the devs meant this for @mouseover and accidentally tied the spell to @cursor. Personally I don’t want either since it often fails in the heat of the moment in pvp because nobody stays still for long enough to be targetted in that manner, but yeah… perhaps let the macro fire with defaults when there is no valid target under the mouse. Ret paladin already has to deal with way too many keybinds to not have this type of macro working to consolidate at least a few.

Just got into Kyrian on my pally and also have this problem.

This is what I did to work around the issue for my macro… maybe others can do something with this to suit what they want:

/castsequence Seraphim, Divine Toll, Final Reckoning
/cast Unchained Gladiator’s Badge of Ferocity
/cast Avenging Wrath
/castsequence [@cursor] Divine Toll, Final Reckoning

So what happens here per each key press:

1st) Seraphim, trinket, and Avenging Wrath all fire
(Divine Toll from the 2nd cast sequence is prevented from firing due to @cursor)

2nd) Divine Toll fires from the 1st castsequence
(The second cast sequence cannot fire because of GCD)

3rd) Final Reckoning is fired from the 2nd castsequence
(First castsequence is cancelled as soon as the 2nd castsequence fires, so no need to click the mouse on the ground, and since Divine Toll was fired previously, it is no longer blocking Final Reckoning, making it fire at exactly the right time)

Repeat as soon as Seraphim/trinket are cooled down and it works again, but this time skipping Avenging Wrath.

This is actually an improvement over my original macro which I had to constantly juggle if I died in a battleground and wings were not yet cooled down. I call this one Can-o-whoopass 5.0

1 Like

Is there any way to make this work using Final Reckoning first instead of Divine Toll? I don’t know why you would ever use DT before FR. You lose out on 50% damage.

I got my original macro working again this way. Thanks for everyone’s suggestions.

#showtooltip
/castsequence [@cursor,talent:1/3] [talent:1/3] reset=5 Final Reckoning, Execution Sentence, null; [@cursor,talent:1/1] [talent:1/1] reset=5 Final Reckoning, null
/cast Divine Toll

Final Reckoning increases the damage of holy power abilities. Divine Toll, while it may do holy damage, is not a holy power ability. I cast Final Reckoning last, or better said, immediately before the first holy power ability that I would use… usually Templar’s Verdict. More time with FR up when I’m beginning to use holy power abilities = more damage. In other words, don’t waste the 8 seconds that FR is up on things that do not do damage by spending holy power unless somehow you ran out of holy power. Your damage spenders in ret are Templar’s Verdict and Divine Storm.

Someone also mentions that while FR is off cooldown, there is a chance it can call down a bolt of lightning which will increase the damage of the next holy power ability by 10%. My way gives 1 gcd more for this to happen in time for it to matter.

I guess it doesn’t matter if you don’t use Execution Sentence. It looks like you’re a pvp player so it may be different, but you almost always take ES in pve scenarios. So you’ll always want to use FR, ES then DT.

I was curious about Execution Sentence and did a few tests. It doesn’t appear that Final Reckoning will affect ES if FR is cast first. FR is expired before ES hits