Instead of checking lastHurtAmount which legitimately can be 0, lastHurtTick is initialized with -1 instead to reliably detect first-time damage. This fixes occasions of damage spam caused by my previous implementation which did bypass the damageSource config by accident.
Instead of checking
lastHurtAmount
which legitimately can be 0,lastHurtTick
is initialized with -1 instead to reliably detect first-time damage. This fixes occasions of damage spam caused by my previous implementation which did bypass thedamageSource
config by accident.