[404UserNotFound]

So I noticed there's this stuff in the player_death event:

 
kill_streak_total   Kill streak count (level)
kill_streak_wep   Kill streak for killing weapon
kill_streak_assist   Kill streak for assister count
kill_streak_victim   Victims kill streak

Anyone know how to properly use this stuff now? I ask because I have some ideas for how this stuff could be used (i.e. adding in bonus points for hitting certain killstreaks in the TF2 Stats plugin, or re-doing the existing TF2 "kill streak" plugins to use this stuff instead of coded-in kill-streak checks and timers and such.

I got this far before I went "Wait, how does this know that it's checking the ATTACKER'S killstreak, and not the victim's?" and then spaced out:

PHP Code:

new killstreak = GetEventInt(event, "kill_streak_total"); 


I think that code needs to be tied into an attacker check of some sort to verify whose killstreak the plugin is checking, but as I said before, I spaced out and don't know where to go from here.

[Chdata]

On a similar note, if I set m_iKillstreaks to something through code, the client who's streaks were changed suddenly has their auth ticket canceled as their game crashes...

(Sorry for the slight hijack).

[404UserNotFound]

Originally Posted by Chdata On a similar note, if I set m_iKillstreaks to something through code, the client who's streaks were changed suddenly has their auth ticket canceled as their game crashes... (Sorry for the slight hijack).

S'ok (it's topical, so I'll allow it)

[Mitchell]

Not sure i understand the OP's question..
They are all shorts so you use GetEventInt on them
if you want to find out on your own then just test out each value on a bot or something.

[Powerlord]

As a reminder, events are a notification of things that already happened.

player_death is the event that populates the killfeed for players. It MAY also be responsible for displaying the messages about killstreaks starting (for attacker/assister) or ending (victim), but it's possible that another event or UserMessage does that.

As you can see from the event's other fields, you already have the various players userids (note: not player indexes) needed to determine who the attacker, assister, and victim (userid) all are.