A couple things concerning logging. I really consider them bugs in stock ET, although maybe the second is merely a good idea that should have been considered.
1. There's a fixed-width placeholder for the timestamp in the server log, which is bad. Once the log timestamp exceeds 1000 minutes, it runs into the log message itself. Over 10000 minutes, it gets truncated. See samples below:
999:57 Item: 6 item_health
999:57 Item: 6 item_health
1000:34Item: 12 item_health
1000:35Item: 12 item_health
9999:59ClientBegin: 21
9999:59ClientBegin: 14
10000:0ClientBegin: 7
10000:0ClientBegin: 2
2. Is there any way to get a player's GUID into the server log? This would be quite useful for stat programs (like the one I'm writing -- yes, this is a selfish request The GUID does get logged in the console log in the Userinfo message, but that message doesn't go to the server log.
Userinfo: \g_password\none\password\none\cl_guid\0123456789ABCDEF0123456789ABCDEF\cl_wwwDownload\1\name\Chairman Kaga
\rate\25000\snaps\20\cl_anonymous\0\cl_punkbuster\1\protocol\82
The console log is pretty much useless for stat programs, since it lacks timestamps. Having this in the server log would provide everything I need. Right now I have a hack that cross-refs the server log with the PB logfile, but it's ugly. Personally, I'm rather surprised this message doesn't go into the server log in the first place.
Logging issues
Moderators: Forum moderators, developers
- Chairman Kaga
- Posts: 64
- Joined: Mon Aug 04, 2003 9:00 pm
Logging issues
Steve (aka Chairman Kaga)
Proud member of Major League Killers
=MLK= International House of Panzer: 64.185.229.60:27960
Proud member of Major League Killers
=MLK= International House of Panzer: 64.185.229.60:27960