World War Z operations network

Survive The World.
Control The Network.

One connected operations platform for the World War Z PlayStation DayZ community — live server intelligence, survivor systems, economy, shop delivery, moderation and administration across Primary World and Livonia.

PlatformPlayStation 4 & 5
MapsPrimary + Livonia
Capacity26 survivors
CommunityWorld War Z

One connected control centre

Made For More Than
Basic Bot Commands

World War Z Bot is being built specifically around the needs of our DayZ console community—from everyday player features to serious administration and server configuration tools.

Its purpose is simple: reduce repetitive Admin work, give players useful self-service features and keep important server systems organised.

Core systems

Built Around The Whole Community

Each system is designed to work together, giving players a smoother experience and Admins a clearer view of the server.

01

Server Integration

DayZ server status, player counts and Nitrado controls presented directly inside Discord.

Nitrado connected
02

Accounts & Profiles

Link Discord members with their PlayStation identity and maintain one consistent community profile.

Player focused
03

Economy & Games

Community balances, rewards, transfers, bounties and individual gambling commands built into the bot.

Always expanding
04

Moderation & Logging

Warnings, player notes, administration records and clear Admin logs for accountable decisions.

Admin tools
05

Tickets & Support

Structured support workflows that keep requests out of Admin DMs and in the correct channels.

Community support
06

Configuration Control

Backups, validation, comparisons and controlled restoration for safer DayZ configuration changes.

Control centre

Slash commands

Clear Commands
No Confusing Prefixes

The bot uses Discord slash commands, organised into straightforward systems. Gambling features use their own commands—such as /slots—instead of being hidden beneath a parent command.

Use the bot in our Discord

WORLD WAR Z BOT

/serverLive DayZ server information
/profileYour linked community profile
/economyBalances, rewards and economy tools
/slotsPlay the community slot machine
/ticketOpen a structured support request

Development roadmap

WWZ Live — Badlands World Profiles Roadmap

The primary WWZ world is selected from the live server registry. Badlands (Nasdara) is the new primary-world map; Livonia is independent and Chernarus data remains preserved for rollback. The original Nasdara paper map v1.2 now provides town names, printed roads and a calibrated X/Z grid. Stage 1 World Manager is verified, Stage 2A provides isolated Badlands staging storage, and Stage 2B Phase 3 now guards four live XP/reward producers (Chernarus expedition, Chernarus progression, Livonia hotspot and community event rewards), while remaining gameplay, banking and worker paths still require migration. Stage 2C Phase 2 adds Admin-only full-roster scans and audited dry-run plans (v2.11.1 hardens status, duplicate handling and audit logs); Stage 2D Phase 4 adds bounded on-demand live Discord message verification to the registered Trader/status/event planning inventory (v2.15.0), building on active-world branding (v2.12.0); the v2.16.0 launch gate exposes production blockers, and v2.17.0 adds a physically separate Badlands Bot database, explicit mission configuration and fail-closed gameplay quarantine; a protected role cutover and automatic identity-only import are now available; external backups, the official map mission and final gameplay activation remain gated. New owner-authorized runtime cutover is available after a live mission match, private database checks, role reconciliation, verified backup/rollback and map checks; the world stays quarantined until those gates pass.

Roadmap updated 17 October 2026 Website v2.19.0 · Bot v1.82.0
Available now Live server Staged · verify live Next development Future · blocked
01
Available now

Connected WWZ Community Platform

The World War Z bot, dashboard, Survivor Shop, Railway API and Discord integration operate as one connected platform with authenticated server/world context.

  • Discord ↔ PlayStation linking, survivor profiles, economy, gambling, PvP, sessions/playtime, XP/Prestige, quests, bounties and contracts.
  • Synchronized Discord + website tickets, moderation, appeals, live ban lists, audit history, rentals and automatic delivery workflows.
  • Owner Configuration Control, Nitrado controls, restart intelligence, validation/backups and server-side permission enforcement.
  • The signed-in member landing page now acts as a personalised command centre for progression, quests, faction activity, events, orders, support and current priorities.
  • Owner-only Data Management provides verified whole-database backups, server-isolated exports and offline restore safeguards.
  • Validated Chernarus and Livonia maps with roads/trails, labels, coordinates, markers, saved locations and shared map tooling.
  • Admin Zones with circular/polygon geometry, protected zone overlays, cached-ADM Online Players mapping and Discord entry/exit alerts.
