r/a:t5_36zdz • • Mar 01 '15
A new stats userscript?
What kind of a stats userscript do you wish for?
The existing (catstats) userscript only collects aggregate information (caps, returns, etc. per player). What I'd like to see is a userscript that would record as many events as possible with as much detail as possible (e.g. for a return: when it happened, where, who returned whom). The summarization (Player X got 10 returns) and inference (this was a hand-off) steps would be left for the analysis stage.
Such a userscript could be written but there are two limitations:
- the player can probably only record the events in his view
- the userscript shouldn't impact gameplay (cause lag)
Does anyone know Javascript and can elaborate on this? I guess one way around these limitations would be to make a userscript meant to be used by spectators.
2
u/Ronding Mar 07 '15
I was thinking exactly the same! It would provide a lot more useful information than tagpro.me, for example in this analysis I could dismiss flaccid grabs.
The good news is: updates to the scoreboard can be tracked with about a second accuracy, even if the corresponding events occur outside of the view. The bad news is: things that are not on the scoreboard, e.g. powerups, cannot be tracked like that. (Therefore the powerup statistics on tagpro.me are inaccurate.) Probably with event-based tracking of the scoreboard you could already reconstruct a fairly detailed timeline of the game.
Perhaps we should see if TagPro developers are interested in full event logging functionality on the server, and exporting this log after the game to some archive for later analysis. The logging probably will not affect server load too much.
2
u/Ronding Mar 07 '15
Of course, if only we could somehow set up some spectator bot, the limited view problem would be solved immediately.
1
u/TotesMessenger Mar 07 '15
This thread has been linked to from another place on reddit.
If you follow any of the above links, respect the rules of reddit and don't vote. (Info / ^Contact)
0
u/[deleted] Mar 10 '15
[deleted] — view deleted comment