Crit rush broken

Spearshard · April 2016

I haven't seen anything posted about it, so if this is a duplicate, sorry. I was playing around with 2 handed this morning in pvp, (no lag was present so that wasn't it), but crit rush, practically never fired. My toon would stutter in place and never move. Has anyone else had issues?

Gargath · April 2016

I can confirm that it sometimes happened to me also in pve (dungeon). Quite rare tbh, and helped to run in place doing other moves and when again crit rush - it was ok.

Keep_Door · April 2016

I have had this happen with ambush as well

leepalmer95 · April 2016

They messed up most gap closers in the TG update when trying to fix toppling charge...

The nb's gap closer works 100% though.

Judas Helviaryn · April 2016

Some gap closers are still broken. So far, winding up and releasing a full heavy attack into the air has fixed the bug whenever it appeared for me. Give it a shot and see if it works for you in the meantime.

magnusthorek · April 2016

It's frustrating having fighting an opponent that can use their Critical Charge on you and when you try to use you fail in a ridiculous dancing movement

mistermutiny89 · April 2016

Yep... I tried dipping into pvp today just to grab vigor and leave and for a Stam sorc crit Rush is EVERYTHING... I made 5k alliance points in the hour and left. Fun times.

Solariken · April 2016

Yeah this happens to me regularly - it seems to start working again after using another skill, such as Rally.

danno8 · April 2016

Templars have had this problem for 2 years now with Toppling Charge. Now everyone does. Ambush has it sometimes but usually not on straight ground.

They said they are looking to make charges work more like Ambush in the last ESO live. So there is at least an acknowledgment that they can't get them to work properly.

Nyteshade · April 2016

OK so it's not just me....the shield charge (I forget what it's called) in the one hand/shield line is failing quite often. It fails more often than it works. I see the beginning of an animation then, nothing.

ADarklore · April 2016

The only time I've seen Crit Rush not work is with uneven ground or an obstacle (no matter how slight) in between you and the enemy. Yet, other times I've had Crit Rush work in cool ways... like when the character zooms around obstacles to attack your target. But yet, it's just weird how sometimes it works and other times, it doesn't... perhaps there is a mouse on the ground and the character is afraid of stepping on it?!?

Spearshard · April 2016

I've noticed that it works completely fine in pve, but never in pvp. Weird. I tried over and over all morn in pvp. Even on nice level ground, but nothing.

kadar · April 2016

Keep_Door wrote: »

I have had this happen with ambush as well

The opposite is true for me. Ambush connects like 100% of the time because it bypasses all terrain effects except line-of-sight. I recently got a 2H Maelstrom Axe so I've been playing around with Crit Rush/Stampede, and it is EXTREMELY unreliable... If there's so much as a pebble in my path to the enemy, Crit Rush will fail every time. Sad Khajiit is sad...

Callous2208 · April 2016

Yea in pvp, there is like a 50/50 chance my crit rush will bug out and do nothing. Seems to work a lot better in pve but it's bugged out there before too. Just keep raising my sword above my head like I'm gonna charge and stand idle. Even on flat terrain with clear LoS I still seem to have the issue.

D0ntevenL1ft · April 2016

Ya most gap closers got ruined after TG update. They'll attempt to fix it come the next update several months down the road.

Calboy · April 2016

Between this and my bugged wings, life is hard as a magicka dk on console.

Stefirex · November 2021

I can confirm that this is STILL broken in 2021!

ZOS_Icy · November 2021

Greetings,

We have gone ahead and closed this thread down since it is rather old. Please keep in mind that sometimes it is better to create a new topic, instead of replying in one that was posted a while ago. With that being said, @Stefirex please feel free to create a new bug report in regards of this issue.

Thanks for your understanding.