Duelist Slayer Ascendency Bugged

"

Vipermagi wrote:

There's no need to bump these threads (especially so frequently). GGG people read it all, they're aware of it.

Ok, I wasn't aware. Thanks.

"

Mark_GGG wrote:

"

Suzumiyaharuhi wrote:

is the Slayer's Headsman passive supposed to prevent on kill effects from curses like Poachers mark, Assassins mark, and Warlord's mark?

No. It does not do this and is not intended to. I don't understand why you think it would be?

I'm not actually so sure that they're aware of it.

I saw that too and agree. If there is a bug, Mark doesn't seem to know about it.

Perhaps the people who are experiencing the problem can provide a bug report number and post it in the thread, so that GGG can test it in the exact scenario where it is going wrong. ( I would, but I don't really feel like spending 20 regret orbs to test it!)

"

Mark_GGG wrote:

I specifically tested this, it definitely works for me.

I spent the last few hours testing, and there's definitely some extreme spaghetti going on.

You don't become entirely unable to generate charges - one slips in here or there - I think that something is having an improper interaction with the increased damage or radius "if you've Killed Recently." Once you're in that recent-kill state, you remain not only unable to generate charges from Poacher's Mark, but unable to benefit from *any* curse whatsoever, even though the monster is cursed. I was unable to benefit from the LGOH/MGOH/increased flask recharge portions of Poacher's Mark as well.

If your entry into the "recent-kill" state was improper, you remain unable to generate charges throughout the entire duration. Meanwhile, if your entry into the "recent-kill" state was not improper, you don't end up bugged at all, and can generate charges normally throughout the entire duration. It's really fucking weird and confused me for a long time because sometimes the setup would work fine and five seconds later it'd stop working.

I don't fully understand it, but the bug is super reproducible and I can demonstrate for you ingame if you want. It's crippling a lot of setups right now.

"

Mark_GGG wrote:

I specifically tested this, it definitely works for me.

I uploaded a quick video of this effect in action, definitely seems to be tied to recent killed state.

Video of Slayer Poach Issues

I think the problem with Headsman is not related to on kill effects in general, but to curses applied via Blasphemy. Tested this in City of Sarn, even big packs just give 0 or 1 charge when cursed by Blasphemy. Casting Poacher Mark manually gave plenty of charges, same with Blood Rage.

I am also having this problem. If I use warlord's mark with blasphemy, no matter how many mobs I kill in 1 hit, I will only ever get 0 or 1 charges. If I apply warlord's mark using another method like manually casting or curse on hit I get the correct amount of charges. This also applies to the leech on warlord's mark. If I use blasphemy, the leech I get is like 1/10 of what I get if I manually cast. I am using infernal blow so I am guessing with blasphemy it leeches from the initial hit and none of the explosions.

And to clarify everything works correctly if I remove the Headsman node.

"

VarthDaver wrote:

"

Mark_GGG wrote:

I specifically tested this, it definitely works for me.

I uploaded a quick video of this effect in action, definitely seems to be tied to recent killed state.

Video of Slayer Poach Issues

Thanks for this. I'd use my flicker setup but it's also pretty unviewable because of the intense lag spikes on killing a large pack with headsman.