OLStats does log carjackings and road rampages. You might need to enable "Full Vehicle Stats" in the UTStatsDB main configuration.

Since you didn't list it, I'm assuming you're not running OLStats for your logging mutator. You'll need to use OLStats.

Based on their example, I would suggest adding the following code in main.inc.php after the line:
require("language/lang_{$lang}.php");

error_reporting(0);
$old_error_handler = set_error_handler( "userErrorHandler" );

function userErrorHandler($errno, $errmsg, $filename, $linenum, $vars) {
$time ...

It doesn't sound like the web log is going to do much good. Is PHP configured to log errors?

Then it sounds as though the match was not successfully parsed completely. Check your web server logs for PHP errors around the time it was parsed.

The problem on his system was having added something to his configuration file that shouldn't have been there.

Please send me all logs from Deathmatch matches with this player from the beginning of the 18th and I'll see if I can duplicate this.

Look under "ChatLogger".

So the issue you're having is in the map stats, nowhere else?

The stats so I can see if things aren't getting logged correct or if it's not parsing correctly.

Send a couple of logs and I'll have a look.

If you mean to search for players by IP address, the only way to do that currently would be to manually perform a database query. Only the most recent IP address is maintained for each player, however. It would be a good idea to add a table to keep track of IP addresses.

That's why I added those features. Now if someone would just document it better...

ut_weapons

Because it knows they're weapons, but it has no clue what kind of type your custom game type is. However, it won't know what type of weapon they are unless you set the weapon types as well. They'll default to regular weapons as opposed to turrets and such, just like your custom game type most likely ...

You need simply edit the ut_type table and set tp_desc, tp_type, and tp_team to the appropriate values for your game type.

Considering there's only one Vehicle CTF match logged, this seems like a reasonable total.

UT3StatsHTTP seems to be hit and miss. I couldn't get it to work reliably on my own server, but it works for some people. El Muerte wrote the UT3 HTTP library and I don't see anything wrong in there. I think it's just something glitchy in the UT3 TCP routines.

using latest serverquery from websvn, still get the offline message. Query port is the default 6500

Make sure that the socket module is loaded in PHP on that system and that they don't have firewall rules blocking outgoing connections from the web server.

Oh that's quite all right, we don't want your money. I would suggest however that next time you take a moment and read the sticky post at the top of the posts (subject "***READ BEFORE POSTING***").

Somewhere. UT3Stats is just the logging mutator for UT3. I believe that what you're looking for is UTStatsDB.

OLStats works well. As for which files, check your browser's URL for the pages you want to modify.

These would be stored as plr_key in the ut_players table, if you're using a logger that supports it.

Logging is built-in, except for chat logging, for which there's a mutator in the download section.

I gather the cost of their service reflects the quality?

I didn't get a different result, but I also didn't get the errors. I'll look into it further.

Try disabling all but the OLStats mutator and see if you can query players then.

No, it appears that the query port is not open. You'll need to have them open the query port (UDP 7787). As for gameservers.com, they're just pulling their list from the master server.

That's interesting. Thanks for reporting this, I'll look into it when I get a chance.

Any chance you can send me a copy of the log files from that match and the one before it?

Off-hand I'd say your FTP path is wrong. Try logging into the FTP server manually and see if you can switch to that path. Take care that you're supposed to use an absolute path, as you have specified in your configuration instead of a relative path.