Targeting self with a hostile weapon proc running interrupts auto attack #627
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
When fighting a mob while running a weapon proc nano, targeting self will lock auto-attack within a few cycles, after which the character cannot continue combat without canceling auto-attack and restarting.
I tested this using both Keeper proc nano lines (Evangelical Reaper and Divine Sanctifier). I suspect it is the same for the Shade proc nanos, but those are broken per #617 and do not produce the proc effects.
This may be related to #593, and it may be that the direct-damage component of the proc is causing an error when applied to self and halting auto-attack, but I am documenting here in cast it's something different. In earlier testing weapon procs (Edge of Tarasque) have no qualms about applying to self, and the spell effects for these Keeper nanos both call out target=target, so this seems slightly different from the other issue, even if related.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Targeting self should not stop auto-attacking the fighting target
Screenshots

Character info:
Unable to repro with the above steps, let it run for a bit to test, slowly killing myself with the proc lol.
This might've been fixed during the changes on #597. Please re-test :)
Unfortunately no, this issue continues.
I noticed in further testing that as the auto-attack cycle locks, I get hit by 799 points of "unknown damage". This is exactly half the normal 1598 hit that Evangelical Reaper causes. This makes sense as I'm fighting a guard and thus flagged for PVP - a player (me) is hitting a player (also me) and so damage is halved.
I repeated this test non-flagged against a normal non-PVP mob, and got the same half-damage hit after the auto-attack lockup.
This looks to be fixed!