Culling Strike (20% from Slayer) doesn't always proc on netted beasts
https://streamable.com/w6r8a
This creature should be netted and I have booth Bane of Legends AND Skull Cracking. Yet netted beasts (sometimes) refuse to be culled. Not sure if intended. I made a topic about it before but had no proof, now I have (see video). Play it slow or pause it and you will see that it has way less than 20% hp. Pausing the video somewhere around the 8 second mark shows the creature having WAY less than 20%hp but still being alive. Bug #: 3.495.346.363 Update: Just happened again on the very first map. I net the creature, it's hp goes down to like 5% but not culled. Then the net wears off and it instantly dies from my damage... This makes capturing them really annoying. Because the cull DOES always work the moment the net wears off. Last edited by silverdash#0964 on Mar 8, 2018, 8:07:07 AM Last bumped on Mar 14, 2018, 6:39:56 PM
|
![]() |
It seems that this is the case for all beasts? I just had a fight against a tough mob. The problem was that my DPS is not high enough to get it down from 30%ish --> 0% hp before the net expires. If it expires and the mob has <20% hp then it get's insta-culled and thus no capture...
This mechanic prevents weaker DPS Slayer builds (with the 20% cull) from capturing tough beasts.. Therefor I again assume this to be a bug and not intended? Also it would make no sense for an Ascendancy skill to actually penalize the player. |
![]() |
Happens to me also, If I don't time the net just right totem or main attack kills mob, if I net too soon can't DPS it down enough.
|
![]() |