Documentation / Grizzly DayZ

Current DayZ setup, player flow, delivery, and admin surface truth.

Use this page for the current DayZ bot behavior: Online Now, player linking, default welcome, optional extra roles, base and faction setup, managed placement lifecycle, Discord layout, and control panel maturity.

Buttons firstProof-aware deliveryPlayer-safe online roster

Player linking and Online Now

Online Now is a player-safe roster that shows in-game names only.
It never shows locations, coordinates, Discord mentions, role mentions, or admin-only details.
If linking is not ready, join the DayZ server, wait for the online-player refresh, then retry with the exact in-game name and spelling.

Base and faction setup

Base setup is player-facing for eligible linked players and is no longer documented as admin-only or test-only.
Base and faction templates preserve reference offsets, scale, and YPR. They do not rotate to north.
Faction setup starts from the existing private base channel. The channel remains a base channel until faction creation succeeds, then becomes the faction channel.
Faction armbands are derived from the selected base flag, such as Flag_Bear to Armband_Bear.

Managed placement lifecycle

Queued or staged means the placement is waiting for the managed delivery process.
Uploaded means the JSON reached the service, not that it is live in game.
Placements still need restart proof and may also need live in-game proof.
Recycled or cleaned historical rows are separated from active placement work.

Welcome, rules, and roles

A default welcome exists when no custom welcome template is configured.
Rules acceptance still gives the default Player role.
Player link success still gives the default Linked Player role.
Guild admins can configure optional extra local roles for rules acceptance and player-link success.

Expected Discord layout

Server Information

#welcome
#rules
#online-now
#player-link
#weekly-events
#banned-players
#player-chat

Player Economy

#economy
#general-shop

Quests and Bounties

#bounties
#quests
#quest-logs
#admin-quest

Admin

#grizzly-setup
#dayz-control-panel
#admin-logs

These stale channels are no longer part of the standard managed layout: #server-info, #status-and-updates, #economy-help. Existing old channels may be reported as deprecated instead of deleted unless safe cleanup rules apply.

Feature maturity

Control panel

#dayz-control-panel is the persistent admin settings hub. Extra rules role and extra linked-player role controls are live. Other categories may be read-only or planned.

Feature maturity

Player management

Banned-player status is read-only capability truth with banlist readback/local evidence. Whitelist and admin-list mutation controls are not claimed yet.

Feature maturity

Weekly events vs event intel

Weekly Events are admin-created calendar items with RSVP and reminders. Event Intel is dynamic detection from logs or host signals and must be labeled by confidence.

Feature maturity

Economy, shop, bounties, jobs, tickets

These systems are active surfaces, but docs use cautious wording where anti-abuse, status health, stale private-channel cleanup, or placement-proof dependencies still need polish.

Admin notes

Managed surfaces are expected to be canonical: setup panels, faction showcase cards, welcome templates, Online Now cards, and the DayZ control panel should edit or repair in place.
Duplicate bot-authored managed panels can be cleaned safely. Human messages are preserved.
Admin and runtime logs belong in #admin-logs, not in control panels.
Public server listings remain data-driven through the admin-created listing flow. Grizzly-owned servers do not bypass normal listing visibility.

Copy warning

Do not treat uploaded JSON as live.

Managed placement copy should distinguish uploaded, waiting restart proof, waiting live proof, failed, recycled, and historical states. The same caution applies to placement-backed shop items.

View DayZ product page Find Support Paths