The settings that shape a DayZ server — player cap, day/night length, security, and the loot economy. What lives in serverDZ.cfg versus the mission XML files, sensible baselines for a friendly and a hardcore server, and what a restart does and does not reset.
DayZ splits its settings in two. serverDZ.cfg controls the server itself — the name players see, player cap, day/night length (time acceleration), third-person rules and the security settings that keep cheaters out. The loot economy is not in that file — it lives in XML inside your mission folder (mpmissions/dayzOffline.chernarusplus/db/), above all in types.xml.
Below are baselines for vanilla, Vanilla+ and hardcore, and which file each setting is in. Starting from scratch? See our how to set up a DayZ server guide first.
Running these settings on a VDS? DayZ server hosting gives you full control of serverDZ.cfg and your mod stack, behind our Anti-DDoS network.
What you'll need
- Access to your server files (a panel File Manager or SFTP).
- The file serverDZ.cfg in the server root.
- The mission folder mpmissions/dayzOffline.chernarusplus/: cfgeconomycore.xml at its root, types.xml, globals.xml and messages.xml in db/.
- The ability to restart the server to apply changes.
- BEServer_x64.cfg for BattlEye RCon settings.
Dial in your DayZ server, setting by setting
Step 1: Set server identity & player cap
In
serverDZ.cfgset thehostname(name in the browser), apassword/passwordAdmin,maxPlayersand amotd. Bohemia's example config uses 60; the documentation gives no fixed maximum, so lower it for a tighter community.hostname = "My ESAGAMES DayZ Server"; passwordAdmin = "changeme"; maxPlayers = 60;Step 2: Set day/night length (time acceleration)
Time acceleration is the setting players feel most.
serverTimeAccelerationspeeds up the whole clock (0.1-64).serverNightTimeAcceleration(also 0.1-64) is multiplied by it, so 8 and 4 make nights pass 32 times faster than real time.serverTimePersistent = 1saves the clock so the next start continues from it.serverTimeAcceleration = 8; // days at 8x serverNightTimeAcceleration = 4; // nights at 8 x 4 = 32x serverTimePersistent = 1;Step 3: Lock down security
Keep signature verification and same-build enforcement on.
verifySignatureschecks .pbo files against .bisign files, and 2 is the only supported value. BattlEye is not a serverDZ.cfg line: it readsBEServer_x64.cfgnext toBEServer_x64.dll, in the folder set by-BEpathor-profiles, where you set the RCon password.// serverDZ.cfg verifySignatures = 2; forceSameBuild = 1; // BEServer_x64.cfg RConPassword MyPassword RestrictRCon 1Step 4: Tune the loot economy (types.xml)
Loot isn't in serverDZ.cfg — it's the central economy in your mission's
db/folder.types.xmldefines, for every item, the spawnnominal(target count on the map),min,lifetimeandrestock. Raise nominal/min for more gear, lower them for a harsher server. The AKM below shows the shipped vanilla Chernarus values.<!-- db/types.xml (vanilla Chernarus) --> <type name="AKM"> <nominal>3</nominal> <lifetime>7200</lifetime> <restock>3600</restock> <min>2</min> </type>Step 5: Pick a difficulty profile
Combine the above into a profile. A friendly server might run 8 and 4 (nights at 32x) with default loot. A hardcore one might run 6 and 1, so nights pass at the same 6x as the day and last longer, with leaner loot and first-person only. Set third-person and crosshair rules to match.
// hardcore feel serverTimeAcceleration = 6; serverNightTimeAcceleration = 1; disable3rdPerson = 1;Step 6: Restart to apply, and shut down gracefully
Config and economy changes take effect when the server starts again. Bohemia highly recommends the graceful shutdown (the countdown in
db/messages.xml) over killing the process, to avoid side effects on player characters and on saving. A restart does not refill the map: the economy is persistent, andRestartSpawnindb/globals.xmlships at 0%.<!-- db/globals.xml -->
Stable, fair and tuned
Loot lives in types.xml, not the cfg
The single biggest confusion: serverDZ.cfg has no loot settings. Spawn rates, lifetimes and restock are the central economy in types.xml inside your mission db/ folder.
Time acceleration sets the feel
serverTimeAcceleration and serverNightTimeAcceleration are what players notice most. Short nights are friendly; long nights (1x) are the hardcore signature.
Keep security on
verifySignatures=2 and forceSameBuild=1 stop unsigned mods and mismatched clients. BattlEye lives in its own BEServer_x64.cfg, not in serverDZ.cfg.
Caps live in globals.xml
ZombieMaxCount (1000) and AnimalMaxCount (200) cap infected and animals across the whole map. simulatedPlayersBatch in serverDZ.cfg limits how many players are simulated per frame, for server performance.
Common problems & fixes
My loot changes did nothing
Loot is in types.xml inside the mission db/ folder, not serverDZ.cfg. Edit types.xml (nominal/min/lifetime/restock) and restart.
Config changes aren't applying
Restart after saving, and check the -config= launch parameter points at the file you edited. The config file can have any name, so a panel may be loading a different one.
Players get kicked for signatures/build
A mod isn't signed or clients are on a different build. Keep verifySignatures=2 and forceSameBuild=1, and make sure all mods are correctly installed and matched.
Nights feel far too short
serverNightTimeAcceleration multiplies serverTimeAcceleration. With 8 and 4, nights pass at 32x. Lower the night value, down to 1 for nights at the day speed.
DayZ is a trademark of Bohemia Interactive. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Bohemia Interactive. You must own a legitimate copy of the game to play.