This has primarily been accomplished by disabling many features and commands, as establishing communication between master and relay(s) to pass through information is way beyond the spare time I have available lately (I believe FAST does offer such communication, if you really need that sort of thing). The relay support hasn't been tested extensively but is hopefully okay for most situations.Beyond that, there are some Dedimania-related enhancements, the previous hotfixes for the challenge list cache are now officially incorporated, as well as a couple of new fixes and other polishing. Here are the complete v1.14 release notes:
New features and other changes in the v1.14 release of XASECO:
- * new support for TMF relay servers:
- * on the master server, relays are now registered separately rather than considered spectating players
* on a relay server, the start-up log includes the login and nickname of the master server it relays to
* new /admin relays command to display (on the master server) the list of connected relay(s), or show (on a relay server) its master server
* the /admin server output is reorganized to make room for a line about the server's master/relay status on the first page
* on a relay server, the /server output includes the master server's login/nickname in place of the track count
* on a relay server are disabled:- * commands (e.g. /jukebox), events (e.g. checkpoints and finishes) and functionality (e.g. player reranking) that make no sense on a relay
* commands (e.g. /recs) and functionality (e.g. personal bests) that require information from the master server's database
* logging of chat messages from the master server (but they are still shown)
- * commands (e.g. /jukebox), events (e.g. checkpoints and finishes) and functionality (e.g. player reranking) that make no sense on a relay
- * identical logins from different games (e.g. TMN ESWC vs. TMU/TMF) are now associated correctly with their records in relevant commands, new/improved/secured/equalled chat messages, and the reports before and after each track
* when a login that is banned from Dedimania joins the server, this is announced with a general chat message, and finishes by that login are ignored (you may also want to activate the Dedimania global blacklist in rasp.settings.php to prevent them from joining in the first place)
* /admin setgamemode checks whether the game mode is actually being changed, and mode changes are now taken into account when restarting (thanks undef.de)
* the XML parser (parseXml in xmlparser.inc.php) has a new option to preserve UTF-8 encoding on extracted strings (for historical reasons the default is false), so now any plugin calling the parser can control UTF-8 encoding
* a new aseco.php configuration definition CONFIG_UTF8ENCODE controls whether UTF-8 encoding on strings in config.xml is preserved (default false as above) -- config.xml setting <welcome_utf8encode> is now obsolete
* tagged all generic warning/error messages from the dedicated server with the invoking method
* all included HTML documentation now passes the W3C validatator - * on the master server, relays are now registered separately rather than considered spectating players
- * the challenge list cache isn't always properly refreshed -- fixed (thanks jimos94)
* when XASECO is configured to use the global Dedimania blacklist on a server that didn't use it before, the initial bulk merge doesn't work -- fixed (thanks soehest)
* merging the global blacklist causes a bogus warning -- fixed
- Important:
* To register your server with the central Dedimania database, you must copy the login and password values in the <masterserver_account> section from your server's dedicated.cfg (TMN) or dedicated_cfg.txt (TMF) file into the corresponding section of the dedimania.xml file, and add the 3-character nation abbreviation. Instead of the password you can also use the community code for your server by using the server login/password on the official site for your game (TMO/TMS/TMN) or on this page for TMF.
* Open port 8002 on your firewall/router for communication with the central Dedimania server.
* In the zip file, all *.XML and *.PHP config files are now located inside the newinstall/ directory. This means that you can (and have to) unzip the download and replace all the PHP code files, without worrying about overwriting your customized config files. However, for every XML/PHP config file that was updated (see above), you must replace your version with the one from the newinstall/ directory, or compare them and add any new/changed configuration settings to your version to insure the system remains working correctly.
* For a new installation, go into the newinstall/ directory and move all *.XML files into the main directory, next to aseco.php, and *.PHP files into the includes/ directory.
Cheers,
Xymph
