Does anybody know the syntax of the :player: tags in the eventlog?

Here's what I DO know:
It seems in a non-ctf match:

Code: Select all

:player:see-labels:score,kills,deaths,suicides,?,?,?,?,?,?:<playtime>:<team>:<ID>:<nickname>

Ex:

Code: Select all

:player:see-labels:-1,0,2,1,0,0,0,0,0,0:61:4:1:Carbias

But in ctf it changes to:

Code: Select all

:player:see-labels:score,caps,?,?,?,pickups,?,?,?,?:<playtime>:<team>:<ID>:<nickname>

Ex:

Code: Select all

:player:see-labels:25,1,0,0,0,1,0,0,0,0:52:14:1:Carbias

The docs are both incomplete and inconsistent about the syntax of this tag.

Any help would be greatly appreciated! Thanks!

The format is:

Code: Select all

:player:see-labels:<score1>,<score2>,...:<playtime>:<team>:<ID>:<nickname>

Your examples look consistent to me.

Aha, I finally understand what the players LABEL is saying. I had dismissed that as incomplete as half the variables weren't even listed, when in reality, every variable isn't needed for each gametype.

Thanks for the tips, and sorry for the ignorant question!

(For those of you wondering the format is:)
CTF:

Code: Select all

:player:see-labels:score,kills,deaths,suicides,pickups,drops,fckills,returns:playtime:team:ID:nickname

All Others (That I've observed. May not be ALL others):

Code: Select all

:player:see-labels:score,kills,deaths,suicides,null,null,null,null,null,playtime:team:ID:nickname

Alright, I got the eventlog working and parsed up, and went to sleep. I woke up this morning to find that the eventlog stopped at 12:40pm Mountain time.
I scanned through the server.log and couldn't find any errors. I didn't change anything, but that usually doesn't stop computers from messing things up
The server.log still shows the eventlog events, so I know it's still running, but it has at least stopped writing to the log files.

Code: Select all

[2009-04-24 13:03:00] "sv_eventlog_files" is "1" ["0"]
[2009-04-24 13:03:00] "sv_eventlog_files" is "1" ["0"]

[edit]It seems to have gone back on itself and begun appending new data to the old files. (beginning again with nexuiz_00000001.log)
I'm actually rather excited to learn that it does this, as this means I can work with simply 19 files, (ie erase the contents of each file after parsing).
However, I would like to know if this is a bug, or if I can expect it to continue making this loop consistently...

Well it LOOKS like a bug, and I would be happy if every match was written into it's own file.