If you mean how do you set a time limit on a match, set the TimeLimit variable for your match type, such as:
[XGame.xDeathMatch]
TimeLimit=30

If you mean how to check for two human players simultaneously, well, I'd say you just need to set a flag and do a check each time someone logs in. If someone ...

For anyone using MySQL 5.5 or newer, you will need to make a couple changes to includes/logsave.php. The "Type" option was renamed to "Engine" when creating tables. Change the queries that create temporary tables using "Type=" to "Engine=". If you need to rebuild the tables you'll have to do the ...

It might be more worthwhile to pursue code that would check for two human players online simultaneously. Also, perhaps a time limit for a match, even if it's an hour or something might help. Those are my thoughts anyway.

Sorry for the delay - things have been busy here. Many of the kills are definitely not getting logged at all, just the score events. I don't know why this would be, perhaps a conflict with another mutator. Is one player logged in locally on the game server?

You can just send the log then, along with a screenshot of the main match stats that the log is for. I need the log for the match (from UT2004).

Post a log or two and a link to the stats site and I can have a look.

Ah, I see. That might be because the file only exists in the unreleased new version of UTStatsDB that's still under development. One of these days I'll likely get back to it. Meanwhile, here are a couple of sections that may apply to you ...

Oh, I missed that part. That's the problem with reading posts from a phone. Did you have a look at the notes in the docs/LOGGING.txt file?

The query should work fine with a host name instead of an IP address, so I don't know why it wouldn't work unless there's some problem with DNS queries on that server.

As for getting your logs over, the easiest method is likely to configure the FTP option in your stats to get them from your game ...

Yes, you can extract the images from the maps, but you'd probably have to load them in the editor.

F9 takes a screenshot.

The ranking system works like chess rankings where the rankings of your opponents affects your gain/loss. You'll gain far more points by doing well against a high ranked opponent than a low one.

Well, yes, play against other humans.

Simply edit the values in the formatdate function in includes/main.inc.php. You can add additional options to the three included. There are two sets - one with and one without the time.

I will look into improving the error handling so that it informs you if it wasn't able to connect to the server. Currently it only throws the correct error if it's not able to initialize the socket on the local system.

The libraries that were written for handling HTTP requests through UT3 don't seem to work reliably and as far as I know nothing has been done with them for ages so I wouldn't hold my breath on the automated method. If you can, set up a cron script to retrieve the logs for you.

It's possible that there's a firewall blocking the outgoing ports from the webserver. Check with your host provider.

Using a stock version of UTStatsDB 3.05 (I also tried the newer version of utserverquery.php with the same results) I didn't have any problem displaying your 2004 or UT3 server stats:
http://www.utstatsdb.com/demo/

Does your PHP configuration include sockets support? You can check by creating a PHP ...

Try the current SVN version of serverquery.php:
http://www.utstatsdb.com/websvn/dl.php? ... hp&rev=135

That's a long password! Trying for the Guinness Book of World Records?

You need to set the "game port" to 6500, since for the UT3 protocol this field is actually set to the query port. The default query port for UT3 is 6500, but it can actually be something else if that port is already in use. It's ...

That's because all the new changes have not been fully implemented in the versions of the files currently on the Subversion server. You would either need to stick with the releases, or finish the modifications I started and send in the completed version...

There is no size limit in current versions. A long time ago UTStatsDB (which it wasn't even called at the time) would load the entire log file in at one time to parse it but now it simply reads it one line at a time, up to 1,536 bytes (if a line is over 1,536 bytes then it's going to get truncated ...

The admin password is stored in the SQL tables. Only the init password exists in the statsdb.inc.php file.

Not that much difference between 3.05 and 3.06. Try clearing your cookies for the site.

What version did you upgrade from?

Please post a log file.

If your account wasn't activated then you wouldn't be able to post.

Have you tried disabling any other mutators on your server?

It is correct that carjackings are not being logged by OLStats. What version are you running?

Everything should be okay there. Upload a log file in which carjackings and road rampage occurred so I can see if the events are being logged by OLStats.