next »

[MordyT]

Hi there,
I have a client who is running a CoDUO server with the AWE mod. Everything is working fine, but we are experiencing a strange issue. When looking at the status.xml, it won't show any clients who are in a team (it will only show spectators).
He says that when he self hosted it would work, and I had a look at his old b3.xml, he was using the same parser I chose (cod).
Any ideas? Would a b3.log help?

Thanks for any help given!

[MordyT]

Bumping this to see if anyone has any ideas.

[Fantasy]

Just a wild guess, but maybe AWE is altering the gamelog somehow so B3 doesn't properly recognize in which Team the ppl are

Are there any errors on this behalf in the b3.log?

[MordyT]

there is a dozen or so errors in the log, but almost all of them have to do with rcon (no readable port) probably because of a map change at that time.

No errors anywhere near where it starts to build the xml status.

[Fantasy]

Now i remember having a similiar, or even the same problem (i dont quite remember) when i was running two bots from the same directory, it started to throw out very strange status.xml files.
Would be worth a try to copy the b3 folder and just start the one bot he is using from there.

And could you please post an extract from the gamelog where someone kills someone?

something like that:

 63:05 D;GUID;2;axis;fantastig;;-1;world;;none;7;MOD_FALLING;none

(Just for my own understanding, the ppl arent in teams already in the status.xml and not in the xlrstats webfront? If its the webfront then he should check $pll_noteams in his config, it has do be 0)

[MordyT]

As a final close note, a downgrade to 1.5.0 fixed this issue. All config files stayed the same.

When I have 2 minutes to breath I will make a new post with debugging info as it seems status.xml does not get written correctly for cod in newer versions of B3.