Overview

Connecting
DAYZ SERVER -

-

PID
-
UPTIME
-
MEMORY
-
RPT SESSION
-
READY MARKER -

Controls

Stop sends the server window a close request (the engine's own shutdown). Nothing is ever killed.

Server config

serverDZ.cfg
Loading serverDZ.cfg…

Saving never restarts the server. A backup of the current file is made before every save and restore.

LAST SAVE

No saves recorded yet.

BACKUPS
  1. No backups yet.

Launch list

-
  1. Loading the mod list…
COMMAND LINE WITH THIS LIST -
Loading…

Mods must already be copied into the server folder. The list can only change while the server is stopped; it is used at the next start, and nothing restarts on its own.

REMOVE FROM LAUNCH only takes a mod out of this list: its folder, keys and update record stay in the server folder. To take a Workshop mod's files out of the server folder, use UNINSTALL… under Workshop updates (recoverable). Warning: without a mod, DayZ may drop the persistent objects that depend on it (items, bases, vehicles in the mission storage) at the next start. Back up the mission storage first.

LAST CHANGE

No changes recorded yet.

Add mods from the Workshop

-

SteamCMD downloads the item into its own staging folder; that may run while the server runs. QUEUE INSTALL changes nothing live: the mod is installed, its keys copied and the mod list extended only at the next scheduled restart or RESTART & APPLY QUEUED (see Workshop updates below). INSTALL NOW copies it immediately, only while the server is stopped, and does not touch the mod list. Workshop dependencies are not installed automatically.

LAST WORKSHOP ACTION

Nothing downloaded or installed yet.

    Scheduled restarts

    NEXT -

    The only time the dashboard restarts the server on its own. At each time it stops the server, applies the Workshop updates you queued and starts it again. Missed times are not caught up.

    Loading…

    LAST CHANGE

    No changes recorded yet.

    Workshop updates

    -

    Installed Workshop mods are checked on their own. An update that is found is only downloaded into SteamCMD's staging folder and checked; nothing in the server folder changes until you queue it for the next scheduled restart or apply it now. Each mod is queued and applied on its own.

    Last checked: -
    NEW MODS QUEUED FOR INSTALLATION
    1. None queued. Download a new mod, then QUEUE INSTALL.

    A queued new mod is installed at the next scheduled restart or with RESTART & APPLY QUEUED, together with the queued updates, and added to the end of the mod list on the side you chose. Until then no folder, key or mod list entry changes. If anything fails, the whole batch is put back. If putting back also fails, Start is refused until you clear the blocker. Starting DayZ outside this dashboard does not apply the queue.

    INSTALLED MODS
    1. Loading…

    Applying replaces the mod folder with the checked download; the old folder is kept as @Name.previous until a start is verified. Apply now is one mod; the queued set at a restart is applied together and fully put back if any mod fails. The mod list is not changed. Workshop dependencies are not detected: update each mod you need yourself.

    LAST UPDATE ACTION

    No update actions yet.

    QUARANTINE · UNINSTALLED MODS

    -
    1. Loading…

    UNINSTALL… moves a Workshop mod's folder (and its @Name.previous, when that names the same Workshop item) into .hf-quarantine in the server folder and removes its update record. It is refused while DayZ runs and while the mod is in the saved mod list. Nothing is deleted: keys, profiles, mission storage and SteamCMD's download are never touched. RESTORE moves it back when its place is free; it is not added to the mod list. There is no permanent delete in this version.

    DayZ server files

    -

    The DayZ dedicated server itself (Steam app 223350), kept apart from Workshop mods. CHECK UPDATE asks SteamCMD which build the public branch has; DOWNLOAD UPDATE puts it in a separate staging folder; nothing in the server folder changes until you INSTALL it with DayZ stopped. Nothing here stops, starts or restarts the server, and Workshop mods are never updated with it.

    SERVER FILE BACKUPS

    1. Loading…

    An install writes only files from the staged build, only where their content differs, and never serverDZ.cfg or other root configuration, mpmissions (including every storage_*), profiles, keys, battleye, mods or the dashboard's own folders. Each replaced file is first moved into .hf-server-backups in the server folder, and any failure puts everything back. Nothing is deleted. RESTORE undoes an install while the files it wrote are unchanged.

    LAST SERVER FILES ACTION

    No server files actions yet.

    Activity

    1. No actions recorded yet.

    Uninstall mod

    WARNINGS
      KEYS · ALL KEPT
        Files that would be moved to the quarantine

          Install DayZ server update

          WARNINGS
            Files that may be written
              Protected, never written
                Not in the staged build, left in place

                  CONFIRM