02
Available now

Discord Access & Dual-Map Routing

Discord authentication, server selection and server-configured Chernarus/Livonia routing are complete.

  • Members see only Discord servers they can actually access, with Railway rechecking membership and roles for protected work.
  • Each selected server controls its own map, dimensions, coordinates, Nitrado service, mission paths and mutable guild-owned records.
  • Public markers, private pins, Shop/rental coordinates and saved locations remain separated by world.
03
Available now

WWZ Server Companion PWA

The existing GitHub Pages website can now be installed as the WWZ Server Companion without creating a second frontend.

  • Windows and mobile installation have been confirmed in real-device testing while normal browser access remains unchanged.
  • The installed app uses the same Railway API, Discord authentication, database, server selection and feature set as the website.
  • Static app-shell assets use safe PWA caching while Railway/API/admin/Nitrado operations remain network-only.
  • Map caching is bounded and on-demand rather than precaching the full Chernarus/Livonia tile sets.
  • The service worker now supports fully opt-in browser push, while the same website release can be prepared for Android/iOS through the Capacitor wrapper foundation.
04
Available now

One-Bot Multi-Server Foundation

One Railway bot supports both WWZ Discord/DayZ services while keeping mutable server-owned data isolated by Discord guild.

  • The server registry binds each guild to its map, coordinate boundary, Nitrado service and mission files.
  • Commands, workers, ADM monitoring, status/restart caches, configuration paths and backups follow the active server context.
  • The same 100-command inventory is synchronized into every registered WWZ Discord guild.
  • Shared Discord↔PSN identity remains compatible while progression, economy, PvP and other mutable records remain guild-scoped.
05
Live now · 26 slots

Livonia Full PvP

Livonia is now open to players as the 26-slot World War Z Full PvP server, while retaining its own isolated Discord, Nitrado and gameplay state.

  • 26 player slots on PlayStation 4 / PlayStation 5 with Full PvP, high loot and 91 random PvP loadouts.
  • Heli crashes, convoys, WWZ combat sites, dynamic gas, PvP hotspots, Most Wanted and faction competition are active Livonia features.
  • Livonia uses its own Nitrado service and dayzOffline.enoch mission. The primary Nitrado server runs the currently configured WWZ world; historic Chernarus files are preserved for rollback.
  • Livonia progression, economy, PvP, tickets, factions, zones, feeds, donation orders, locations and configuration continue from their preserved Livonia-owned records.
  • ADM, status, shop/delivery and moderation workers resume independently for Livonia when its runtime is active.
  • Chernarus and Livonia can now operate simultaneously without sharing mutable gameplay or administration state.
  • Livonia includes the Deathmatch configuration rotation foundation with profile-matched Discord messaging and restart-safe JSON staging; activation remains Admin-controlled and now refuses to enable until its mission root and at least one valid arena profile are ready.
06
Production verified

Natural XP & Prestige

Natural XP progression and Prestige have been confirmed working in live use and are no longer waiting on production verification.

  • Natural level progression updates the existing Discord role, economy reward, announcement, /rank and /profile path as designed.
  • The Level 100 → Prestige transition preserves Lifetime XP while resetting the active progression cycle and applying the expected Prestige state.
  • Prestige rewards remain protected by the existing duplicate-safe progression ledger.
  • No historical PvP XP backfill is planned or required for the verified system.
07
Available now

Chernarus Survivor Passport & Exploration

Chernarus retains its configured PvE-era Survivor Passport and exploration progression. However, Road to Badlands: Total Chaos currently overrides the normal PvE / military-zone rules with full-map PvP and base raiding until Badlands releases on PlayStation.

  • For the ongoing Total Chaos event, full-map PvP and raiding apply; the previous PvE / military-zone configuration remains preserved for rollback.
  • Survivor Passport discovery across 27 Chernarus locations with categories, completion percentage, badges, milestones and a private personal map layer.
  • Per-life survival records, validated distance travelled, PvE reputation ranks and multi-stage no-death WWZ Operations with ordered and dwell-based stages.
  • Travel/PvE-heavy daily and weekly quests, weekly community campaigns, existing-faction PvE standings and seasonal survival/exploration records.
  • Console-safe tracking uses valid ADM position/activity telemetry only; unsupported infected or animal kill totals are never inferred.
  • Livonia PvP Operations remain isolated and unchanged.
