DayZ players are kicked or the server is missing from the launcher

Most DayZ tickets are one of these five. Work down the list.

1. Signature or mod kicks

• Every mod's .bikey file must be in the keys folder in the server root. One missing key kicks everyone using that mod.
• The server and the players must run the same mod versions. After a workshop update, update the server files.
• Let the DayZ Launcher load the mod set from the server rather than picking mods by hand.

2. Wrong build

With forceSameBuild = 1; in serverDZ.cfg, a client on a different game version is refused. That is the correct setting. Restart the server after a game update so it takes the same version as your players.

3. The server is not in the launcher list

• Add it by address in the launcher's server tab, using the query port rather than the game port.
• Give a newly started server a few minutes before expecting it in the list.
• Check the console for errors during boot. A server that failed to load its mission never registers.

4. There is no loot in the world

• This is nearly always a broken economy file. Read the console during boot for XML errors.
• A mod's types file that is registered but missing, or an unclosed tag in types.xml, empties the whole economy.
• Restore the mission folder from a backup and reapply your changes one file at a time.

5. The world reset itself

The storage folder is tied to instanceId in serverDZ.cfg and to the mission name. If either changed, the server started a fresh world and the old storage is still on disk. Put the values back and restart.

6. Config changes are ignored

Stop the server before editing. Read the first lines of the console after a start, since a missing semicolon in serverDZ.cfg makes the server fall back to defaults.

Open a ticket from Support in the Client Area with the console output and the exact kick message if none of this fits.