I do a lot of event logging in my script so people can see whats been going on afterwards. I thought it would be cool to log any attacks by other players, be it melee/archer, war spell or vuln. The description of OnMeleeLastAttacker seemed perfect. When I try to test it though, nothing happens. It doesn't get fired for any pk attacks. As I think about it, not entirely sure it gets called for any attacks.

Does anyone else use this? Is it just filtering out any pk activity or does it not work anymore?

I'm seeing OnMeleeLastAttacker in PvM using SW 2.5 and Decal 2.5.2.0. I'm not a PK, so I can't test that mode, but I don't know of any reason why it wouldn't work. Does the manual Last Attacker command (Home by default) work for PKs? If so, OnMeleeLastAttacker should work too.

I've just started to try and use this event (OnMeleeLastAttacker) and am also seeing the event not get fired at all. I'm looking at PvM, I think I have the handler set up correctly (the same as all of my other handlers) but this event never gets hit.

Is anyone currently using OnMeleeLastAttacker?

Thanks.

Warbot uses...

skapi.AddHandler( evidOnMeleeDamageSelf, MainH );
skapi.AddHandler( evidOnMeleeEvadeSelf, MainH );
skapi.AddHandler( evidOnMeleeLastAttacker, MainH );

and they work fine, at least in PvM mode.

Maud-Dib

It has worked in the past, but I'm not seeing it either now. I'll look into it when I get a chance.

When in doubt, use Px Events from the SkunkWorks console to see what events are actually being fired.

Fixed in 3.5.491.

Are you sure this fix made it into 491? I'm still not seeing it fire. (I'm looking with both my own code and the PX Events in the SK console UI.) I can see the damage and evade messages, but not the lastattacker messages. :-(

Well, I must have thought it was fixed at the time, but you're right, it's still broken. In fact the "fix" I implemented then is one of two bugs breaking it now. So I guess I must not have been thinking straight or testing carefully enough at the time, and for that I apologize.

In any case, I've backed out that previous "fix" and implemented a real fix for the real bug, so there will be a tested and verified fix in the next release of SkunkWorks. When that might be is somewhat up in the air; there's talk of a new release of Decal fairly soon, so it seems best to wait and retest against that.

Again, my apologies for not getting this right the first time.

Any news on what might be happening with relevant releases?

Thanks