Make Servers Automatically Update

You need to have the HLDSUpdateTool installed for this all to work (Please see http://www.steampowered.com downloads page) - its usually at the bottom right by the dedicated server area.

To automatically keep your server up to date, please edit autoupdater.cfg to tell it what server(s) you are running and your preferred options. You'll find autoupdater.cfg in your hyperbol folder. If you ran the server installer, it will be in that folder.

Note: your server does NOT have to be official in order to auto update itself with the autoupdater!

Here's an example autoupdater.cfg:

serverinstance: -configfile "hostoptions.cfg" serverinstance: -configfile "hostoptions-elimination.cfg" serverinstance: -configfile "hostoptions2.cfg" -console serverinstance: -configfile "hostoptions-mydm.cfg" -serverip 1.2.3.4 -console

The auto updater ignores all lines not starting with "serverinstance:" Each serverinstance line it finds represents a server. This example would therefore start 4 different servers with different configs. It would automatically add the -autoupdate command line option to them, so there's no need for you to do that. Once you've created or edited this file, you simply run ServerAutoUpdater.exe to automatically launch all the servers.

It launches them one by one, slowly.

You need to have the HLDSUpdateTool installed for this all to work (Please see http://www.steampowered.comdownloads page).

LINUX users You might be able to use this tool, if you install the Windows version of the HLDSUpdateTool, using WINE.A Linux version of the auto updater may be forthcoming.

How it works

When a game server finds out that there's a new version, the game launches a single instance of the auto updater. It will then start sending messages to all connected players, every couple minutes, that the server will go down for auto updating. When nobody remains in the server, or its the end of the map, the server will quit. The auto updater waits until all such servers have quit, up to a maximum of 30 minutes. It then terminates all instances of the HBDS.exe, and performs an auto update. Then it loads the config file, and uses it to restart each server, one by one.