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 dedicated 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. Should the client (for whatever reason) not close regularly, then the server will continue running until the client is restarted and/or the server is closed manually via the client UI.

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.


Regardless of how they are started, all servers create a log file in game folder\server\logs\. In case of crashes, check these logs.

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

Hosted servers provide their services both via TCP and the Steam peer-to-peer API. With the exception of localhost connections, clients typically connect via Steam, which is capabable of automatically circumventing any NATs (e.g. your router) in the way. Unless some permanent IP/URL-based host is intended, no router configuration changes are necessary.

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. A third port (by default 10249) allows console control access from localhost, but is of no relevance to hosting.

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.

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