Product / Grizzly DayZ

DayZ server operations with player-facing setup and proof-aware delivery.

Grizzly DayZ connects Discord setup, live online-player proof, base and faction workflows, economy tools, support, and Nitrado-backed operations. The bot is explicit about timing: uploaded JSON is not treated as live until restart and live proof say so.

Online NowBase + FactionPlacement lifecycleAdmin control panel
Current DayZ Surface

Player setup that starts in Discord

Players accept rules, link their in-game name with live server proof, check Online Now for refresh visibility, and use player-facing panels where the bot owns the flow.

Current DayZ Surface

Base and faction setup

Eligible linked players can start base setup, raise the watched White Flag, finish the private base flow, and later create a faction from the same channel.

Current DayZ Surface

Managed placement lifecycle

Bench, flag, and faction armband JSON delivery is tracked as queued, waiting upload, uploaded, waiting restart proof, waiting live proof, failed, recycled, or historical.

Current DayZ Surface

Admin control surfaces

The DayZ control panel is the preferred settings hub. Some categories are live controls today, while deeper diagnostics and mutating tools remain admin or operator guarded.

Player truth

Online Now is public-safe proof visibility.

  • Online Now shows in-game player names only.
  • It does not show locations, coordinates, Discord mentions, linked Discord users, role mentions, or admin-only details.
  • Player linking still requires live server proof from the online-player refresh.
Delivery truth

Managed JSON delivery is tracked in stages.

  • Queued or staged
  • Waiting for upload window
  • Uploaded to the service
  • Waiting for restart proof
  • Waiting for live in-game proof
  • Live, failed, blocked, recycled, or historical
Feature maturity
Ready to describe
Player linking, Online Now, welcome/rules roles, base setup, faction identity, managed placement lifecycle, economy accounts, shop workflows, bounties, jobs, tickets, and weekly events.
Use cautious wording
Placement-backed shop fulfillment depends on the same proof lifecycle. Economy, bounties, jobs, and tickets are active but still need polish and health reporting.
Do not overclaim
Whitelist and admin-list mutations are not advertised as supported. Control panel categories are organized, but not every category is fully interactive yet.
Server listings stay data-driven

Public server cards come from normal admin-created server listings. Grizzly-owned servers use the same listing system as everyone else; unlisted servers are not added as static product cards.

View DayZ docsJoin the Grizzly Discord