08
Available now

Notifications & Community Workflow Enhancements

The shared platform now includes community analytics, reusable event automation, member-controlled browser notifications and a repeatable native-wrapper foundation without forking the website.

  • Fully opt-in Web Push topics for scheduled events, meaningful server-status changes, personal ticket replies, PvE/PvP rotations and shop/order updates.
  • Reusable event plans with staff scheduling, immediate starts, Discord announcement routing and restart-safe reminder/start/end transitions.
  • Privacy-safe Chernarus/Livonia analytics built from existing console-safe ledgers, including activity timelines, active locations, participation and server-FPS summaries.
  • A responsive Community Hub improves touch/mobile access to analytics, the event calendar, notification preferences and staff Event Planner.
  • A Capacitor 8 wrapper foundation prepares the same canonical website release for Android/iOS; store signing and publication remain external developer-account steps.
09
Stage 1 · verified

World Profiles & Admin World Manager

World-profile readiness has been confirmed in live Admin testing (Bot v1.68.0 / Website v2.5.0). No map, player balance or Discord role changes were triggered.

  • The primary world is selected through the live registry; all Chernarus records and map assets remain preserved for rollback.
  • Badlands is a separate staged world profile; Livonia stays fully independent and unchanged.
  • Admin-only World Manager displays profile readiness, migration blockers and a non-destructive Discord role-change preview.
10
Stage 2A · deployed, verify live

Badlands Economy & Progression Storage

Bot v1.69.0 / Website v2.6.0 establishes isolated Badlands staging and a domain coverage tracker. Deployment has been reported; final live validation is pending.

  • Transaction-safe Badlands-only XP/levels/prestige, wallets, bank balances, ledger and transfer operations are staged and tested.
  • Fresh factions, claims, coordinates and other world-owned records have separate staging structures.
  • Badlands starts at Level 1, XP 0 and Prestige 0, with fresh economy and faction progression. Existing Chernarus levels, balances, ranks and history are preserved.
  • Production Discord commands and automated jobs still use existing Chernarus/Livonia storage; installing this release does not reset anyone.
11
Stage 2B · Phase 3 partial integration

Gameplay & Transaction World Routing

Bot v1.72.0 / Website v2.9.0 connected four audited, idempotent XP and wallet-reward producers to the guarded live-world write gateway. Legacy Chernarus/Livonia ledgers are preserved. Most gameplay, banking and worker paths still require integration.

  • Phase 1: inspect Chernarus XP, levels, prestige, wallet and bank alongside Badlands staging without resetting or creating accounts.
  • Phase 2: guarded XP/prestige and wallet/bank write adapters added with guild/map validation.
  • Phase 3: Chernarus expedition and PvE milestone awards, Livonia hotspot awards and manually approved community event payouts now use the live-world gateway; IDs, metadata and legacy duplicate protection are preserved.
  • Next: audit and migrate quest claims, banking commands, contracts, bounties, factions, shop, rentals, workers and remaining gameplay paths; complete transaction and replay guarantees before activation.
  • Separate faction/claim records, purchases, carts, rentals, delivery coordinates, events and scheduled workers.
  • Reconcile pending orders and test all money-changing paths against cross-world leakage and replay before permitting activation.
12
Stage 2C · Phase 2 ready

Automatic Discord Role Reconciliation

Read-only plans can now be staged from a verified full Discord member scan, preserving Badlands fresh-start and Chernarus rollback role deltas in an audited SQLite snapshot. Applying roles remains locked.

  • Reset Badlands level, prestige, rank and faction roles to reflect its fresh world data; restore corresponding Chernarus roles on rollback.
  • Preserve Verified, Admin, donor, moderation, Livonia and unrelated roles; respect Discord role hierarchy and rate limits.
  • Persistent dry-run snapshots and audit history built, with duplicate plan protection and safer scan feedback; execution worker, live retry queue and actual Admin resync remain blocked until authorised migration.
