logging/debug info (was RE: [bf1942] crash updates...)

[WarmFuzzy]

Agreed.  I haven't looked too hard at the console or log contents because 
I haven't been running a windoze server in the meantime, but I would think 
at LEAST kills and captures should end up in a game log somewhere.

IMO, the best logging for a multiplayer game is Half-Life (haven't looked
at UT2003 yet), and they log kills, joins, parts, chat, and objective
completion, along with kicks and bans for cheating ;)

But yeah, we'd prefer stability to feature set right now :)

-WF

On Wed, 11 Dec 2002, Dan Beimborn wrote:

> Realizing that you're probably contracted to port this rather than make
> any changes, any chance you could output debug info like "X killed Y with
> Tiger" etc? I've been trying to correlate what goes on in the game with
> where the CPU load is higher. There really isn't good info out about 
> how many plaers a server can support, or *why* so that the tweak monkeys
> out there can try to tune for it
> 
> As a community thing, that kind of logging would really be great for 
> posting stats pages etc.
> 
> Of course, figuring out why it crashes is probably more important at
> the moment :)
> 
> DB
> 
> 

-- 
GCS d-(+) s+: a- C+++$ U+++$ P++>+++ L++>+++$ E--- W++ N+ o K++ w$ O- M- 
V- PS+++ PE(--) Y+ PGP(++) t-@ 5 X-- R+++ tv- b+++ DI++ D++ G e h-- r y+*