Workload · Hosting a Holdfast battlefield

Holdfast dedicated server for your regiment, set up properly

A Holdfast: Nations at War dedicated server is a free download from Steam (app 1424230, anonymous login, Windows or Linux) that you run from a copied config file, with the UDP ports from that config open to players. This page walks through the install on Ubuntu, the settings that matter, the map rotation block and the admin login, then shows what kind of machine keeps a full line battle smooth.

The short version
  1. Free server files through SteamCMD, app 1424230, no second game licence needed
  2. The example config's UDP ports: 20100, 8700 and 27000
  3. Map rotation is a block inside your own config copy
  4. Several instances fit on one machine, each with its own ports

What the server asks of a machine

Like most game servers, a Holdfast battle leans mostly on one fast processor thread; beyond that it needs enough memory for the players you invite and a short trip to where they live. Size it by measuring a full round rather than by trusting a number on a hosting advert.

Set maximum_players to the roster you expect; a full line battle is when a slow core starts to show. Our game server page explains why one fast thread decides how a game server feels, and ranks the processors we sell by that single-thread score.

What you planWhat to look at firstWhy
One public or practice serverA processor near the top of the single-thread tableOne battle leans mostly on one core
Two to four servers, say a line battle and a naval eventMore cores, with each still fastEach instance is its own process on its own ports
Events with full rostersMemory headroom, then watch real usageMeasure a full round rather than guess a per-player figure

Before ordering anything big, start one instance, fill it for a round, and read memory and processor use with top. That number, not a guess, tells you how many instances one machine will carry.

Why a whole machine suits a regiment server

A whole machine means nobody else's workload competes for the core your battle runs on. You rent the server outright, with root or Administrator access and no other customer on it, so you choose the operating system, the number of instances and when they restart.

  • The port is unmetered. Nothing counts the traffic, and the port is not shared with another customer at the access switch, so a busy weekend event costs the same as a quiet Tuesday.
  • Monthly, no contract. Run it for an event season and stop when the regiment does.
  • Five cities. New York, Miami, San Francisco, Amsterdam and Bucharest; time each one from your browser on the locations page before you choose.
  • A person when you want one. Our AI chat answers in seconds and can check your server for you, and a person takes over whenever you ask.

The server that fits your battles

For one server and a regiment of friends, a single-socket machine with a quick core and NVMe storage is the sensible start; the Intel Xeon E3-1585L v5 line is sold in all five cities. For a community running several servers side by side, the many-core AMD EPYC machines keep a fast thread for each instance and take a lot of memory. The Intel Xeon E-2286M has one of the quickest cores we sell and is offered in Bucharest.

Every build, with its current price, is on the game server page; the full catalogue of lines is on dedicated servers. A machine already in the rack is handed over about 30 minutes after the order is approved, and the payment check before that is the part that varies.

Up and running in an evening on Ubuntu

The install is SteamCMD, Valve's command-line downloader, fetching app 1424230 into a folder owned by an ordinary user. Choose Ubuntu 24.04 at checkout (see Linux servers), sign in over SSH, and run the steps below. The SteamCMD package shows a Steam licence prompt you must accept.

# 1. SteamCMD from Ubuntu's multiverse repository
sudo add-apt-repository multiverse && sudo dpkg --add-architecture i386 && sudo apt update && sudo apt install steamcmd

# 2. A user that owns the game files, never root
sudo useradd -m -s /bin/bash holdfast

# 3. Download the server; run the same line again to update it
sudo -u holdfast /usr/games/steamcmd +force_install_dir /home/holdfast/server +login anonymous +app_update 1424230 validate +quit
  1. Still signed in as your admin user, open the UDP ports from your config in the firewall with the block below, SSH first.
  2. Switch to the game user with sudo -iu holdfast and go to the install folder with cd ~/server, then copy the example files to names of your own, for instance cp serverconfig_default.txt serverconfig_regiment.txt and cp LaunchServer.sh LaunchRegiment.sh. Edit copies rather than the originals, because a SteamCMD update with validate can replace the shipped files. Do the editing, the chmod and the launch as this user too.
  3. Point your copied launch script at your copied config, then set the name, ports, admin password and rotation in the config (next section).
  4. Start the server as the holdfast user with ./LaunchRegiment.sh from ~/server, inside tmux or under a systemd service so it survives your SSH session closing. If you write a service, do it from your admin user with the service set to run as holdfast; systemctl enable --now starts it today as well as at boot.
  5. Find it in the in-game browser or share the address and port with your players.
