I run a popular 3rd party stats package for TF2, after this latest update I 
was investigating adding the new weapons and events to it so that my users 
could see who got the most kills with this and that, and who hit someone 
with jarate the most, etc.  While I was investigating I found a couple small
quirks with events/logged messages that would make it easier on this third 
party stats program if they were corrected.  

FAN still logs as scattergun (when medic weapons were first released the 
unlock names matched the items they replace, this was changed in a later 
update) - if it could log with a unique name that'd be very useful.

Dead Ringer - the 'death' line looks identical to a normal death line - the 
'fake' can be detected in the player_death event by looking for 
death_flag & 32 (which is great) but if a property could be add to the death 
log line that differentiated 'fake' eg: (customkill "fake") or had any other 
way of distinguishing from the just the logs so that it wouldn't require a 
plugin to tell if it was a real death or not.

The events player_jarated and player_jarated_fade and player_shield_blocked 
don't seem to ever happen in game play (I couldn't get them to happen at 
least) - I don't even see them with net_showevents 1, so they don't seem to 
be client only.

player_extinguished happens when you put out a teammate with the jarate, 
but not for pyro (air blast) or medic extinguishes (medigun). The comments 
in the modevents.res say:   

"player_extinguished" // sent when a burning player is extinguished by a medic. 
 

Also vicim is always set to 0 in this event.  When this event does happen 
(due to jarate) it sometimes happens a couple times for the same extinguish 
this isn't that big a deal, but I thought it might be a symptom of a bigger 
problem.

-octo

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to