The GCD triggered by Hammer of Light is unaffected by haste. It feels awful to use HoL and then slowly wait for my other spells to come back up.
This, it also resets your auto attack swing timer.
2 Likes
Merging my thread with this one.
The paladin Templar ability Hammer of Light (HoL) has the following bugs:
- HoL’s GCD is unaffected by haste. There’s also a delay between pressing HoL and HoL actually firing, but I believe that’s an intentional design, whereas the slow GCD feels like a bug.
- HoL resets auto-attack. (Shield of Vengeance does this too, btw.)
- When the talent Light’s Deliverance triggers a free HoL, this HoL does not generate stacks of Crusade (Ret Pal talent). This is surely a bug because HoL normally generates stacks of Crusade, as do other talents that grant free holy power spenders (Divine Purpose, Empyrean Power).
And as a bonus, this isn’t really a bug, but the buff bar text for Light’s Deliverance is totally wrong. It describes an old version of how the mechanic maybe originally worked, but doesn’t anymore.
Please fix these issues because, although paladin is fun to play right now, it feels something of a buggy mess.
4 Likes
Everyone is still using Herald because of house awful Hammer of Light is to use.
1 Like
Let’s just debunk this one
Hammer of Light does in fact reset the swing-timer. I could make a decent guess at why your combat log gave inaccurate info, but really it doesn’t matter. Hit a target dummy for a couple minutes while watching a swing-timer and you can’t not notice it. The only time HoL will appear, wrongly, not to reset the swing-timer is when used just before an auto-attack. HoL has a delay before it fires and so the auto-attack will actually have fired first.
Please test this again.
So, again, the bugs are:
- HoL resets the swing-timer.
- Its GCD is unaffected by haste (or something of that nature).
- It does not generate stacks of Crusade when triggered by Light’s Deliverance.
You’ll see that there are 2 logs there, one where hammer of light is cast and hits before the melee swing and one where hammer of light is cast, the melee swing then hits, and then hammer of light hits. Neither scenario reset the swing timer.
The combat log is giving more accurate info than whatever you’re using to track swing time
1 Like
Auto-attack the five target dummies in Dornogal while talented into Crusading Strikes and Art of War. This gives a very high chance to trigger AoW, but notice how AoW never triggers following a Hammer of Light. Instead, it triggers when you’d expect it to following an auto-attack reset.
I think you maybe haven’t played much Templar yet because it’s hard to not notice the auto-attack being reset.
1 Like
Try just sitting and auto attacking for a bit, and look at the pace of those hits, then cast hammer of light in between the regular hits and watch how delayed the next melee is. That’s what we’re talking about.
1 Like
Does not reset the swing timer with crusading strikes and 2/2 zealots favor either.
If you want an example of a swing timer reset, look at shield of vengeance.
1 Like
Can confirm, please fix, Blizz!
It feels bad to play Templar when it doesn’t mesh in with the rest of the gcd’s, it ruins the rhythm.
1 Like
Yes, SoV resets the swing-timer. This is a good bug report. If you weren’t so myopic about your combat log you might notice that HoL does as well.
1 Like
it doesn’t
1 Like
It does. It’s been confirmed in the ret discord as well. I can’t post image/link but this image shows what’s happening.
imgur. com/a/2E86YLZ
You can see that the first 5 hits of crusading strikes happen about 1.1 sec apart, then hammer of light hits and its about 2.5 sec from the previous hit to the next. Then the next hit happens about 1.3 sec later
Does this only occur at higher haste levels?
The GCD takes forever after using Hammer of Light. Doesn’t make sense.
Happens at all haste levels
Dunno what to tell you other than I haven’t been able to make it reset my swing timer as either protection or retribution, crusading strikes or templar strikes.
1 Like
This bug still exists in 11.0.5, please fix.
Tested this morning. Appears to be fixed. Thank you Blizz.