Setting up dzBot

Step 1Invite dzBot to your Discord server

Nothing else can happen until the bot is a member of your server.

Open the invite link the operator sent you, choose your server from the dropdown, and authorise.

Don’t untick any permissions. dzBot needs to manage channels (ticket and faction threads), manage roles (linked, banned and faction roles), manage messages (replacing its own panels), manage webhooks (feed posting), and to read and send messages. Removing one doesn’t make the bot safer — it makes a feature silently fail later.

The moment it joins, dzBot registers its commands for your server, sends a welcome message to whoever clicked Authorise, and posts a short note in your system channel.

You’ll know it worked when: dzBot appears in your member list, and you get a direct message or a post in your server within a few seconds.

Step 2Check you can see dzBot’s commands

Every setup step is a slash command, so if they don’t appear, nothing else works.

A slash command is what Discord shows when you type / in a message box — a menu of things a bot can do. Type / in any channel and look for dzBot’s entries: /install, /setup, /player, /nitrado.

dzBot registers its commands directly to your server when it joins, so they’re normally there straight away — no waiting.

You’ll know it worked when: Typing /install offers dzBot’s install command.

Step 3Run the install wizard

One command sets the three things dzBot can’t work without, and there is no other way to set them.

/install is a guided wizard: it asks one question at a time and saves each answer as you go. Close it halfway and nothing is lost — run it again and you pick up where you left off. It’s also how you change any of these later.

It walks through five things:

Audit channel — a channel where dzBot posts every action it takes. Pick a private, staff-only channel. You’ll read it constantly for the first week, and after that it’s your record of who changed what.

Admin role — the Discord role allowed to use dzBot. Without one, only people with Manage Server can use it at all.

Nitrado connection — your Nitrado API token and the service ID of your DayZ server. A *service ID* is the number Nitrado uses for one hosted server. dzBot checks the connection against Nitrado while you wait and only saves it if it works.

Modules — which features to turn on. Tick Event Feeds unless you have a reason not to: it starts the log reader that everything else feeds from, including player records, the live map and stats.

Your plan — a summary of what your community’s plan includes.

You’ll know it worked when: The wizard finishes with a recap listing your audit channel, admin role and connected server.

Step 4Confirm the audit channel is working

If the audit log is silent, you have no record of what dzBot or your staff did.

You set the audit channel in the install wizard, back in step 3 — this step is how you check it actually works.

Open /setup and choose Show current config → Overview. Your audit channel should be named there.

Then look at the channel itself: the install you just ran should already have posted to it.

You’ll know it worked when: Your chosen channel is listed, and it already has posts in it from the install.

Step 5Confirm dzBot is reading your server

A saved connection proves nothing on its own — this proves the logs are actually arriving.

dzBot reads your DayZ server’s log files every minute or so. That reading is what feeds player records, kill feeds, the live map and stats.

Run /nitrado status. On the dashboard, the same thing is the Last sync time in the corner.

The first read can take a few minutes after connecting. Leave it and come back.

You’ll know it worked when: Status shows a tick, and the dashboard shows a recent sync time.

Step 6Give your staff access

Until you do, only people with Manage Server on Discord can use dzBot.

The admin role from step 3 is the blunt version: everyone with that role can use everything.

For anything finer, use the dashboard’s Access page. You can grant one person or one role a specific set of powers — reviewing whitelist applications but not touching bans, for instance — and scope them to one of your DayZ servers.

You’ll know it worked when: Someone on your staff, who does not have Manage Server, can run a dzBot command.

Step 7Run the health check

One screen that lists everything still missing, and the exact fix for each.

Open /setup and choose Health check. Every setting dzBot cares about is listed with a tick, a warning, or a cross.

A cross means something is broken or unusable. A warning means an optional setting isn’t configured — you can leave those.

The dashboard shows this same check as your setup checklist. They can’t disagree: it is the same code answering both.

You’ll know it worked when: No crosses. Warnings are fine.

Step 8Turn features on, one at a timeOptional

Each one needs a channel or a role, and switching them all on at once makes a bad configuration hard to find.

Everything from here is optional, and each is set up from the dashboard. Do one, check it behaves, then do the next.

Most of these are per server. If your community runs more than one DayZ server, pick the server in the sidebar first — the channels, roles and settings you choose apply to that one alone.

Feeds — post what happens on your server into DiscordOptional

Kills, connections and base building land in the channels you choose.

Dashboard → Feeds. Build a feed, choose which events it carries and which channel it posts to.

Per server. A feed built for one server never posts another server’s events.

You’ll know it worked when: A player connects and a message appears in the channel you picked.

Whitelist — control who can joinOptional

Players apply in Discord and approved names are written to your server automatically.

Dashboard → Whitelist. Set the channel where players apply and the channel where your staff review.

Per server. Each of your DayZ servers keeps its own whitelist.

You’ll know it worked when: A test application appears in your review channel.

Bans — ban once, everywhereOptional

A ban applies on the DayZ server and in Discord together, from one command.

Dashboard → Bans. Set the log channel where bans are recorded, and optionally a role applied to banned members in Discord.

Per server.

You’ll know it worked when: A test ban is written to Nitrado and posted in your log channel.

Tickets — support requests in private threadsOptional

Players open a ticket from a panel; your staff answer in a thread only they can see.

/setup → Tickets sets the channel, the handler role, and the categories a player can pick from.

Publish the panel when you’re done — until you do, players have no way to open one.

Tickets are community-wide, not per server. If your community runs several servers, you can have the panel ask which one a ticket is about.

You’ll know it worked when: The panel is posted in your tickets channel and its button opens a thread.