Foreword

Since I was honestly unsure about my first setup of a DayZ server, I documented all my steps in Notepad++. Over time these notes grew in size and I began to organize them and created this github wiki. Eventually I thought at some point that this information and experience might be of interest to others. Hence this BLOG with clever tips and hopefully useful assistance.

A basic recommendation, especially if you are not experienced with XML and JSON: Make sure you have modified XML or JSON files checked before they are saved (on the server) using the appropriate test websites (see chapter "tools"). I really often crashed one of my servers (among other things because Nitrado updated from 1.14 to 1.15 without prior notice, which led to a server wipe...) because I had installed faulty XML and JSON files. You don't really have to understand anything about XML and JSON, just follow the rules! With the release of 1.16 to the current 1.19, everything went flawlessly so far.

My appeal to you: document what you do – similar to my document here. This makes it easier for you to understand errors - but above all it makes it easier for you to set a server up again from scratch (e.g. the winter mods according to the season).

Always do one step at a time. This is the only way to understand what may have gone wrong - and can be reversed. One mod after the other - it's annoying, but this is the only way to identify sources of error. Sometimes it also makes sense to change the order in which individual workshops are loaded.

For each workshop that is to run on the server, the corresponding mod must be loaded (Nitrado: "Basic settings") - that should be clear. Also that this mod (workshop) has to be installed on the server, but also has to be provided by the client (DZSALauncher does this independently, the player has to do it via the Steam "Launcher").

If the client reports that a PBO is missing (and the server specifies the mods), closing (from the system tray!) and restarting Steam usually helps. In most cases this message is telling that the versions of the specific mod is different between server and client. Give the server owner a hint - he/she might not have recognized in time a version update on that workshop/mod.

An important note on Livonia/Enoch tier levels: Unlike Chernarus, Livonia/Enoch only has three (3) tier levels (as of v1.19: a fourth one was added, called "Unique"). Therefore, all entries for Tier4 in the types.xml file must either be deleted or, if there is no other tier level in the corresponding configuration, changed to Tier3. (). Mixed tier tiers (Tier234, etc.) have been introduced for Namalsk. This always causes problems for me, which is why I replaced this mixed tier again (Tier234 => Tier2, Tier3, Tier4).