How to set up a DayZ server: mod load and the central economy

This guide builds a working DayZ server from scratch: choosing the operating system, installing through SteamCMD, configuring serverDZ.cfg, opening ports, installing mods and tuning the central economy. Two things separate DayZ from other survival games: the mod list drives most of the resource requirement, and because the server tracks every object on the map, a server that has not been reset in a long time consumes several times more at the same player count.

Before you start: what you need

• A server sized against your mod list. A vanilla Chernarus server runs on 8 GB up to 40 players. A 60-player server with a moderate to heavy mod list goes past 12 GB, and storage needs double or triple along with the mods. So the correct order is: finalise the mod list first, then choose the plan. To pick resources once the mod list is settled and see the monthly total: server configurator
• A real Steam account. Server files download over an anonymous session, but Workshop mods do not; downloading mods requires you to log in.
• Fast storage. Mod downloads and verification are storage intensive, and disk latency directly sets how long the server takes to come up: what is an NVMe SSD?

1. Operating system

Choose Ubuntu 22.04 LTS and tie the server process to a separate user created only for DayZ. SteamCMD needs 32-bit libraries; without the distribution's 32-bit compatibility packages the first command fails with an opaque error.

The longer the mod list, the longer the server takes to boot. Treat that as part of your maintenance plan rather than a fault: after a mod update the server will be down for a few minutes, and announcing that window in advance beats having players assume it crashed.

2. Installing with SteamCMD

Server files are downloaded with an anonymous Steam session:

./steamcmd.sh +force_install_dir /home/dayz/server +login anonymous \
  +app_update APPID validate +quit

Replace APPID with the Steam application ID of the DayZ dedicated server; the correct value is in the game's official server documentation. Mods arrive by a different route: you download Workshop content with your own Steam account through a separate SteamCMD command. An anonymous session will not work for that step.

Define the server as a systemd service with Restart=always.

3. serverDZ.cfg and the mission folder

The server name, passwords, player cap, day/night cycle and restart behaviour live in serverDZ.cfg. Do not leave the admin password (passwordAdmin) empty; that password is remote control of the server.

The actual game data lives in the mission folder. That is where you tune the central economy: how many of each item exist on the map, how often they respawn and how long they stay on the ground. Leaving these at their defaults is the most common planning mistake in DayZ, because this is the real mechanism that governs object accumulation. When the server slows down, the first place to look is these item counts, not the hardware.

Persistent data — player structures, vehicles, loose items — is kept in a separate storage directory under the mission folder. That is exactly what you back up; copying the whole install directory means needlessly duplicating hundreds of gigabytes.

4. Ports

Open the whole range; DayZ uses a consecutive port range rather than a single port. If the query port is closed the server runs but never appears in the public list — the most common cause of "my server is up and it is not in the list".

5. Installing mods: a two-step job

Installing a mod in DayZ is not one step, and skipping the second step is the most widespread mistake.

Step one: put the mod folders in the server directory and add them to the mod list in the launch parameter in order. Order matters: a mod that depends on another must come after the one it depends on. When the order is wrong the server either fails to start or behaves as though the mod were never loaded, without a clear error in the console.

Step two: copy each mod's verification key file into the server's key folder. Skip this and the server starts cleanly and you assume everything is fine — but every player who connects is kicked with a verification error.

When a mod updates, restart the server and copy the key files again. A version mismatch blocks players from connecting entirely.

The most common first-boot mistakes

1. Not copying mod keys. The server starts and no player can connect.
2. Not ordering mods by dependency. Mods silently fail to load.
3. Opening the game ports and forgetting the query port. The server does not appear in the list.
4. Leaving the central economy at its defaults. Object accumulation eats resources over time, and bigger hardware does not fix it.
5. Never resetting persistence. A server left unreset consumes several times the resources at the same player count.
6. Choosing a plan before the mod list is settled. The gap between vanilla and heavily modded is more than one step.
7. Backing up the entire install directory. What needs backing up is the persistence directory.

Monitoring resources

In DayZ the hardware decision is not a one-off. The central economy runs continuously and accounts for a significant share of CPU use, and the number of tracked objects grows as players build. If the server runs comfortably in month one and chokes in month three, the cause is usually not shrinking hardware but growing load.

The practical approach: watch persistence size and memory use weekly, see the trend, and stay on a virtual server that genuinely reserves your resource ceiling. In a shared, oversold environment that trend cannot be measured at all, because neighbour load mixes into whatever you are measuring.

On DDoS

DayZ carries all game and query traffic over UDP. Because a UDP source address can be forged, floods cannot be blocked at the application layer, and the query port is also a surface exposed to reflection attacks. How the attack types differ and how the protection works: what is DDoS protection?

On Datafex servers, layered Fexwall DDoS protection runs on every plan at no extra cost.

Next step

We have put the recommended plans by player count and mod list, the processor options and the DayZ-specific questions on one page: DayZ server plans.