Top Banner

Server Start

Dedicated servers may be started by executing the shipped [install dir]\server\server.exe executable. Upon start up, it will load the current server configuration and initialize accordingly.

Alternatively, the client UI allows to start a linked server from the server selection screen. Note that any server started this way will not display a console window, and shut down automatically when the client closes. The server requires periodic heartbeats from the client in this mode. Should the client (for whatever reason) terminate prematurely, then the server will create an automatic save game at game folder\shared\saves\no-heartbeat-shutdown.hsf and then shut down after 3 seconds.

Starting the server via the visual client provides three options. You may visually configure the server before starting, run it with the current server configuration, or load a previously created save game.

Save Games

The server manages all save games. See save games for details. If you are not hosting the server, then you cannot create or load save games.

When starting the server using the client visual interface, then a menu option allows to start a new server directly with a previously created save game.


Regardless of how a server is started, it always creates a log file in game folder\server\logs\. In case of crashes, check these logs.

NAT (Network Address Translation, i.e. Routers)

The server requires two TCP ports to operate which must be accessible to anyone attempting to connect via TCP. By default these are 10247 and 10248. If you are located behind a NAT router, and you wish others to connect to you via TCP, then these ports must be forwarded to your physical server.

Runtime Parameters

For the more proficient users, a number of runtime parameters allow customization of more specific server settings. Execute server --help for a list of all switches.

If you wish to run multiple servers on the same system, then an adjustment of base ports is required. The current game base port is 10247. Starting from there, two more TCP ports are used (effectively: 10247, 10248, and 10249). Consecutive servers should thus allocate base ports (via the -p [base port] parameter) in steps of 3.

External clients trying to connect must specify non-default base ports as additional address parameter (yourhost:baseport), e.g. localhost:20000, if 20000 is your non-standard server base port. LAN computers will automatically receive these ports via the UDP discovery function.

Use the -p [base port] runtime parameter of a control console to connect to these servers.