From f192c14ff0d6d3205d90f83f254ecaa637e59bbb Mon Sep 17 00:00:00 2001 From: Rudolf Polzer Date: Fri, 14 Dec 2012 11:00:16 +0100 Subject: [PATCH] link to new/better playerstats response format idea --- qcsrc/server/playerstats.qc | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/qcsrc/server/playerstats.qc b/qcsrc/server/playerstats.qc index 4608b56df..5ddad200f 100644 --- a/qcsrc/server/playerstats.qc +++ b/qcsrc/server/playerstats.qc @@ -210,22 +210,7 @@ void PlayerStats_TeamScore(float t, string event_id, float value) // TODO: doesn acc--cnt-fired: amount of fired shots acc--frags: amount of frags dealt by weapon - Response format (not used yet): - - V: format version (always 1) - this MUST be the first line! - #: comment (MUST be ignored by any parser) - R: release information on the XonStat server - T: current time - S: in case of a stats submit request, the human readable xonstat URL for the submitted match - P: player ID of an existing player; this also sets the owner for all following "n", "e" and "t" lines (lower case!) - e: followed by an event name, a space, and the event count/score, and - if this is a reply to a stats submit request - a space, and the delta of the event count/score caused by this match - event names can be the same as above (they then are either sums, or minimum/maximum values, depending on context), as well as: - elo: current Elo calculated by the stats server - rank : global rank of player for this game type (for stats submit requests) - rank- : global rank of player for any game type (for non stats submit requests) - not all events need to be included, of course - if an event is counted additively from unprocessed submitted data, it should not be sent as part of stats submit response - achievement- events may be generated by the xonstat server and reported as part of stats submit responses! + Response format (not used yet): see https://gist.github.com/4284222 */ void PlayerStats_ready(entity fh, entity pass, float status) -- 2.39.2