Hello, everyone. the problem is when you push for the Crusader. after 7-8 minutes, the main damage-causing ability ceases to activate. tested on different computers. on different great portals. video below.
That’s very interesting. I have not pushed that high so do not know. I have had my sader get stuck in place before but can just walk around until it clears…never had condemn not work.
That is weird. If I were the OP, I would do a video of the entire rift, showing it working then it suddenly not working, for nothing else but to absolutely show the issue being present.
If you are in a group does this happen?
After you leave the game and start a new game, you are seeing the same issue?
But yeah, do a video cap of the run from start till the skill stops working.
Last season I was in mid 120 gr’s as a condemn sader in 4 man group and never saw OP’s issue.
This appears to be another bug issue with what Blizzard has done with small patches lately!
I have had blessed shield stop attacking for brief periods of time, 2-5 seconds. Sometimes due to waller affix, but occasionally there is a clear line of sight to the target. Even while holding down shift, the attack animation stops completely. I have to stop attacking, then resume again with a new click. But nothing like this where all damage ceases, almost looks like a lag out. If i had to guess, it is a bug with the waller affix. It stinks that this happened on a push.
Same problem!!! (timecode is 13:42)
I do not see yet, but i should to write that warning.
Please, do not spam a messages where written that we are doing something wrong. It`s the bug.
Is this a recent problem? Looks like both of you play on the EU server? Is this an EU specific problem?
I think, that`s Stone of Gauntlets bug. Something going wrong when you use it.
I haven’t played in a couple of weeks, but I wasn’t having this problem with Stone Gauntlets. Hmmmm. Weird. Could be the SG though since they mess up attack speed severely without a way to counteract the debuff.
I’ve done many sader solo from 100s - 137 and I haven’t seen that problem once on NA server. Could be isolated to the region (EU) or possibly a minor patch made some spaghetti code.