Server Integration
DayZ server status, player counts and Nitrado controls presented directly inside Discord.
Nitrado connectedWorld War Z operations 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.
No need to learn every system at once. These four destinations cover the essentials: sign in, learn the rules, shop and get support.
One connected control centre
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
Each system is designed to work together, giving players a smoother experience and Admins a clearer view of the server.
DayZ server status, player counts and Nitrado controls presented directly inside Discord.
Nitrado connectedLink Discord members with their PlayStation identity and maintain one consistent community profile.
Player focusedCommunity balances, rewards, transfers, bounties and individual gambling commands built into the bot.
Always expandingWarnings, player notes, administration records and clear Admin logs for accountable decisions.
Admin toolsStructured support workflows that keep requests out of Admin DMs and in the correct channels.
Community supportBackups, validation, comparisons and controlled restoration for safer DayZ configuration changes.
Control centreSlash commands
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.
WORLD WAR Z BOT
Development 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.
The World War Z bot, dashboard, Survivor Shop, Railway API and Discord integration operate as one connected platform with authenticated server/world context.
Discord authentication, server selection and server-configured Chernarus/Livonia routing are complete.
The existing GitHub Pages website can now be installed as the WWZ Server Companion without creating a second frontend.
One Railway bot supports both WWZ Discord/DayZ services while keeping mutable server-owned data isolated by Discord guild.
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.
dayzOffline.enoch mission. The primary Nitrado server runs the currently configured WWZ world; historic Chernarus files are preserved for rollback.Natural XP progression and Prestige have been confirmed working in live use and are no longer waiting on production verification.
/rank and /profile path as designed.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.
The shared platform now includes community analytics, reusable event automation, member-controlled browser notifications and a repeatable native-wrapper foundation without forking the website.
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.
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.
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.
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.
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.
Do not invent or substitute Badlands coordinates, mission paths, map tiles or console server support before official assets are available.
Activation will require an Admin confirmation, verified external backups, controlled DayZ/Nitrado mission transition and post-switch checks.
Continue production observation, map accessibility refinements and optional native-store publication alongside world migration work.
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
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.
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.
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.
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.
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.
No. Discord bot tokens, Nitrado credentials and other secrets must never be placed in this public GitHub Pages website.
Survive together
Connect with other survivors, access the bot and stay up to date with server news and events.