Step 01
Download and install
One package, one script, one desktop icon. Chapter 7 shows it in five steps.
This manual takes you through all of it once: download, install, set up, run. One chapter after another, in the order you actually need them.
Step 01
One package, one script, one desktop icon. Chapter 7 shows it in five steps.
Step 02
A one-off setup on the first start. Chapter 8 walks you through it.
Step 03
Name, map, done. DZSS allocates the ports itself.
Step 04
The everyday work. Chapter 9 has a guide for each task.
The application itself is in English. Labels therefore appear in this manual exactly as you see them in the program, for example New instance…. Only the explaining text is translated.
Before you start, you should know what you are getting into. It takes a minute and saves you trouble later.
DZSS Server Studio is built with care and runs on real servers, but it is not finished.
The program is under development. Features may change, move or disappear again. It may contain bugs nobody has found yet, and it may behave differently from what this manual describes.
You run DZSS on your own machine and for your own servers. The program does what you tell it to, including resetting and deleting saves. Check what you just clicked before every larger step.
There is no assurance that DZSS works without faults, is available at all times or is fit for any particular purpose. Nor is there any claim to further development, to a specific feature or to an answer within a given time.
You are responsible for your data, your servers, your configuration and above all your backups. By default DZSS backs up automatically when starting, stopping and restarting and before every restore, and on request while running as well; but that does not replace a backup of your own in a second place.
Keep it simple: a copy of your own before you change anything major.
Use is free of charge. Liability for damages, data loss, downtime or misconfiguration is excluded as far as the law permits. This does not affect liability for intent and gross negligence, for injury to life, body or health, or under the German Product Liability Act. Nor does it affect liability for the culpable breach of essential obligations, which is then limited to the foreseeable, typical damage.
Mandatory consumer rights remain in place. This text is a plain-language summary and does not replace legal advice. The German wording is the binding one.
Your confirmation stays in this browser and is never sent anywhere.
Notice confirmed. You can read it again here at any time.
In two minutes: what the program is, what it was built for and who it is for.
A Windows program for managing your DayZ servers. Every server, every setting, one window. It runs on your own machine, with no account and no cloud.
Running a DayZ server otherwise means copying folders, hand-editing XML, hunting for keys, writing batch files and getting up at night when the server hangs. DZSS takes exactly those chores off you.
For anyone who wants to run a DayZ server: from a first server of your own to several instances side by side. No prior knowledge of XML or the command line is needed.
That you look after your community instead of your folder structures. Everything a server owner touches daily should sit in one place and be done in seconds.
A full overview of all features is on the home page.
No company, no team, no investor.
I'm a developer myself and I build software for a living. At some point I decided to put that knowledge and experience to work for the DayZ community as well, and build something that genuinely adds value for server owners.In-game name: Vezir Fx, developer from Germany
DZSS stays free, with no paywall and no ads. If you would still like to back the development, you can do so voluntarily.
Report bugs, name your wishes, help others on Discord. That is worth just as much.
More ways to support the project: join the Discord, recommend DZSS and report bugs. If you would like to give money, both ways are above: monthly via Patreon or a one-off card payment via SumUp.
Without them there would be neither test servers nor the time to write this manual.
The German speaking DayZ community gave DZSS room in their forum. Server Studio and Launcher are presented there, and the first feedback from server owners came in there. Thank you for that.
Support pays for development time, not for access: Server Studio and Launcher are and stay free for everyone, without an account and without unlocking. The launcher is open source on top of that.
You need administrator rights and nothing else. .NET does not have to be installed, the package brings it along.
Step 01
Download the package from the home page. A single archive holding everything the target machine needs, including the two Microsoft runtimes the DayZ server requires.
Step 02
Unpack the archive and copy the whole folder onto the machine your servers will run on. That folder is the installer, not the program: you can delete it later.
Step 03
Open PowerShell as administrator, change into the copied folder and run these two lines. The first one is needed because Windows marks downloaded files and PowerShell refuses marked scripts that carry no signature; it applies to this window only and changes nothing permanently. Do not unpack app.zip by hand.
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
.\install-on-server.ps1
The script installs the missing runtimes, puts the program into C:\Program Files\DZSS\, sets up the background service and creates a desktop icon. Another target and further accounts go like this:
.\install-on-server.ps1 -InstallDir "D:\DZSS" -AllowedUsers "SERVER\admin"
Step 04
Start DZSS Server Studio from the desktop icon or the start menu. Do not start it from the unpacked package: there is deliberately no runnable program in there, so that two copies never run side by side and write their logs into the wrong folder.
Step 05
Decide up front where your server data should live: an NTFS partition of its own. Not inside the installation folder, because an update replaces app\ and service\ there completely, and uninstalling deletes the whole folder. A OneDrive folder is unsuitable too, because its synchronisation corrupts saves.
D:\DZSS-Server
What you have now
The program is installed on the machine, the background service starts with Windows from now on, and there is an icon on the desktop. Setup comes next.
A later update takes the same route: close the program, copy the new package, run the installation script again. Your servers keep running meanwhile, they are separate processes. Chapter 11 walks through it step by step.
On the first start the program walks you through this. After that you never have to do it again.
Step 01
DZSS fetches the server files and the mods through your Steam account. For that it has to sign in once.
Connect Steam… at the bottom right of the footer.Connect Steam account window there is a QR code on the left under Via QR code. Open the Steam app on your phone, tap the magnifier and scan it.Or with credentials on the right.If a note next to the account name says DayZ is not part of it, this is the wrong account: without owning DayZ, Steam refuses the download of the server files. A fresh QR code appears by itself, it expires regularly.
Step 02
This is where your servers, mods and backups will live. It is the most important choice in the whole setup.
Initial setup screen is already open. Later you reach it through Data directory… in the toolbar.Browse… to pick a folder on an NTFS drive with enough space, outside the installation folder and outside OneDrive.Network drives, exFAT and ReFS are unsuitable: backups and mod links need NTFS. If DZSS reports too little free space, it names the amount required.
Step 03
These are the actual DayZ server files. They are fetched once and then serve every instance as a template.
Install server files (master).Back to instance list takes you back to the instance list.If the download breaks off, start it again: the parts already fetched are kept. If DZSS additionally asks for a SteamCMD sign-in, that is the built-in fallback route. It is needed once per data directory.
What you have now
Steam is connected, the data directory is set, and the server files sit as a template in serverfiles\. No server ever starts from that folder: each instance gets its own copy when it is prepared. Now you can create your first server.
Sorted by what you want to do. Every guide has the same shape: goal, steps, result, way out.
The template becomes a self-contained instance: its own folder, its own mission, its own ports.
Instances tab click New instance….General tab fill in Name and Map. Under Map you find the maps that are complete: the ones from DayZ and every community map whose mission and required mods are in place. If one you expect is missing, chapter 10 takes it to the end. DZSS allocates the ports by itself. Only if the forwarding in your router is already set do you open Ports and enter Game, Steam query and RCON. Ports already in use and duplicate names are marked red in the dialog straight away, with the reason below.Maximum players and Server password (optional) on the same tab, fixed CPU cores under CPU cores on the Performance tab. The other tabs hold the values of the server configuration, such as time of day, view distances and passwords. For a first server you can leave them as they are; the “Server settings” tab explains what is there.Create. The service checks your input before the window closes; DZSS then prepares the instance for you straight away.Start.
Instances tab: the toolbar at the top with New instance…, Start and Stop, and below it the servers with their state and player count.What you have now
The dot next to the instance turns green and the state changes to Running. Shortly after, the player count and uptime appear. The server is reachable.
If a window titled Cannot start opens, read it to the end: it names the reason and the way out. On a freshly installed machine a Microsoft runtime is almost always missing. If a port is taken, DZSS tells you which instance holds it.
The ports can still be changed later with Edit…, see the “Edit” tab. You adjust the forwarding in your router yourself, though; so if it is already fixed, it is easiest to enter the matching ports right when you create the instance.
Adjust name, ports, player slots, cores or any other server value without creating the instance again. This also works while the server is running.
Instances tab double-click the instance, or select it and click Edit…. The same dialog as for creating opens, here titled Edit instance followed by the instance name.General tab holds Name, Network address, Ports, Maximum players and Server password (optional), the Performance tab the CPU cores. The “Server settings”, “RCON” and “Auto mod updates” tabs explain all other values. Only the map is fixed; for a different map you create a new instance.Apply Changes is not possible right now and which tab to look at. The instance's own ports never count as taken.Apply Changes. DZSS first has the service check the values (Checking the settings with the service…). If it refuses, the window stays open with all your input. If the server is running, DZSS asks first.Applying changes: restart in … s) and the players are warned in game. Skip wait goes ahead at once; if you cancel, the server keeps running unchanged.What you have now
If the instance is stopped, the new values apply from the next start. If the server is running, DZSS applies the cores, the backup settings, the automatic mod update setting and the RCON firewall rule immediately and without a restart. For everything else DZSS first backs up the persistence, shuts the server down cleanly and starts it again with the new values. A new name then shows up in the server list as well.
If you changed ports, players from outside only get in again once the forwarding in your router matches too; DZSS cannot change that for you. DZSS reconciles the firewall rules itself: a rule for a port the instance no longer uses goes away, and players are not disconnected by the change. If an orange band about the firewall rules still appears in the detail area, create them again with Create rules.
Every name exists only once, so that your servers can be told apart in the server list. If two instances from earlier on carry the same name, it stays that way until you change one of them.
Set game time, view, performance and persistence the way you want them, without editing the configuration file by hand.
Instances tab click New instance…, or select an existing instance and click Edit…. Both open the same large window with seven tabs: General, Game, Performance, Persistence, the tab for RCON and the admin password, Updates and Advanced. General holds name, map, network address, ports, player slots and server password; the “Create a server” and “Edit” tabs describe those.serverDZ.cfg. If the line is missing there, the field shows not set (server default), for some values with the server's default in brackets, and a switch shows Not set (server default); the server's built-in value then applies. For numbers the dialog names the allowed range. Use server default takes a value you set out of the file again.Game controls the game itself. Server time is the time of day at startup: SystemTime takes the clock of this machine, otherwise a point in time in the form YYYY/MM/DD/HH/MM applies, for example 2015/4/8/17/23. Time acceleration speeds up game time (0 to 24; at 24 a whole game day passes in one hour), Night acceleration works on top of that during the night only (0.1 to 64). Then come the switches 3rd person perspective, Crosshair, Voice chat (VoN), Debug monitor and Force same game version. They are named for what they do: On allows the third person view even though the line in the file is called disable3rdPerson; DZSS writes the reversal itself. This applies only up to DayZ 1.29. From DayZ 1.30 on, the view is set by the field 3rd person view (1.30) in the same tab instead: 0 turns it off, 1 allows it, 2 allows it in vehicles only.Performance gathers what costs CPU time. At the top are the CPU cores for fixed processor cores. Below that is Limit the server FPS: switched on, DZSS starts the server with -limitFPS and the value you enter, from 10 to 200; this lowers the load of a server with few players. Then come the values from serverDZ.cfg: the login queue (Login queue: concurrent players and Login queue: maximum waiting), Simulated players per frame, Multithreaded replication, the four network ranges from Network range: close (m) to Network range: distant effects (m), the view distances Terrain view distance (m) and Object view distance (m), and the Server FPS warning from 11 upwards. The view distances are upper limits: if a player sets less on their side, their value applies.Persistence shows under Storage folder where the game state lives: in storage_1 inside the instance's mission. You can set Time persistence (the time of day is saved and continues from there at the next start), Save building states (doors etc.) (open doors, for example, stay open) and Storage auto fix (the server replaces damaged persistence files with empty ones at startup). Below are the same backup settings as on the Backups tab; they take effect immediately, without a restart. What they mean is on the “Auto backups” tab.Updates tab you switch on automatic installation of mod updates for this instance and set how long in advance the players are warned. The “Auto mod updates” tab describes how it works.Advanced lists every other value in the instance's serverDZ.cfg, each with Bohemia's explanation where there is one. Use server default marks a value for removal; it only leaves the file when you apply, and until then Undo brings it back. If a value is missing, enter it under Custom serverDZ variable: the name under Key, the value under Value, then Add variable. Numbers as well as true and false stay as they are; text gets its quotes automatically. A list goes in braces and needs a name ending in [], for example motd[] with { "line1", "line2" }.Create or Apply Changes. Before that, DZSS has the service check everything; meanwhile Checking the settings with the service… is shown in the window. It only closes once the service agrees. If it refuses, the window stays open with all your input and names the reason, and next to the buttons it says which tab needs a fix.What you have now
Whatever you change on Game, Performance, Persistence and Advanced, DZSS writes into the instance's serverDZ.cfg, and only the lines that changed. The file stays the source of truth: anything you changed there by hand on another line stays in place, and the next time you open the dialog it shows what is in the file again. The FPS limit is not in the file but in the server's start line. The new values apply from the next start; if the server is running, DZSS restarts it for them, as described on the “Edit” tab.
Values that would break the file are not accepted in the first place: the dialog marks the field and names the rule, such as the allowed range or that text belongs in quotes. If DZSS reports on opening that serverDZ.cfg cannot be read, it was usually damaged by hand: open it through Instance folder, fix it and open the dialog again. If another program holds the file open, an editor for example, DZSS changes nothing; close that program and apply the changes once more.
Some values DZSS sets itself from the instance settings, so they do not appear on Advanced: name, both passwords, player slots, instanceId, Steam query port and mission. instanceId stays 1 for every instance because each one has its own mission; a different value would start with an empty persistence.
Set an RCON password of your own, connect an external RCON tool and log in as admin in game.
Instances tab select the instance, click Edit… and open the fifth tab in the window, the one for RCON and the admin password.RCON password is the BattlEye password for the instance's RCON port. DZSS needs it itself to stop the server cleanly and to send messages, and an external tool needs the same one. 6 to 64 characters without spaces are allowed. Generate next to it creates a random password of 24 letters and digits.Admin password is the password that ends up as passwordAdmin in serverDZ.cfg. In game it makes you server admin: type #login, a space and the password in the chat. Again 6 to 64 characters apply, no spaces and no quotes; Generate helps here too.Allow RCON from other computers. The RCON password then needs at least 12 characters. DZSS adds a Windows firewall rule for the RCON port for this, together with the instance's other firewall rules; switch it off again and the rule goes away.Apply Changes. DZSS applies the switch immediately, even with the server running and without a restart. A new password, on the other hand, only takes effect after a restart; if the server is running, DZSS restarts it for that, with a warning to the players.General tab under Ports, next to RCON.What you have now
BattlEye listens where the server listens: on the network address you chose for the instance or, if none is chosen, on all addresses of this machine. DZSS no longer writes an RConIP line into BEServer_x64.cfg. Even so, a tool from outside only gets in once the switch has created the firewall rule.
If the tool does not get through, check in this order: is the switch on, and does the instance's detail area show no orange band about the firewall rules? If rules are missing, Create rules creates them, the RCON rule included. If the tool sits outside your network, the RCON port has to be forwarded in your router just like the other two ports; RCON runs over UDP. If the dialog refuses a password, it names the rule below it. After restoring a backup DZSS may report that a password from the backup does not meet today's rules; the instance then keeps its own, and you set a new one here if needed.
Since version 0.1.16 RCON listens on all addresses for an instance without a fixed network address; before, only on 127.0.0.1. As long as the Windows firewall is on, that changes nothing, because only the switch opens the port. If the firewall is off, DZSS reports it with an orange band, and then no rule holds RCON back: if the machine has a public address or the port is forwarded, RCON can be reached from outside even without the switch. In that case set a long RCON password, most easily with Generate.
Get Workshop mods onto your server without players failing on a missing key.
Mods tab enter the Workshop address in the field at the top and click Add. A link can also be dragged in.→ Assign.Up and Down. Frameworks such as @CF belong at the top.Apply mods, then stop and start the server on the Instances tab.What you have now
DZSS copies the mods into the instance, puts the keys in the right place and writes the load order. Until the restart a brown band points out that the change has not taken effect yet.
If players are rejected, a key or a dependency is almost always missing. Repair puts a single mod right again, Reapply from pool plays all assigned mods in once more. Careful: the latter overwrites mod files you changed inside the instance. A large download does not need you: if the connection drops, DZSS carries on more slowly and retries after short pauses, and a cancelled download does not start over from zero but fetches only the rest. If a Steam sign-in is missing, the tab offers it to you right there.
Adjust amounts, locations and rarity without the next DayZ update overwriting your work.
Economy tab pick the instance and create a layer of your own with Create. Your changes land there and not in the original files.Filter classname… and edit the values on the right, for instance Nominal, Min or Lifetime.Bulk on filter.Apply (write override) and restart the server.What you have now
Your changes sit in a layer of their own above the original files. The vanilla files stay untouched, a DayZ patch never touches your work.
Watch the Issues column and clear any complaints before writing. Whether the server accepted the change is shown by CE errors from log: clicking a message jumps to the type concerned.
See where something appears and move it with the mouse instead of typing coordinates.
Map tab pick the instance and click Generate map. This happens once per world and is cached afterwards. Community maps are included, not just the ones from Bohemia. For Sakhal and Nasdara DZSS puts the tiles together the way Bohemia arranges them; a Sakhal map from a version before 0.1.17 is redrawn once at the next click on Generate map.Events and Player spawns at the bottom.Add position (click on map), delete with the Del key.Apply now (soft reset). A full Wipe is not needed for this.What you have now
The points live in this instance's mission. Since every instance has its own mission, you can run two servers on the same map quite differently. A backup is taken before anything is reset.
If the map stays empty, read the status line or the Cannot generate the map window: the reason and the way out are in there. Sakhal and Nasdara get no terrain from the server; DZSS then reads it from the DayZ installation on this machine. If DayZ is not installed there, on a rented server for example, the window names the missing file, for Nasdara worlds_nasdara_data.pbo. Copy it from the Addons folder of the DayZ installation on a PC that has DayZ into the folder the window gives (mapsources in the data directory) and click Generate map again. The server itself runs without the map image as well. If the display component fails once, the tab does not stay dead until you restart the program: the error is reported, and the next switch to the tab tries again.
Hold on to a state you can go back to when a change goes wrong.
Backups tab pick the instance.Back up persistence saves only the game state and works on a running server too.Back up complete instance saves the whole folder. The instance has to be stopped for that.Restore…. As a safeguard you have to type the name of the instance.What you have now
The backup appears in the list. Before every restore DZSS additionally writes a safety copy of the current state, so the way back stays open as well. If you restore a complete backup, DZSS also switches off the automatic mod update of the instance, so the restored mod versions stay.
If the action is refused, the instance is usually still running. Stop it and try again. The same holds the other way round: while a backup, an update or a scheduled restart is running, DZSS refuses a stop as well and names the operation you have to wait for. Deleting an instance likewise waits until a running backup has finished. Backups survive even deleting the instance, by the way. From a complete backup, Recreate instance… builds the instance again. If another instance carries the same name by now, the recreated one gets the suffix (restored).
DZSS also backs up the persistence without you doing anything: by default before every start and after every stop, provided it changed since the last backup, and on request while running as well; how to set that up is on the “Auto backups” tab. You can tell these backups by their note: Before start, After stop, Scheduled restart or Scheduled backup. The suffix (forced, last world save missing) means the server had to be killed; whatever happened since the world was last saved is not in it. These automatic persistence backups and those made with Back up persistence are cleared away together: the ten newest always stay, older ones only for as many days as set under Keep for. If that is 0, the oldest gives way to the newest, so if you start and stop often, your own backups are pushed out sooner.
Decide when DZSS backs up on its own and how long it keeps the backups, also while the server is running and full.
Backups tab pick the instance. The settings are in the Automatic backups section; you find the same ones in the instance dialog on the Persistence tab.Back up on start and stop backs up the persistence right before the start and right after the stop, provided it changed since the newest backup.Back up while running backs up the running server at a fixed interval. After every enter the minutes, from 60 to 10080, so at most one week. It counts from the newest backup of any kind, and if nothing changed, DZSS writes nothing.Keep for enter how many days backups should stay, from 0 to 365. The ten newest always stay, whatever their age; with 0 days exactly those ten stay. Below, DZSS estimates roughly how many backups that makes at this interval and how much space they need, measured by the newest one.Save. The settings apply immediately, even with the server running and without a restart.What you have now
Backups taken while running carry the note Scheduled backup. DZSS backs up a copy it checks file by file: so even a full server that writes all the time gets an intact backup instead of a half written one. Backups made before a reset, a restore or a DayZ update are never cleared away; of those taken before an automatic mod update, the three newest are kept.
If a backup while running does not appear, there is usually a reason: nothing changed, a scheduled restart is due or has just run and backs up anyway, or the server wrote to the same files every time DZSS copied them. DZSS then discards the unsafe copy, tries again later and notes it in the service log. If Save does not accept the values, one of the two fields is usually outside its limits or empty.
After the update to 0.1.16, existing instances keep their previous behaviour: backup on start and stop on, while running off, 0 days, so as before the ten newest stay. Newly created instances also back up while running, every hour, and keep 14 days. If you switch on the interval for an existing instance, the estimate shows you before saving roughly how many backups that makes.
The server should keep running and speak up even when you are not sitting in front of it.
Restart schedules: pick a Preset… or enter an expression of your own, then Add. Warnings go out to the players automatically 15, 10, 5 and 1 minute before.Scheduled messages. For a single announcement tick one-off and enter a point in time.Broadcast message to all players… plus Send reaches your players right away. The player list offers Kick and Ban.What you have now
Before every scheduled restart a backup is written, then the server is shut down cleanly and started again. Messages only go out once the server can actually accept them. If an automatic mod update is pending, DZSS installs it with this restart.
If the player list is still empty after a start, that is normal: it appears as soon as BattlEye accepts the connection. Use plain characters only in messages to players, otherwise they arrive garbled in the in-game chat.
Bring a new DayZ server build to every instance without anyone being thrown out in the middle of a game.
Steam has a newer server build. appears above the instance list. DZSS asks Steam when it opens, every 30 minutes after that as long as the interface is running, and also right away when you change the data directory or sign in to Steam.Update server files in the band and confirm the question.Server update finished sums up what became of each instance.What you have now
Every instance runs the new build. What was running before is running again; what was stopped is updated as well and stays stopped. Before DZSS touches an instance, it writes a complete backup; on the Backups tab it carries the note State before the DayZ server update.
If a server cannot be shut down cleanly and has to be killed, DZSS does not bring it to the new build but starts it again on the old one; the window at the end names it. If an instance is busy with something else, such as a backup, DZSS skips it and names it as well. Such an instance then shows a band in the detail area that begins with Server files were updated: stop it and click Prepare again there. For the download DZSS needs a Steam sign-in with an account that owns DayZ.
DZSS does not install a DayZ update on its own. It reports the update, and you choose the moment with the click. Do not wait long: anyone whose game is already updated cannot join your server until then.
DayZ 1.30 adds the map Nasdara to the server files. It only becomes available after this update, then on the Worlds tab and under Map when you create an instance. Every instance grows with it, by about 1.3 GB with 1.30: like the sakhal\ folder, DZSS mirrors nasdara\ into every instance, whatever map it runs. Plan for the space before the update.
Bring a mod that got a new version in the Workshop onto your server. Steam downloads the new version for your players on its own; while your server still runs the old one, they usually cannot join any more.
Check for updates on the Mods tab. DZSS asks the Workshop about every mod in the pool. A mod with a new version then carries a ⚠ in the pool; select it, and the right side says An update is available in the Workshop. Only changed content counts as a new version: if the author only changes the description or the picture, the mod gets no ⚠.Download again on the right. The new version goes into the pool. Your servers keep running meanwhile, because every instance runs its own copy.Instances tab, send an announcement through Broadcast message to all players… and Send, using plain characters only, and wait a few minutes. Then click Stop.Mods tab the assignment is now headed Assignment for: with the name of this instance. Click Reapply from pool and confirm. The instance gets the new version along with its key.Start on the Instances tab again. If several instances use the same mod, repeat steps 3 to 5 for each; the download happens only once.What you have now
The instance runs the new version, the ⚠ next to the mod is gone, and players with the current version can join again.
Reapply from pool refuses while the server is running; stop it first. The button overwrites mod files you changed inside the instance; mod folders that DZSS did not create are left alone. Apply mods is not enough for an update: it only adds missing mods and leaves existing copies as they are. If DZSS is still downloading the mod, it does not copy a half downloaded version into the instance; it refuses and names the mod. Try again once the download has finished.
DZSS installs a mod update by itself only for instances for which you have switched on automatic mod updates; the “Auto mod updates” tab describes this. For all others DZSS asks the Workshop only when you click Check for updates. Check there regularly, and at the latest when players report that they cannot join any more.
An instance should pick up new versions of its Workshop mods by itself, so your players can join again after a mod update, even when nobody is watching the server.
Instances tab select the instance, click Edit… and open the Updates tab in the window. When you create a new instance, the same tab is in the window that New instance… opens.Workshop mods switch on Install mod updates automatically.Warn the players enter how many seconds before the restart (seconds before the restart) DZSS warns the players in game, from 0 to 900. The default is 180 seconds, that is three minutes. If nobody is online, DZSS does not wait.Apply Changes, or Create for a new instance. The setting takes effect immediately, even while the server is running and without a restart.What you have now
From now on the background service watches the mods of this instance, even when the interface is closed. When an author uploads a new version, DZSS waits until ten minutes have passed without another upload. Then it downloads the new version into the pool while the server keeps running, warns the players, stops the server, takes a complete backup, installs the update and starts the server again. The backup then shows up on the Backups tab as before mod update. If the instance is stopped, DZSS installs the update and the instance stays stopped. If a scheduled restart is due within the next 15 minutes anyway, the update is installed with that restart, and the server restarts only once.
If the note turns orange, DZSS needs you. If DZSS is signed out of Steam, it cannot download the update. Sign in again; the Mods tab offers the sign-in right there. If the new version requires a mod the instance does not have, DZSS does not install the update, and the server keeps the old version. Assign the missing mod on the Mods tab and prepare the instance again. If installing fails, DZSS starts the server again with the old version. If the mod cannot be copied into the instance, for example because its folder there was not created by DZSS or a file in it is locked, the note gives the reason, and DZSS tries again once the mod changes again. If the server does not come back up after the update, the note says so as well; the complete backup DZSS took beforehand is on the Backups tab as before mod update. If only a download fails, DZSS tries again by itself after a pause.
After the update to 0.1.18 the automatic mod update is switched off for every instance, existing ones included. Before every update it installs, DZSS takes a complete backup of the instance. The first one can be as large as the instance itself; every further one shares unchanged files with the previous one, and the three newest are kept. If you restore a complete backup, DZSS switches off the automatic mod update of this instance, so the restored mod versions stay. If you restored because of a faulty mod update, switch it on again once a fixed version is out.
Follow the chat, answer players directly and see where someone is, without launching DayZ yourself.
Mods tab click Activate on the DZSSLink tile at the bottom.DZSSLink tab you follow the chat. The recipient field lets you write to everyone or to a single player.Map tab, Show players shows the player positions.What you have now
DZSS packs the server mod itself and puts it into the instance. Your players install nothing for it, download nothing and need no key. Your server stays in the ordinary server list instead of the modded filter.
If the tab reports that the installed copy comes from another DZSS version, click Deactivate once and then Activate again. That delivers the server mod anew. Writing to a single player only works with DZSSLink, RCON alone cannot do it.
The interface tells you at any moment how your servers are doing. You only have to know where to look.
Running, orange for Starting, Stopping and Unresponsive, red for Crashed and grey for Stopped.⚠ not prepared, the instance has to be prepared first. It will not start otherwise.Service connected with a green dot is the normal case.What you have now
If no band is shown, nothing is open. DZSS deliberately shows no green all-clear for things it has not really checked.
If a message carries an identifier in the form ERR-1A2B3C, the same identifier sits in the log next to the full cause. Note it down when you ask for help.
Read what the DayZ server wrote during a particular run, for example after a crash.
Instances tab select the instance and click Server logs. Not to be confused with Logs in the footer at the bottom: that one belongs to DZSS itself.profiles folder until the next start. Instance folder gets you there: it opens the instance's folder with server files, mission, mods, keys and config.What you have now
Every start tidies up: the logs of the previous run move into a folder of their own under logs, and DZSS removes runs older than 30 days. That way profiles does not grow without end, and you find a particular run by its date and time.
If DZSS reports No server logs yet, the instance has never been started; logs only appear with the first start. If another program, an editor for instance, holds a log file open at start, it stays where it is and moves along with the next start.
If loose logs from earlier still lie in profiles, DZSS files them away once at the next start of each instance: one folder per run, and runs older than 30 days are removed right away. The first time that looks like a lot of movement, and it is meant to.
Banov, DeerIsle, Antoria: DZSS runs maps that do not come from Bohemia. Three things have to come together for that, and this chapter walks through them once.
Step 01
The maps DayZ ships with are known to DZSS already: Chernarus, Livonia, Sakhal and, since DayZ 1.30, Nasdara from the Badlands DLC. Which community maps join them is set out in the world list. DZSS ships that list with it and fetches the current one at the press of a button.
Worlds tab. Antoria, Banov and DeerIsle are already there: the list comes with DZSS and applies even on a machine without internet access.Check for updates. DZSS fetches the current list from dzss.eu and files it away; maps added since then appear afterwards.Update server files as described in chapter 9 under "DayZ update", and click Refresh here afterwards.If the button reports an error, DZSS cannot reach the network; a firewall or a proxy is usually in the way. Nothing is lost: the list that came with DZSS still applies, and the button can be pressed again at any time. If a hand-written worlds\catalog.json from an older version is still in your data directory, the tab says so. It is no longer read and not touched either; you can leave it or delete it.
Step 02
A map has two parts: the mission, which only ever sits on the server, and the mod, which players download too. This step covers the first part.
Worlds tab and click Install.Install mission from file….Missions belong to their authors. DZSS does not redistribute them, it only names the address; if there is nothing to download there, your installation is not at fault. If a mission does not match the map it is meant for, DZSS stops and names both. Without that check one mission would overwrite the other, and you would only notice at the next server start.
Step 03
Every community map is a workshop mod, and some need further ones. Only once everything is together can the map be picked.
Worlds tab names the mods each map needs, in the right load order. Missing ones are highlighted.Mods tab. Keep the order from the world list exactly as it is.Map in the New instance… dialog. From here it is the usual route: create, prepare, start.If the map is not offered, something is still missing: either the mission or a required mod. That is deliberate. An instance without its map mod starts perfectly happily and still turns every player away, because the matching key is absent. Nothing looks red in DZSS, and in the game it looks like a broken server.
What you have now
The map is in the list, the mission sits with your server files, and the required mods are assigned. A server on this map behaves like any other from now on: backups, economy, spawn points and monitoring all apply unchanged.
When the author releases a new version of the mission, the same button is all it takes. DZSS asks for the mission details only when you press it, never on a timer and never in the background.
An update replaces the program, not your servers. Those keep running, and nobody is dropped from the game.
app\ and service\ in the installation folder are replaced. Your data directory with instances, mods and backups lives elsewhere and is not touched.Step 01
The installed version stands in the footer at the bottom left, for example Service connected (v0.1.x). The current number is on the home page, and below it, under "What changed", what it brings along.
If dzss.eu lists a newer version, the footer shows the Update available notice next to it by itself; a click opens the download page. The check runs once per program start, silently and without telemetry. The gear at the top right opens the settings with the details of the installed version.
Step 02
Same as the first time: download the archive, unpack it, copy the whole folder onto the machine. Keep the package folder of the version you were running so far; it is your way back.
Step 03
Close DZSS Server Studio. Do not stop your servers, they run right through it. If the interface is still open, the script stops before it touches anything and names the folder it was started from.
Step 04
Open PowerShell as administrator, change into the copied folder and run the same two lines as during the installation. The script stops the background service, replaces app\ and service\ completely and starts it again. That your DayZ servers keep running meanwhile, it tells you outright.
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
.\install-on-server.ps1
If you gave a target of your own or further accounts at installation time, the same details belong here again:
.\install-on-server.ps1 -InstallDir "D:\DZSS" -AllowedUsers "SERVER\admin"
Without -InstallDir the script puts the new version into C:\Program Files\DZSS\ and points the service at it, while the previous installation folder stays behind unused. Without -AllowedUsers only the account doing the installation is left, and the others can no longer reach the service.
Step 05
Start the interface from the desktop icon. The footer now carries the new number, and your servers stand unchanged at Running, with their uptime carrying on.
What you have now
The program is new, everything else stands as before: instances, mods, backups, schedules and the Steam login. No server was stopped for it, so no player noticed a thing.
If the service does not come up after the update, the script says so and names the log folder. The way back is the same way: run the installation script from the older package folder once more. Your server data stays untouched by all of it, as it lives outside the installation folder.
Not to be confused: this replaces DZSS. When DayZ gets a newer server build, the program reports that itself with a band above the instance list, and Update server files pulls it in. Running instances are announced, shut down cleanly and started again there, because the server files themselves change. Step by step this is in chapter 9 under "DayZ update", and right next to it, under "Mod updates", the way for mods.
None of it is compulsory. All of it has proven itself in practice.
DZSS backs up by itself: by default when starting, stopping and restarting, on request while running as well, and before every restore. These backups rotate, though, and their note only says when they were made. Before larger rebuilds a deliberate backup of your own is therefore worth it, with a note that says why.
Three changes at once and the server no longer starts: then you do not know which one did it. Change, start, take a quick look, carry on.
Do not test new things first on the server where fifty people are playing right now. A second instance for trying things out is created in a minute.
The messages nearly always name the reason and the way out. If a message is too long for the status line, DZSS shows it as a window as well.
Bugs get fixed, and a fix only helps the person who has it. How you put a new version in place is in chapter 11.
Otherwise your instance keeps running the older build and rejects updated players. DZSS shows you with a band which instance is affected. The button in the band above the instance list does that for all instances at once.
The data directory belongs on an NTFS partition of its own, not in the installation folder and not in a cloud folder. That way your servers survive every update unharmed.
The cases that come up most often. Pick the one that applies to you.
Start it from the desktop icon, not from the unpacked package. If it still does not come up, run the diagnostics report in the installation folder as administrator. It lands in the log folder and says what is missing.
.\collect-diagnostics.ps1
On a freshly installed machine one of the two Microsoft runtimes is almost always missing. The DayZ server then quits at once and writes no log at all. DZSS checks this before every start and names exactly the missing package and where to get it; the installation script brings both along. If it starts and only dies afterwards, the reason is usually in that run's RPT; Server logs on the Instances tab takes you there.
Look for an orange band in the detail area of the instance and create the rules with Create rules. If a blocking rule stands in your way, DZSS names it: a block beats every allow rule, so the server runs and still nobody gets in. Beyond that, people from outside only get in if the ports are forwarded in your router. That stays your job.
Three causes cover nearly every case: a missing mod key, a mod that is newer in the Workshop than on your server, or a DayZ update after which the instance has not been prepared again. Use the repair and Check for updates on the Mods tab, and stop the instance for Prepare again. How to install either update, and how to let mod updates install themselves, is in chapter 9.
Open the instance with Edit…, switch to the tab for RCON and the admin password and switch on Allow RCON from other computers; the RCON password then needs at least 12 characters. If the tool sits outside your network, the RCON port has to be forwarded in your router like the other two ports. Up to version 0.1.15 DZSS also wrote an RConIP line into the BattlEye configuration that external tools failed on; from 0.1.16 on it no longer writes it. Chapter 9 has the steps on the “RCON” tab.
Undo the last change rather than adding more. If that does not help, stop the instance and restore the state from before the change on the Backups tab. The current state is backed up automatically as part of that.
Read the status line on the map tab first, it names the reason. Sakhal and Nasdara take their terrain from a DayZ installation, because the server ships none for these worlds; if there is none, the window names the file and the folder for it. More on this in chapter 9 under "Map". If the whole tab stays empty while everything else works, the Microsoft display component is missing, which Windows Server does not include. Every other tab then carries on normally. If the component fails just once, switching to another tab and back is enough; you do not have to restart the program for that.
Download the latest version and restart the machine once. Make sure Windows 10 or 11 is fully updated. If that does not help, open a ticket on Discord; describe what happens at startup and what does not.
Open a ticket on Discord and bring the log folder along: the Logs button at the bottom of the footer writes a fresh diagnostics report into it and then opens the folder. No passwords are in there. With that folder and the error identifier, one answer usually settles what went wrong.
Questions, bugs and wishes all come together on Discord, each request as its own ticket. That is where I answer fastest.
The official place to go for support, bugs and wishes. Every request gets its own ticket so nothing gets lost.
The Logs button in the footer writes a diagnostics report and then opens the folder. Name the identifier from the error message as well.
Join the server and open the category of the program in question: DZSS Server Studio or DZSS Launcher. Both have the same channels. For help with setup and operation go to support-setup-help and open your ticket there. A bug belongs in bugs-issues, a wish in feature-requests, a special request in custom-requests.
This manual too grows on what gets reported. Is a chapter missing, a step unclear, or does something no longer match the program? Say so on Discord.
Legal matters have pages of their own: legal notice and privacy.
A separate program for DayZ players: open source, free for everyone and independent of the Server Studio.
The DZSS Launcher is a dedicated server browser for DayZ players: search and filter servers, see ping and player counts live, keep favourites and join directly.
It is being built alongside the Studio as a separate project, and it is open source: the source code is public, anyone may read it, audit it and contribute. News about it lands in the Steam group.
For context: the DZSS Launcher is a program of its own and not part of server management. You do not need it to run your servers.
The download is free and open to everyone: no account, no unlocking, no supporter tier.
Windows 10 or 11, .NET is included. Version, size and checksum are on the launcher page; announcements about new builds go out through the Steam group.
Two steps, no installation in the usual sense. You do not need administrator rights for this.
Step 01
Unpack the downloaded ZIP file into a folder of your choice. A folder of its own is better than the downloads folder, because the launcher stays where you put it.
Step 02
On first start the launcher asks whether it should set itself up. Say yes and you get a shortcut on the desktop, Windows search finds it, and you can remove it again from Windows Settings under Apps. No administrator rights, no PowerShell.
On the very first start Windows shows a warning: “Windows protected your PC”. That is because the launcher is not signed yet. Click More info and then Run anyway. If you unblock the ZIP file before unpacking it (right-click, Properties, tick Unblock), you never see the warning at all.
A profile is your in-game name plus a DayZ folder of its own: its own key bindings, its own graphics and sound settings, its own mod configurations. You create, switch and delete profiles in the settings under Profile.
Which profile applies on which server is set on the server itself. It is meant for servers that require a particular name or keep a whitelist by name. If you pick nothing, DayZ starts exactly as it would start without the launcher.
The settings show the Steam account you are signed in with, including a copyable ID; you need that for unlocks and whitelists. Below it are your characters: one per server, with play time, distance travelled, infected killed and the name you last played under there.
The launcher reads both from your own drive: no sign-in, no request over the network. Server passwords sit in the same DayZ file; they are not read, not stored and not displayed.
If Discord is running on the same machine, the launcher tells it that it is running: “DZSS Launcher” then shows up next to your name, with its icon. You can switch this on and off in the settings under Discord status; it is on by default.
Only the name and icon of the launcher are passed on: no server, no address, nothing about you. The launcher opens no connection to the outside for this, it talks to the Discord on your machine through a local interface; Discord is what spreads the status afterwards. The one connection the launcher opens itself remains the question whether a newer build exists.
Next to ping and player count stands the time on the server, so you can see before joining whether it is night there. The ring beside it stands for one full in-game day: the dark part is night, drawn as wide as it actually lasts. On most servers night runs several times faster than day; on others it drags on for hours.
Before Steam overwrites a mod, the launcher sets the old version aside, and it does so for every mod you have. If a server stays on an older version of a mod, you can start it with the version that was kept. The choice applies to that one server only; every other server stays on the current version, and one click on use current again undoes it. You can look through the kept versions and delete them one at a time.
The column heading PLAYED sits next to PING and PLAYERS and works the same way: one click and the list follows it. In the Favourites tab that is the default, so the server you played on most recently sits at the top; servers you have never played on come below, ordered by ping. Ping still orders the main server list.
Minimise the launcher and it goes quiet: while nobody is looking, it stops querying servers. Your Discord status stays on, and the protection for your mod versions keeps running.
An install.ps1 still ships with the archive. You only need it if the launcher should live under Program Files for all users of the machine; that does require administrator rights. For the normal route above it is unnecessary.