Docs

Welcome to .bOne

This is a full walkthrough for setting the bot up from scratch, step by step, in plain language ; no experience needed. Use the ◀ Prev / Next ▶ buttons below to go through it in order.

Before you start: every command here needs you to be a server Administrator (or hold whatever role gets set as the ".bOne Admin" role in step 5).

There are 9 steps to get fully working, plus a couple of pages on what to look at once you're set up. Hit Next to begin.

▸ Step 1 of 9: Connect to your DayZ server

Command: /setup nitrado

This is the very first thing to do ; nothing else works until this is done. It opens a private popup asking for your Nitrado API Token and Service ID.

Where to find those: log into your Nitrado account → your game server → the API/token section of your Nitrado web panel. If you're not sure, search "Nitrado API token" on Nitrado's own help site, or ask in the support server (/support).

If you run more than one DayZ server on this Discord, add server:<name> to this command; see the "Running more than one server?" page near the end of this guide.

Step 2 of 9: Tell the bot your map

Command: /setup map map:<Livonia | Chernarus+ | Sakhal>

This makes location names in the event feed (kills, deaths, etc.) show real town/area names instead of raw coordinates, and makes heatmaps/loot maps line up correctly. Pick whichever map your server actually runs.

Step 3 of 9: Create the bot's channels

Command: /setup auto-channels

This is the fast path, and the recommended one: one command that builds every channel the bot needs: kill feed, connect/disconnect, chat, dynamic events, tickets, heatmap, and more, neatly organized into their own category, and creates the .bOne Admin role at the same time.

If you'd rather build channels one at a time yourself instead, that's what /channel create is for; most admins never need it once auto-channels has run. If you ever want to undo everything auto-channels made, /remove auto-channels confirm:true cleans it back up.

Step 4 of 9: Turn on your DayZ server's event logging (CRITICAL)

Dynamic events, vehicle spawns, heli crashes, convoys, and police events, the channels step 3 just created, only show up if your DayZ server is actually writing them to its logs. .bOne can't detect what the server never logs, no matter how the channels are set up.

What to do: open your server's mission folder (matches your map, e.g. shown in your host's file manager under mpmissions) and find cfgeconomycore.xml. In its <defaults> block, make sure these are set to "true":

log_ce_loop, log_ce_dynamicevent, log_ce_vehicle

Most servers ship with these off by default: this is the #1 real-world reason event feeds silently stay empty. If your host's file manager (e.g. Nitrado) lets you edit files directly, edit it there ; otherwise ask their support to check it for you.

While you're in there: the rest of the log_ce_* flags in that same block (loot spawn/cleanup/respawn, statistics, zombie, animal) don't hurt to enable too, and give your host fuller logs to troubleshoot with if something still looks off.

Step 5 of 9: Set your Player role

Command: /setup player-role role:<@role>

Tell the bot which role your normal, everyday "verified player" members have. This is needed for /tempban: when someone's temp-banned, the bot temporarily takes this role away and gives it back automatically once the ban ends.

Make sure .bOne's own role is positioned ABOVE this role in Server Settings → Roles, or the bot won't actually be able to add/remove it; the command will warn you if it isn't.

Step 6 of 9: Set your Ban role

Command: /setup ban-role role:<@role>

The role /tempban swaps a punished player INTO while they're banned (the opposite of the Player role above). Set this role's own channel permissions however you want in Discord's normal role settings; the bot only ever assigns or removes it, it doesn't configure what it can/can't see.

Same role-position rule as step 5: .bOne's role needs to sit above this one too.

Step 7 of 9: FTP access (optional)

Command: /rotation setup-ftp

Only needed if you want the loot-table/event rotation feature (automatically swapping in different heli crashes, convoys, vehicle spawns, etc. on a schedule). Opens a private popup for your server's FTP host, port, username, and password (also from your Nitrado panel).

Totally fine to skip this one and come back to it later; nothing else in this guide depends on it.

Step 8 of 9: Set up support tickets

Command: /ticket quicksetup

Creates a staff role, a private ticket-log channel, and posts an "Open a Ticket" button in one go, so players can privately message your staff team.

If you already ran /setup auto-channels in step 3, this is already done; this step is for anyone who skipped that or wants to redo just the ticket piece.

Once it's set up, /ticket category-role-add lets you pick exactly which staff role(s) automatically see each type of ticket, e.g. only your ban-appeals team sees Ban Appeal tickets, not every category. Covered in more detail under "What to look at next" below.

Step 9 of 9: Check your work

Command: /setup view

The final checkpoint. Shows everything configured so far in one place: Nitrado status, map, channels, roles, so you can confirm each step actually took effect before moving on.

That's it: the bot is fully working at this point. The remaining pages cover optional next steps, not required ones.

Running more than one DayZ server?

If you have 2+ DayZ servers on this one Discord, do this first:

/setup server-add name:<label>: register each additional server (up to 5 total). /setup server-list shows everything you've registered.

Then repeat steps 1, 2, 4, 5, 6, and 7 above for each server, adding server:<name> to each command so the bot knows which server you're configuring (step 4's cfgeconomycore.xml check is per-server too; each server has its own file). Steps 3 and 8 (channels and tickets) and the roles are shared across all your servers and only need doing once.

What to Look at Next (not required, but important)

Once the essentials above are done, these are worth setting up soon:

/setup bot-admin-role / /setup mod-role: let trusted roles besides real server Administrator use .bOne commands. Also on the dashboard's General Settings page.

Moderator Permissions (dashboard only, no slash command): the ONLY place to actually grant your Moderator role access to specific commands, one by one. Without this, a mod role can barely do anything.

/setup auto-role: automatically hands new members a role the moment they join.

/setup bot-trap: a decoy channel that instantly bans any non-staff member who posts in it, to catch raid bots.

/ticket category-add and /ticket category-role-add: add more ticket types and control which staff role sees each one.

/setup backup-export: download an encrypted backup of everything, worth doing once you're happy with your setup.

Optional Features (browse when you're ready)

Everything below is genuinely optional; the bot works fully without any of it. Run /help any time for the full command reference.

▸ /whitelist: restrict server access to an approved player list
▸ /online-count setup: a voice channel showing your live player count
▸ /welcome config: customize the message new members see
▸ /embed create: build and schedule custom announcement embeds
▸ /dz-store: an in-game item shop tied to a Discord economy
▸ /casino: coinflip/dice/roulette/slots minigames
▸ /zone create: geofenced auto-ban zones
▸ /baseping add: pings your team when someone approaches a base
▸ /detect toggle: anti-cheat behavior alerts (underground, dupe, etc.), off by default

Questions? /support has the developer support server. Good luck out there.