I've found a couple of issues in this release. One is a typo in the logs.php file that affects command-line stat parsing.
To fix this, just change:
if ($setglobals = true) {
to:
if ($setglobals == true) {


The other involves UTF-8 encoding, affecting things such as map names and author names. I ...

The next version will include a check for the file with a friendly message instead of generating a critical error.

I started going through the documentation a bit more after I released this and I noticed that I failed to specify that the MySQL type is now "MySQLi" since the old database format is no longer supported in PHP. Setting it to MySQLi should resolve the issue for you.

UTStatsDB 3.10 has finally been released. Compatibility with newer versions of PHP, MySQL, SQLite, and even Microsoft SQL has been added.
Please note that there is no automatic upgrade path from older versions this time. You will need to start with a fresh database or reinitialize the existing one ...

UTStatsDB 3.10 is almost ready for release. Everything is working great with PHP 8.2 along with MariaDB 10.6 (and presumably MySQL), and SQLite 3. Additional testing, including with Microsoft SQL, will be completely soon. Some of the database methods needed to be rewritten due to the previously used ...

UTStatsDB is back, with updates to make it compatible with PHP 8 (including 8.2), plus various bug fixes and enhancements to the special event tracking. It's been tested a bit with MySQL, but I still need to test with Microsoft SQL and SQLite. One downside with this release is that I've not ...

There's an issue with the version 3.07 release that needed fixing. I'll repost it soon.

An issue was found in 3.07, so the release was immediately removed. An update is being worked on that now includes support for PHP 8. The original post for 3.07 is here:

This project has been long neglected, but I've finally released version 3.07 which includes support for MySQLi and newer versions ...

You don't need a mutator for UT '99 logging. Mainly, just make sure the following settings are configured in your Logs Config settings:

Log Path: <server path>/Logs/
Log Prefix: Unreal.ngLog.
No Port: False
All Logs: True
Multi-check: True

As long as you've set the query type to "Unreal" it should work, but you might also need to make sure any firewalls enabled (such as the Microsoft Windows Firewall) are allowing the port through.

I think I see the problem. The "fixed" database files I posted for MySQL 5.1 and newer were the wrong file set. They had been modified for the unreleased 3.07 version (I never completed the changes). I've posted corrected versions of the MySQL database files for version 3.06.

If you reinitialize the database, what happens? Do you still get the error that the database is newer?
Did all the files you're using come from the same UTStatsDB archive?

It slipped past me that there was a post awaiting approval (required only for new members due to past spam problems).
Did you get this resolved? You should update Apache (or make sure it's a patched version) by the way if you plan to have this publicly accessible.

The error is probably caused by the MySQL files using the deprecated TYPE parameter instead of ENGINE. I've uploaded an update to the file section. Just extract that to your tables/mysql directory.

Looks nice, I'll check it out more as soon as I have some time. Perhaps we can stick some of your mods in the official release. Unfortunately, I'd left off some time ago while making some major changes to the way some things are stored for better flexibility and need to figure out where I left off ...

Both WebSVN and direct SVN access now work again. SVN uses the standard guest user.

It was working, I'll look into it. It must have broken with the recent subversion update.

I'm looking into how we can restore guest access to the SVN repository via WebSVN. Meanwhile you can use an SVN client such as TortoiseSVN. Please keep in mind that the SVN version is not fully functional, but some components such as the server status utility may have been updated to work better.

Sorry about that, I didn't realize that people weren't able to post and failed to visit the site for some time. There's still a requirement for new users to have posts approved initially, but not people who we know aren't here to annoy everyone.

It looks like the code causing the problem might be earlier. Are there any directories within your Demos path?

Pretty much anything can be done, it's just a matter of someone spending the time to do it.
It sounds like you basically just want to have a look-up table to set the display name of the game types. This should probably be done by adding a column to the types table then redoing the section in ...

Moderation was enabled due to the barrage of spammers and I seem to have failed to check in on the forums in quite some time.

The uploading function seems to have been hit and miss. Some people successfully got it working while others didn't, with almost identical configurations. It's usually better to just have it pull them down via FTP or something. Query server is your server's IP address, and for UT3 you must use the ...

Linux is case sensitive, while Windows is not, so you'll need to adjust your image file names and you also have "UT3stats" instead of "UT3Stats" in your configuration.

I recall someone had mentioned seeing such a bug once before, so likely the math does need some tweaking. Unfortunately, it's not something I plan on going into anytime soon, but I'll post it in the changes if I do.

I don't remember exactly how I'd configured the system, but looking in a directory of sample files I found them in this format:
0318-0521-DM-Gael.demo4

Hopefully that helps, or perhaps someone else will respond now that I've finally approved these posts (for a long time only spammers were posting ...

The SVN version is a work in progress and does not necessarily consist of a functional configuration. I had started to make some fairly major code changes at one point but didn't finish. Maybe if there's ever a UT 4 I'll give it another go. In the meantime it's best to just stick to the last release ...

As far as I understand, you're still running the Windows or Linux versions of the server, so certainly, it's the same system. Your maps are just compiled differently.

Newer versions of MySQL have a separate permission for creating temporary tables. Just modify and execute the following to grant the permission to the database user:

GRANT CREATE TEMPORARY TABLES ON database.* TO dbuser@localhost;

Set "Allow Incomplete" to "Unknown/Map Change".