Paladin's Smite with Divine Challenger is supposed to "place you at the top of the threat list of the target" when not charged. However, quite often it does not.
This might or might not be related to the server lags and the charging part.
On a side note, during heavy server lags in the past I could see Smite animation twice: when I use it instantly (without Divine Challenger) and then again after a second.
I have Smite on video failing twice in a row, 9 seconds apart, then succeeding 11 more seconds later. It was during RC Garakas fight on October 26. I was using Smite after Soulforged revive and the UI clearly showed that I was only getting aggro from the Smite's damage and not from the taunt part.
I also see Demogorgon go for my pet (Batiri or others) instead of me, when I use Smite to aggro it.
I suspect that Vow of Enmity might be affected as well.
2
Comments
I've noticed that I was blocking after the Smite, when it failed. I couldn't reproduce it that way though. Server lag might play a role, if it's not a coincidence.
I don't have a Demo video. I was able to reproduce it in a raid two times I've tried. I didn't block after the Smite and had troubles getting the aggro when he went for pets and then for other players. Couldn't reproduce in solo queue. But Demo might be a different issue. Keep in mind, that damage from the Smite (even without the taunt) is more than enough to not lose the aggro to the pet.
since saturday I have to use more than 1 smite to regain aggro, and now I lose it on tomm p3 if I'm not cautios smitting and hitting all the time. (and yes, I'm using divine challenger as an aura)
Templar's wrath lost the effect in dungeons (today's RC was impossible to get aggro from ads)
Only with the use of aura of valor I managed to keep aggro in angels at ZCM and ToMM... but since saturday I've been losing it with random players (not top dps)
Silvana
Last time, I couldnt aggro it 2 times. The animation on the Anvil is all bugged anyway ... I know when it hit only by the encunter going on cooldown. Saw its a bug, but didnt know its an aggro-bug. Hope this gets looked into and fixed asap.