It sounds as though the cron job user does not have write access to your local log directory. Your web server user has write access, however. Just change the permissions on the log folder.
As for chat logs, I've never even heard of ACLS, so there is no support for it in UTStatsDB.
To answer some of your other questions - you do not need to run any of the ngStats utilities, you just need to have the log files created. The logs are in UTF-16 format which is a 16-bit format, even though only 8-bits are actually used for the stats. UTStatsDB automatically detects and parses these ...
If I recall, it is possible to save logs using the OLStats mutator version, but UTStatsDB is designed to work with PHP and a web server. OLStats does have the ability to generate its own web pages, but I don't know if it does this when playing instant action. You'll find support for OLStats at http ...
UTStatsDB does indeed work with UT '99. OLStats works only with UT2004. UT '99 has logging capability built-in. The prefix for UT '99 is normally "Unreal.ngLog.". For automatic parsing simply configure a scheduled task to run the log parser periodically. If you're using MySQL there is no concern of ...
I've added multi-page ranking lists, with the ability to search by player ID which will take you to the page with that player on it.
If you would like to see these changes and others, download the SVN version of UTStatsDB but don't run it as your live server stats - upgrading from SVN releases is ...
For one thing different versions of UTStatsDB are configured differently.
Simply set "Max Matches" in your main config options to how many matches you want to keep and UTStatsDB will remove all older matches.
Some of the changes you listed are somewhat dependent on the admin's preferences I'd say, but I know that I should at least finish the help page. Long ranking pages - do you mean where there are a lot of different game types, or separating the pages when listing the top 100? As for the UTStats code ...
An extremely useful feature of the exisiting UTStatsDB interface is the Server Status... and I'm sure you'll carry that forward into the next version. I've put some time into researching and coding my own UT3 Server Query... UT3 server query support has been integrated into the development version ...
The rankings are by different game types, but instagib is a mutator, not a separate game type. Still, it can be done, but would require modifying the log parser to check for the instagib mutator and redefine the game type.
What you want is to set the Backup folder path in your logs configuration. This should be a relative or direct path to a server writable directory to save successfully parsed logs.
Well, your problem with SQLite is apparent that it's either not installed or not enabled in PHP. Check your php.ini file and make sure your php_sqlite.dll extension is enabled.
Well, yes, the server query has been modified to work with UT3, but the stats system is still rather useless without logs, so I'm waiting for someone to come out with a stat logger so I can finish UT3 support. You can utilize serverquery.php from SVN, but there's one slight difference with UT3 in ...
Use the local IP that the server is listening on for the "Query Server" field (you can use 127.0.0.1 if you didn't limit which address it listens on). Then the port that the server is listening on in the "Game Port" field - this is 7777 by default. Query type must be set according to your server ...
By default a player must log at least 5 matches and 10 minutes of game time before they can be listed in career highs. This is adjustable in the main settings ("Min. CH Matches" and "Min. CH Time").
As for the server status - just fill in the required info under Query ...
Extract that to a directory called "mapimages" within your UTStatsDB path and they'll automatically be checked in order to display map images with queries on the main page and within the map pages.
I have used utstatsdb with Ut99, 2k3, & 2k4. I know that 2k3 didn't log local stats and users need a mod for this. Hopefully, such a fix will come along for UT3.
BTW, nice new phpBB3 forum Panther. 8-) Thanks, I figured the UTStatsDB project site could use an overhaul....in preparation for when ...
As we continue to migrate all UTStatsDB services to the utstatsdb.com domain, users and posts were not copied from the old forum so it will be necessary to register again.
When posting about any issues you might have, please include the following information:
UTStatsDB version
Operating system and version
Database type and version
PHP version
Web server and version
Unreal Tournament version
Stat logger type and version