Quote:
Originally Posted by trevius
Yeah, that is just where nexthpevent gets set to -1 if no further HP events are set when the EVENT_HP gets parsed there. It doesn't make sense why that would treat the perl Damage function different than normal damage.
|
Every time an HP Packet gets sent, it sets it to -1 if it is less than the amount of HP on the mob. You could try forcing an HP update right after damaging it. If what is happening is what I think is happening, it's parsing EVENT_HP twice; once when you damage the NPC, another when the tick gets sent to the client. I think so anyway; didn't look into it more than that.
Resolving it manually or sending an HP update after doing the damage should work though.
Threaded Mode
