Since I noticed a couple of people complaining about the broken Player Leaves event (Blizzard's Leave event doesn't notice when players simply quit the game; only when they get defeated or victorious).
I wrote a fixed version and added some neat interface to it.
It's fully integrated into GUI and can be used with a single action.
Installation involves just copying over a folder from the attached map.
I am using it myself (so it has seen some practical action already) and it works perfectly fine.
I have a similar action in my map. Over the course of a 2 hour game it executed 7200 times. According to the trigger debugger the entire execution time was under 200ms for that trigger.
Since I noticed a couple of people complaining about the broken Player Leaves event (Blizzard's Leave event doesn't notice when players simply quit the game; only when they get defeated or victorious).
I wrote a fixed version and added some neat interface to it.
It's fully integrated into GUI and can be used with a single action.
Installation involves just copying over a folder from the attached map.
I am using it myself (so it has seen some practical action already) and it works perfectly fine.
Yeah checking every 1.0s... wonder why there's still crying over it
Edit: your 1st pic is screwed :P
@progammer:
I have a similar action in my map. Over the course of a 2 hour game it executed 7200 times. According to the trigger debugger the entire execution time was under 200ms for that trigger.
Doh, map updated with a localized version.
I think I'm repeating myself in various topics but: Blizzard failed again.
@s3rius: Go
Didnt the latest patch correct the "Player Has Left" event?
@SouLCarveRR: Go
Yes, but I wrote this a couple of days before that patch was out. Back then there was no telling if they'd fix it or not.