# SSH stays open, then the example config's ports
sudo ufw allow OpenSSH && sudo ufw allow 20100/udp && sudo ufw allow 8700/udp && sudo ufw allow 27000/udp && sudo ufw enable

On Ubuntu, ufw applies the same rules to IPv6 while IPV6=yes is set in /etc/default/ufw, which is the default; check it so the server is not left open over IPv6. On Windows Server, use the Windows launch script shipped in the install folder instead and allow the same UDP ports with New-NetFirewallRule -DisplayName Holdfast -Direction Inbound -Protocol UDP -LocalPort 20100,8700,27000 -Action Allow.

The config file: ports, password and rotation

Everything about a Holdfast server lives in one plain text file of settings, one per line. The example config sets three port values; give each instance on the same machine its own set of all three so they do not clash.

server_name Your Regiment Line Battles
server_port 20100
steam_communications_port 8700
steam_query_port 27000
server_admin_password a-long-random-secret-only-admins-know
  • server_port carries the game traffic, and steam_query_port and steam_communications_port are the two Steam ports in the example config; open whichever ones your config uses.
  • A second instance needs a second config and launch script with three fresh ports, for example 20101, 8701 and 27001, each opened in the firewall too.
  • The rotation is a block in the config; copy its exact layout from the example file shipped with the server, and take the map and mode names from there too rather than typing them from memory.

Once the server runs, join it and sign in from the in-game console with the admin password; the official wiki's remote console page lists the login command and every admin command. Anyone who knows that password can kick, ban and change maps, so give it only to officers you trust and change it when one leaves.

Keeping it healthy

  • Updates. When the game patches on Steam, stop the server and run the SteamCMD line again so it matches what your players have. Add validate, as above, if files ever look damaged.
  • Backups. The work you would lose is your copied configs and launch scripts. Copy them somewhere other than the server after every change.
  • The password file. The config holds the admin password in plain text, so keep it readable only by its owner with chmod 600 serverconfig_regiment.txt.
  • Restarts. Pick a quiet hour for your players and schedule updates then, not in the middle of a weekend event.
  • A clean slate. If an experiment goes wrong, you can reinstall the operating system from the control panel for free; save your configs first.

When this is the wrong place to run it

We do not sell a game panel, install mods or update the game for you; you install and run Holdfast yourself. No attack filtering is sold on any machine, as a feature or an extra, so a well-known public server that draws hostile traffic needs its own plan for that before it opens. And if you only want a private practice match, the dedicated server tool in your own Steam library is enough to try the settings first.

Questions people ask

Do I have to buy Holdfast again for the server?
No. The dedicated server is a separate free Steam app, number 1424230, and SteamCMD downloads it with an anonymous login. You only need a copy of the game to join and play on it.
Which ports do players need open?
The example config uses UDP 20100 for the game plus 8700 and 27000 for Steam; open whichever ports your config uses, and the new numbers if you change them. Give every instance on the same machine its own set.
Linux or Windows for a Holdfast server?
Both are supported, with a launch script for each: LaunchServer.sh on Linux and the Windows launch script shipped in the install folder on Windows. Linux needs no licence, while Windows Server is added on the order form with its licence priced there. Pick the one you are most at ease running day to day.
How many players can one server take?
Set maximum_players in your config to the roster you expect. How smoothly a full server plays depends on the processor's single-thread speed, so fill one round and watch the load before running bigger events.
Can one machine run a line battle server and a naval server together?
Yes. Give each one its own config file, its own launch script copy and its own three ports, and open all of them in the firewall. A processor with more cores keeps a fast thread free for each.
How soon can my regiment play?
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 SteamCMD download and your settings.

Get a server for your regiment

Pick a processor by its single-thread score, a city near your players and the memory you need, then install Holdfast as soon as the machine is yours. Monthly, no contract.

Find your battle server

Read next