What the game asks of the machine
Xonotic publishes requirements for playing the game, not for hosting it, so the honest answer is a short list of facts and a lot of headroom. The 4 GB of memory on the download page is the figure for the game client with its graphics; the project states no separate number for a dedicated server.
| Item | What the project states |
|---|---|
| Release | Xonotic 0.8.6, one zip of 1182 MiB with a published SHA-512 sum |
| Platform | Linux x86-64 with glibc 2.29 or newer; Windows and macOS builds in the same zip |
| Server scripts | server_linux.sh, server_mac.sh and server_windows.bat in the server folder |
| Port | 26000 UDP by default, set with the port line in server.cfg |
| Player slots | maxplayers, shown as 8 in the example config, spectators included |
| Server frame rate | sys_ticrate 0.0333333 (about 30 frames a second); 0.0166667 doubles it for somewhat higher CPU use |
Check the library version on a fresh system with ldd --version before you download anything. Leave disk room beyond the zip for the unpacked game and your maps.
Why a whole machine suits a match server
A fast shooter punishes a server that stalls, and the thing that stalls first is the processor thread running the game loop. On a machine you rent whole, that thread belongs to your server alone: no neighbour on the same box borrows it during a busy evening.
- Picked by its fastest core. Our game server machines are ranked by PassMark single-thread score, so you choose the processor on the number that matters here.
- An unmetered port nobody else shares at the access switch. Players pulling a custom map package on join, or a long evening of matches, is never counted.
- Five cities. New York, Miami, San Francisco, Amsterdam and Bucharest. Put the server where most of your players live; distance is most of their ping.
- Full root access and monthly billing with no contract. Run the release exactly as the project ships it, and stop paying when the community moves on.
The machine that fits
For one public server and a group of regulars, start with the Intel Xeon E3-1585L v5: it clears the single-thread bar on our game list, has NVMe storage and is sold in all five cities. If raw speed on one thread is what you want, the AMD EPYC 72F3 tops that list, in New York and Bucharest.
Planning a duel server, a CTF server and an instagib server side by side? Each is its own process on its own port, so a processor with more cores keeps a quick thread for every one. Browse the full catalogue on dedicated servers, or take a finished machine from the instant servers list as it stands: one already in the rack is handed over about 30 minutes after the order is approved, and the payment check that comes first is the part that varies.
Up and running in an evening
These steps assume Ubuntu or Debian, picked at checkout, and an ordinary user called xonotic that you create for the server. Never run a game server as root.
- Install the tools the steps and the updater need:
sudo apt install wget unzip rsync screen. - As the xonotic user, download the release and its checksum, verify the zip, unpack it and copy the example config into the data directory. Each command runs only if the one before it succeeded, and
cp -nnever overwrites a server.cfg you already have. - Edit
~/.xonotic/data/server.cfg(the settings below), then open the port. - Start the server inside GNU screen, which the project recommends:
screen -S xonotic ~/Xonotic/server/server_linux.sh. Detach with Ctrl+A then D, and come back withscreen -r xonotic.
wget https://dl.xonotic.org/xonotic-0.8.6.zip https://dl.xonotic.org/xonotic-0.8.6.sha512
grep ' xonotic-0.8.6.zip$' xonotic-0.8.6.sha512 | sha512sum -c - && unzip -q xonotic-0.8.6.zip && mkdir -p ~/.xonotic/data && cp -n Xonotic/server/server.cfg ~/.xonotic/data/ && chmod 600 ~/.xonotic/data/server.cfg
You can run the script from the server folder without copying it: when it finds the dedicated binary one level up and your server.cfg in ~/.xonotic/data, it starts the binary with +serverconfig server.cfg. That matters later, because the updater removes files you added to the game folder.
Firewall: allow SSH before you switch ufw on, or you lock yourself out. The ufw manual says IPv6 must be enabled in /etc/default/ufw for IPv6 rules to work, so check that it reads IPV6=yes first; then each rule covers both address families.
sudo ufw allow 22 && sudo ufw allow 26000/udp && sudo ufw enable && sudo ufw status verbose
The example config recommends moving off 26000 to a free port above 1024, because some internet providers filter well-known game ports. If you do, change the ufw rule to match.
The server.cfg lines worth your time
Nearly every line in the example file starts commented out with two slashes; remove them and change the value.
| Setting | What it does |
|---|---|
| hostname | The name on the public server list |
| sv_public | 1 lists the server publicly; 0 or -1 keeps it off the list |
| sv_motd | The message shown on connect: a good place for how to reach you |
| sv_termsofservice_url | Your server's terms of service, shown in the server info dialog (right-click the server in the multiplayer menu) |
| maxplayers | Slots, spectators included |
| port | The UDP port players connect to |
| gametype | dm, tdm, ctf, ca, ft and the other modes listed in the file |
| g_maplist | Maps in rotation; empty means every map that supports the mode |
| rcon_password | Remote console password; empty keeps rcon switched off |
| log_file | Copies console output to a file |
Two lines are active as shipped. sv_vote_gametype 1 holds a game-mode vote after every match, and sv_weaponstats_file sends weapon-balance statistics, along with your server's address and name, to the Xonotic project. The comment above the statistics line lists exactly what goes and says no player data is included. Read it and decide whether to keep each of the two.
In the console, cmdlist and cvarlist print every command and setting, and status shows who is connected.
Custom maps your players can fetch
Maps come as .pk3 packages. Drop them into ~/.xonotic/data and the server can run them; players who lack a map download it over HTTP or FTP from an address you give the server. The project's map download notes prefer HTTP because it works better for players behind firewalls.
- Set
sv_curl_defaulturlto the web folder holding your packages, ending in a slash, since the engine appends the package name. - For different sources per package, a
curl_urls.txtfile in the data directory maps name patterns to URLs; the first matching pattern wins, and a dash means do not offer that package. - If the web server runs on the same machine, keep the packages under its own web root. Ubuntu 24.04 home directories are mode 0750, so a web server cannot read them from inside a home folder.
Updates, backups and remote control
New releases arrive through the rsync updater that ships with the game: cd ~/Xonotic/misc/tools/rsync-updater && ./update-to-release.sh. It needs rsync installed.
The updater deletes any custom files inside the Xonotic folder, and asks you to confirm before it does. Keep server.cfg, maps and anything else of yours in ~/.xonotic, stop the server first, and copy ~/.xonotic to another machine before every update.
Xonotic has a QuakeWorld-compatible rcon. If you set rcon_password, make it long and keep it in server.cfg, which the install step left readable by the xonotic user alone; if you only ever manage the server over SSH and screen, leave it empty and rcon stays off. To remove a player, run status to see each player's number, then kick # 3 removes player 3 (note the space after the #).
When this is the wrong place to run it
- You want a game panel, one-click mod installs or someone else to apply updates. We hand over the machine with root access; installing and updating Xonotic is yours.
- Your players are spread across continents. No hardware fixes distance, so some communities run one server per side of the ocean, and test the round trip from each city on the game servers page first.
- You only need a private match for a handful of friends now and then. A whole machine is more than that asks for. For another small open-source game run the same way, see our Luanti world guide.
Questions people ask
- Which port does a Xonotic server listen on?
- UDP 26000 unless you change the port line in server.cfg. The example config suggests a free port above 1024 instead, since some providers filter common game ports. Whatever you choose, open that UDP port in the firewall for both IPv4 and IPv6.
- How do I get the server onto the public list?
- Uncomment
sv_public 1in server.cfg and give it ahostnameplayers will recognise. Setsv_motdwith a way to reach you too. To keep a private server off the list, use 0 or -1 instead. - Can one machine host several Xonotic servers?
- Yes. The readme says that for several servers you rename server.cfg for each one and change that name in the start script. The updater replaces or deletes edited scripts in the Xonotic folder, so keep a note of your edits in ~/.xonotic and re-apply them after each update. Give each its own port and its own log file.
- Will updating the game wipe my maps and settings?
- Not if they live in ~/.xonotic/data, which sits outside the game folder. The rsync updater deletes custom files only inside the Xonotic folder itself, and it asks before doing so. Back up ~/.xonotic before any update anyway.
- Can I run it on Windows Server?
- Yes. The release has server_windows.bat, and the readme puts the Windows config in %UserProfile%\Saved Games\xonotic\data. Windows Server is offered at checkout with its licence added on the order form; Linux needs no licence.
- How soon can players connect?
- A machine already in the rack is handed over about 30 minutes after the order is approved; the payment check comes first and is the part that varies. After that it is the release download and your server.cfg edits.