XASECO2 Upgrade

Upgrading the dedicated server and XASECO2 can be done in either order, or each individually, when a new version arrives. To find your current versions, see the boxed area in XASECO2's log shortly after it has started. Compare to the version lists for the TM² dedicated server and for XASECO2 and upgrade if not the latest.

Differences

To learn about the differences between versions, read the relevant release notes. To see the differences between configuration files, especially new options that need to be added to your existing files, use 'diff' and 'dircmp' on Linux, or similar programs on Windows.

Dedicated server

Unpack the server distribution somewhere near your dedicated server tree, not overwriting that. Stop the running dedicated server, on Linux this can be done with an init.d script.

Copy the new dedicated executable (ManiaPlanetServer for Linux, ManiaPlanetServer.exe for Windows) to your server tree, overwriting the old one. Compare your existing UserData/Config/dedicated_cfg.txt file with the new one, and copy over any new entries. Compare the entire existing and new server trees for any new/changed files that might be relevant (this happens rarely).

Start the new dedicated (on Linux via init.d, see above) and check the start-up messages and the new Logs/ConsoleLog.##.txt file for problems.

XASECO2

Unzip the XASECO2 distribution somewhere near your XASECO2 tree, or, if you didn't make any custom changes to source code files, onto your existing tree, overwriting it. Stop the running XASECO2, on Linux this can be done with an init.d script.

The new configuration files are in the newinstall/ directory, and won't overwrite your existing files during the unzip. Compare your existing configuration files with the new ones, and copy over any new entries. If you didn't unzip the distribution onto your existing tree, compare all source code files and copy any custom modifications to the new files, then move all new source code files into your existing tree.

Start the new XASECO2 (on Linux via init.d, see above) and check the new xaseco2.log file (or logfile.txt) for problems.
Last updated: 2013-03-02