There are multiple ways cheats could figure this out. However, that's quite different than adding it as a feature to etpro
Also, logging revives doesn't mean you have to log spawns or gibs/tapouts. You could still make an educated guess, but in matches that's pretty easy to do from the other teams /kills.
The gameplay change that seeing the other teams revives would cause is knowing how many people that 4 man airstrike actually took out of action.
Anyway, statsall should take care of your statwhoring needs. If people want to see revives and/or gibs as a gameplay change (shrub rtcw showed both if I remember right) thats a different debate.
i dont really see how it'd be any easier to get spawn time off of revive logging, compared to /kills or just Seeing it, but whatever, you dont need to log 'XXX revived YYY' just need to add another column to the end of round stats table where existing client log parsers already get gibs, dg, dr, xp from. then it'd be a trivial update. given statsall already provides revives i wouldnt expect any time to be given to it, its would be a lot easier than relying on clients to use b_endround statsall and parsing that.
I think changing that normal table would be a bad idea, then all the OTHER stats wouldnt work. And I think it'd become inconsistant between mods (afaik).
IMO, just make a command that does a /statsall in a nice table format.
Then it wont takeup 50 lines.
b_endround "statsall" does give you the stats, but I love looking at that original table aswell, and because of the statsall spam its lost a few miles up the console
would become incorporated in the client etconsole.log file? And thereby, any statparser could then put in revives if they chose to right?
Right. The output is included in etconsole.log, and is also saved in your demo.
BTW, I include "weaponstats" just so mine are at the bottom in the console. You'd only need "statsall" for what you're asking. Statsall = everyones stats (including yours), weaponstats = just your stats (or "weaponstats <slot number>" for a specific player).
You also need whatever stat parsing program you use to understand the output of statsall.
Dersaidin has a good point that statsall ouput spams a lot in your console.
Atleast 1 stats maker from Australia has plans to support this (gravystats)
And the longer I've had b_endround statsall happening the more I want it in a table. External file would be ok too, but I dont mind looking at them aswell. Original table is ftw though.
to me, it just seems like an awful lot of effort when really, all that people want out of statsall is the revives. most of the information in statsall can be attained already - the rest isnt worth much.
Accuracy depends on to many variables to really mean anything in a stats file, and xp means nothing in a competition sense which is what most stats are focused on. Headshots might be interesting to track but again are largely context sensitive. The only things apart from revives Im looking at pulling from statsall are the number of canisters/airstrikes/panzers etc fired, and maybe team damage received.
I just reckoned that with revives, you could easily forget the rest and you'd have satisified most people's needs for stats (its the only real recurring request).
All the other stuff from a clan perspective doesnt matter much. I mean if a guy gets 100000 damage from getting 77 headshots or zero headshots I do not care, as long as he is getting the damage. Heck, he could achieve that damage by using his friggin knife only, whatever.
Accuracy too, who cares per se? Higher the better I guess (although one could argue against that too to some extent) but its the damage given that counts in the end.
Revives though, those are KEY, they are equal to damage given in importance.
I love all the info in the statwhore program though, its a very nice job.
Last edited by Herf on Sat Jun 24, 2006 5:40 am, edited 1 time in total.
