Runar

"mortars.1 mortars mortars into oblivion"

Kill Track exploit.. I have an idea of how to fix it, dunno if you were aware of faking out the script like this yet

:o

I been waiting for a fix for this for awhile, hopefully it comes now :)

Why does Prestos have to be so perfect and slow :(

and gay

If Presto hadn't been so gay, z1tt would have had nobody to rip off for his ShitHud

he might not have had as much fun making z-Thod not run like a piece of shit either

My config > z0dd_hud.cs

;P

:bigmouth:

I would assume that would be easily fixable with Presto.

Except Presto is (sadly) slow as shit

I think I fixed it with Runars with little to no speed loss anyway

androo, why dont you work on a prestoplusplus and strip it right down, i know you have the scripter $$$ :o

im not great at making publicly releasable scripts :(

maybe ill put my new config out when im done, almost as fast as z1tthud with more features..

Well, all one would have to do is make sure the killer and victim's name isn't "%weapon*".

Hm.. wasn't aware of it.. I never play on non-Fstat servers so I've never seen any "abuse" of the killtracking thingie.

Glad you fixed it though :)

Any player who plays as a word/phrase found in any kill message can potentially mess up the parsing

And if two players have simliar names ("Bob", "Bobby"), and Bob is checked before Bobby for the client matching when Bobby was the player affected, it will fuck up as well

I would usually not care and just put a kill parser that only tracks my events on, but I'm a stat azz and need them to be perfect ;(