15
Stage 2D · Phase 3 ready

Automatic Active-World Branding

Phase 3 (v2.14.0 / Bot v1.77.0) expands the audited registry to newly published or refreshed Chernarus Radio Zenit Trader panels and verified server-status edits. World Manager now shows metadata-only transition actions: preserve historical event announcements and Chernarus Trader coordinates, prepare new Badlands panels only when map data exists. Live author/permission preflight, Discord edits and activation remain locked.

  • Load current-world titles and descriptions from one authoritative world profile; never rewrite historical Chernarus records or Livonia names.
  • Refresh Bot-owned editable panels and calendar embeds, and identify old messages requiring replacement announcements.
  • Protect unmanaged Discord channels, roles, events and server names from blanket renaming; activation and map-dependent work remain locked.
13
Stage 3 · awaiting platform support

Badlands Map & Nitrado Readiness

Do not invent or substitute Badlands coordinates, mission paths, map tiles or console server support before official assets are available.

  • Verify official DayZ PlayStation and Nitrado Badlands mission support before constructing deployment-ready configurations.
  • Load world-specific tiles, markers, PvP zones, trader locations, spawn and delivery coordinates only from reliable Badlands data.
  • Preserve every Chernarus tile, map marker, mission rule and customisation as a reversible fallback.
14
Stage 4 · activation locked

Verified Backup, Migration & Rollback

Activation will require an Admin confirmation, verified external backups, controlled DayZ/Nitrado mission transition and post-switch checks.

  • Archive and test-restoring Chernarus data, world configuration and relevant DayZ persistence before any switch.
  • Pause/reconcile pending Chernarus transactions, validate Badlands and then activate world-specific gameplay plus Discord role sync.
  • Keep rollback able to restore Chernarus's original player levels, economy, factions and world-specific roles.
  • Complete Road to Badlands: Total Chaos through its existing Admin-confirmed ending action when Badlands is released on PlayStation.
15
Later improvements

Production QA & Optional Store Publication

Continue production observation, map accessibility refinements and optional native-store publication alongside world migration work.

  • Observe event reminders, user opt-ins, analytics, progression and delivery handling under real community activity.
  • Maintain the installable WWZ Companion PWA; mobile app-store signing and review remain optional future work.
  • Keep console mission compatibility checks aligned with official DayZ updates.

Migration safety rule: No Badlands activation, world-wide economy reset, automatic Discord role edits or Nitrado mission switch is enabled by Stage 2B Phase 3. Chernarus balances, progression, roles, map assets and world settings remain preserved; Livonia stays independent. Badlands launches with fresh world progression only after all live data paths, backups, role sync and console map readiness have passed verification.

Frequently asked questions

Know What Is Live—And What Comes Next

The dashboard displays live DayZ server information, a public interactive current-world map and each signed-in member's own survivor profile and economy summary. Verified Admins and the Owner can also use protected, audited Start, Stop and Restart controls.

Is the dashboard using live server data?

Yes. Server status, player count, capacity, map, platform, Railway uptime, Discord health, sanitized Nitrado state and update time are public. Signed-in members can also load their own verified profile and economy summary.

Can I sign in with Discord?

Yes. Discord identifies your account, then Railway checks your current membership and roles in the World War Z server. Only the basic identify permission is requested.

Will members and Admins see the same tools?

No. Members see personal self-service areas. Admin and Owner navigation stays completely hidden unless Railway verifies the required Discord access. Railway checks again before accepting any protected server action.

Is the WWZ map public?

Yes. Visitors can pan, zoom, search and view approved public markers without signing in. Live players, private bases, Admin positions and unpublished events are never shown.

Does the website store bot tokens?

No. Discord bot tokens, Nitrado credentials and other secrets must never be placed in this public GitHub Pages website.

Survive together

Join The World War Z Community

Connect with other survivors, access the bot and stay up to date with server news and events.

discord.gg/worldwarzps