Documentation / Grizzly DayZ

The live DayZ product surface for operations, support, and player workflows.

Grizzly DayZ is the active operations product for feeds, economy, shop workflows, ticket-linked support, and manual review. The docs stay aligned with what the bot actually does today.

Live runtimeManual review truthTicket-linked workflows
Use this page when

You need the live DayZ picture, not a generic overview.

  • You are checking what the live DayZ product actually supports right now.
  • You need the current support, economy, shop, ticket, or feed workflow context.
  • You want the documented path before escalating into support.
What you leave with

A clearer next step for live operations, player workflows, or support.

  • Which parts of DayZ are live today.
  • Which workflows stay manual on purpose.
  • Which command groups and support routes actually fit the problem.

What is live now

  • ADM-driven feeds and activity tracking
  • Player linking, profiles, and verification review
  • Economy balance, dailies, grants, removals, and history
  • Shop listing, buying, pending review, fulfillment, and delivery-marker capture
  • Tickets for verification, bounty review, shop support, and general issues

Operational truths

  • Manual fulfillment stays honest. The system does not fake automated in-game item delivery.
  • Verification review shares the ticket surface, but /verify-player remains the real verification command.
  • Bounty claim automation is not active. Tickets provide the manual review layer where needed.
  • Linked ticket outcomes only trigger real state changes where those flows already exist.
Command groups
Setup
/setup-status, /setup-start, /setup-welcome, /setup-rules
Players
/player-link, /profile, /stats, /leaderboard
Economy
/economy balance, /economy daily, /economy history
Shop
/shop list, /shop buy, /shop history, /shop pending
Bounties
/bounty list, /bounty create, /bounty cancel
Support
/ticket create, /ticket list, /ticket close, /verify-player
After this page

Use support only when the docs have narrowed the issue far enough. That keeps setup, shop review, and manual follow-through moving through the right path instead of dropping straight into a generic help request.