Help Incorrect Spell Damage Display.

[Meydex]

Hello,
Whilst trying to investigate and solve issues on my pack, I came across this problem:

As you can see, the damage message is displayed after the monster is dead which doesn't seem right. This only happens with spells (fighter-mage included) ,not auto attacks. Any ideas how to fix it?
Thanks!
 

 

UPDATE: After countless tests I realised that damage is displayed even when the monster is dead. For example I had a friend of mine kill a monster and with the right timing I managed to start a skill cast right before the monster's death and the damage msg appeared even though it was dead :S . Any guidance on which file to search for the solution of this issue?

Edited October 20, 2016 by Meydex

[Onix]

This problem just should be of server or client delay. Serioulsy never meet same problem as you ( most of pack i used )

[Meydex]

Does it have to do with delay in general or is it code enumeration issue? That's what I am trying to figure out and I can't seem to find the answer anywhere :S

[SweeTs]

Most likely 'bad timing'. Mob was doing a hit and you killed it. Normally the hit should be aborted/canceled.. :P

Edited October 9, 2016 by SweeTs

[Tryskell]

Most likely 'bad timing'. Mob has doing a hit and you killed it. Normally the hit should be aborted/canceled.. :P

 

Could be, if there isn't any isDead() check. The possibility than the creature dies before getting hit points removed is impossible, so it's either *ONLY* the message display which is setted in top end. Need further infos, notably :

- use regular cst/atk speed and figure out if it's really that damage which kills the NPC.

- does it happens always or only few times (few time could be lack of synchro somewhere)

- if the event comes few seconds after the death, it is most probably a code from onKill section from L2AttackableAiScript which needs to be moved out from that section.

Edited October 9, 2016 by Tryskell

[Meydex]

It happens with all spells and it happens every single time, which probably eliminates the lack of sync possibility. Additionally, this damage really does kill the NPC, that's why I assumed it is a display error. Should I limit my search within the L2AttackableAiScript or should I check something else too? I Appreciate your help btw guys.

[Tryskell]

You didn't answer to the last question which could help to define where to search. If it happens in same time than regular onKill scripts, you got your answer. Only spells, not physicial damage ?

 

It is almost sure than it's a problem of "code positioning".

[Meydex]

Oh yes, it happens only with spells, not physical damage :)