Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

Issue Confirmations

  • Yes (2)No (0)
Photo

Crush Strike

Posted by gunzlinger on 28 April 2014 - 08:17 PM

Crush Strike is supposed to be able to do three things that it cannot do at the moment.
These three things are:

A.) It is affected by Crit and can crit.
B.) It is affected by Double Attack.
C.) It is affected by the Thurisaz rune's chance of triple damage on normal attacks.

Right now, it probably isn't being treated as a normal attack - hence, inability to crit, inability to double attack, and doesn't qualify for Thurisaz's 15% chance of triple damage, so there is a further issue with it - it's probably affected by WoE skill reductions. This part is untested, but is a pretty sound conjecture.

Please help fix this, as it's a really bad bug for Rune Knights in general.

It should also trigger from Auto Counter's hit.

I mentioned Auto-Counter in a different thread, since it's a separate bug. However, it is also relevant - you're not counter attacking with Crush Strike. :/

changed status to: Fixed

Fixed @ f4f4b3310d83c10f72af525d86c58053411df5da

:meow: