i have attached a sample configuration to create a dedicated server by
using the server-init.cfg file. I have seen an example directory for
the redeclipse server package and figured it could be a good idea to
include one for sauerbraten as well.
I've also attached an example file describing the use of cron and
screen which is heavily influenced by the openarena server package in
I think this could help new admins with the administration of the
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sauerbraten-server depends on:
ii libc6 2.13-32
ii libgcc1 1:4.7.0-8
ii libstdc++6 4.7.0-8
ii zlib1g 1:1.2.7.dfsg-1
sauerbraten-server recommends no packages.
Versions of packages sauerbraten-server suggests:
pn sauerbraten <none>
//// example configuration for a dedicated and public Sauerbraten server
//// copy your custom server-init.cfg to the home directory of the sauerbraten user
//// you have to create the user with adduser first, disabling shell access is recommended
//// the whole server documentation is available at http://sauerbraten.org/docs/config.html
//// optional specific IP for server to use
// serverip 18.104.22.168
//// optional specific port for server to use (default port is 28785)
//// to make your server accessible from the internet you have to open the serverport and serverport +1
//// for this example open udp port 28785 and 28786 for internet games in your firewall
//// regardless of what ports are set, port 28784 must be available for pinging servers over a LAN to work
//// for pure internet games opening port 28784 is not necessary
// serverport 28785
//// maximum number of allowed clients
//// maximum number of bots a master can add - admins are unaffected by this limit
//// set to 0 to disallow bots
//// controls whether or not the server is intended for "public" use
//// when set to 0, allows "setmaster 1" and locked/private mastermodes (for coop-editing and such)
//// when set to 1, can only gain master by "auth" or admin, and doesn't allow locked/private mastermodes
//// when set to 2, allows "setmaster 1" but disallows private mastermode (for public coop-editing)
//// description the server shows for the server browser
serverdesc "A Sauerbraten server powered by Debian"
//// password required to connect to the server
//// generally unnecessary unless you really don't want anyone connecting to your server
// serverpass "your_secret_server_password"
//// password that allows you to gain admin by "/setmaster your_secret_admin_password"
// adminpass "your_secret_admin_password"
//// controls whether or not the server reports to the masterserver 0=disabled, 1=enabled
//// optional message of the day to send to players on connect
servermotd "Welcome to Cube2:Sauerbraten"
Running the server with cron and screen
You can run the server in a screen(1) session and from a cron @reboot action.
This can be used to run multiple instances of the server; you'll need to set
a different serverport on each server after the first. It's safest to create a different user
and server-init.cfg for each server. You have to create the sauerbraten user first and you
should also disable shell access by pointing the shell to /bin/false.
To do this, you could put something like this in the sauerbraten user's