Server operations
Each Nitrado service gets an isolated workspace for settings, diagnostics, tools, map operations, events, missions, deployments, notifications, and audit history.
DZManager connects Discord administration, Nitrado server control, security, events, missions, mapping, claims, and staff workflows. The fast jobs stay in Discord. The complicated jobs get a real operations interface.
Deploy, inspect, and recover server changes from one workspace.
DZManager is built around the jobs staff actually repeat: checking health, changing settings, deploying tools, running events, reviewing security, and knowing exactly what changed.
Each Nitrado service gets an isolated workspace for settings, diagnostics, tools, map operations, events, missions, deployments, notifications, and audit history.
Monitor fresh-spawn protection, desktop clients, exploit signals, runtime watchers, configuration validity, and log availability without mixing monitoring with destructive actions.
Work with high-resolution DayZ maps, live overlays, saved coordinates, radius zones, and managed server tools from the same selected-service context.
Build reusable presets, deploy temporary files, handle restart-based activation, send announcements, and restore the exact previous server state afterward.
Claim systems, suggestions, staff tasks, delegated access, public pages, and Discord commands stay attached to the same community instead of separate utilities.
The interface keeps status, actions, history, and permissions obvious so staff can move quickly without guessing what a button will touch.
Every connected Nitrado service keeps its settings, tools, security, events, deployments, and audit state separate.
Owners can delegate viewer, moderator, editor, server-admin, or Event Coordinator access without opening the whole dashboard.
Important operations retain actor, status, validation, restart requirement, and history instead of disappearing after the click.
Slash commands stay useful for fast actions while the website handles deeper operational workflows.
Flags, raincoats, armbands, suggestions, and player-facing pages stay synchronized from the same data.
Configuration dependencies, restart lifecycles, map coordinates, ADM/RPT logs, and Nitrado file operations are first-class concerns.
DZManager does not force every workflow into one surface. Staff can use Discord for quick commands and open the operations workspace when they need diagnostics, configuration, mapping, lifecycle controls, or history.
Connect the Discord community and keep identity, roles, claims, and staff operations in the same boundary.
Save a Long-life token and let each DayZ service become its own isolated operations workspace.
Use one interface for health, settings, tools, security, events, missions, map operations, and audited changes.
The platform is structured around server workspaces and map-aware systems so new DayZ content can slot into the same operations model.
Discord for fast staff actions. A dedicated web workspace for the server work that deserves context, validation, and history.