AW: [bf1942] bfv goes fourth

[Martin Steiger]

Peter: First of all, thanks for the GLIBC <= 2.2 thing!!

Second: As you may know, there are some log-parsers for BF1942 out there (at
the moment I only know of select(bf) and phpBFStats). It is not a "very"
important thing to have the mapname in the logs, but it would make life
easier, since both stats-systems are also creating mapstats. If you think,
you could manage it, to have this in 1.0, it would be great...

Not many people really care for the logfiles, but they do care, if their
stats are wrong... ;)

Next (unimportant) thing: I had a short look at the logs and they look
similar to the ones, bf1942 creates. But first thing what I saw is, that
flag captures are not called "attacks" anymore. Sure, it makes sense to call
them "FlagCaptures"... ;) Still, it would be easiest (for us of course), if
the events are similar, since you could use both stat-systems for BF1942 and
BF:V... As said, not really important, just a "nice-to-have"...

Again, thanks for your hard work!

Martin



-----Ursprüngliche Nachricht-----
Von: Peter Chang [mailto:peter.chang at dicecanada.com]
Gesendet: Samstag, 13. März 2004 13:20
An: 'bf1942 at icculus.org'
Betreff: RE: [bf1942] bfv goes fourth


From: Forrest Thiessen [mailto:thiessen at alum.mit.edu]
Subject: RE: [bf1942] bfv goes fourth

<bf:setting name="map">Landing_Zone_Albany</bf:setting>
However, in the logs I looked at, this one <bf:setting> value was missing
(all the other usual ones from BF1942 seemed to be there).


This is a low priority for fixing, I'm sure, but without it you can't tell
from the log file what map was being played, so I'd appreciate having it on
your fix list.


is this going to affect enough people that it should be in the 1.0 release?

i'm sure that this is something that i dropped when merging because we don't
carry around (visibly at leat) some of the data that 1942 was. however, if
it is a small population of people who care then i'll just roll out apps at
the end of the weekend (in case something else goes wrong)

\p