Skip to main content

Getting started

This guide combines installation and the essential first steps so dzbot works reliably after you connect your server.

Requirements​

  • A DayZ server hosted on Nitrado (PC / PS / XBOX)
  • A Discord account to sign in to dzbot

Wait until your DayZ server is fully available in Nitrado before you start.

1) Log into dzbot​

Open dzbot.de and use Sign in in the top navigation.

After login:

  • My servers shows all linked servers directly in the website navigation. On mobile, use My servers in the main navigation to open a servers-only modal with the Connect server action.

2) Connect your server​

Use Connect server in the top navigation (or Connect new server on the homepage hero) to start the Nitrado OAuth flow.

  • If your account has one DayZ server, dzbot connects it directly.
  • If your account has multiple DayZ servers, you can choose which one to connect.

After connecting, you are redirected to your server home page.

Connection notes​

  • "No code provided": the OAuth callback was interrupted. Start the connection flow again from the website navigation.
  • "No DayZ servers found": confirm your Nitrado account has at least one active DayZ service.
  • Token expired: reconnect from Server Admin → Settings. dzbot also shows an alert in the admin area when reconnect is needed.

3) Open the Admin Panel​

Use Server Admin in the top-left of your server page to enter the admin area.

Tip: You can always return to the player view with Open Shop in the admin header.

4) Set the admin player name​

Open Server Admin → Players and find the admin player. Change the username to your in-game username so dzbot does not create a second player profile when logs arrive.

If a player profile already exists with your username, open a ticket in Discord so a moderator can merge the accounts.

5) Run the DayZ++ user migration (optional)​

If this server currently runs DayZ++ / killfeed.xyz and you want to keep your existing linked users, use the User migration step in the setup flow before you finish the rest of the initial setup.

Follow the dedicated User migration guide to request API access, create the correct API key, and start the import from Server Admin → Setup.

6) Update core server settings​

Navigation path:

  • Server Admin → Settings

Recommended values to review:

  • Server name: short community name used across the UI.
  • Subdomain: your player-facing URL (<subdomain>.dzbot.de).
  • Timezone: used by the scheduler and time-based logs.

7) Enable player list synchronization​

In Settings → Integrations:

  • Enable Synchronize player lists.

This makes dzbot the source of truth for whitelist, restriction (ban), and priority lists, and keeps Nitrado aligned. All ban, whitelist, and priority entries that existed in Nitrado at the time you connected your server were already imported automatically, so no entries are lost. Once sync is active, dzbot overwrites those lists on every sync — changes made directly on Nitrado or via other tools will be overwritten.

In Settings → Players & Access:

  • Enable Whitelist enabled if you run a controlled community.
  • Enable Auto-whitelist linked players to reduce manual approvals.

For full behavior and smart whitelist logic, see Whitelisting.

9) Connect Discord integration​

Step 1: Connect the server and install the bot​

In Settings → Discord:

  • select Discord Server from the guilds available through your connected Discord account
  • Save your settings

After saving, dzbot checks the Discord connection. If the bot is not installed, you will see an admin alert with an install link. Follow that link to add the bot to your Discord server.

Step 2: Configure optional Discord channels​

Once the bot is installed, return to Settings → Discord and choose the optional Discord targets from the dropdowns:

  • Discord Support Channel (support/task notifications)
  • Discord Online Players Channel (live list channel)
  • Discord Base Alarms Category (auto-managed channels)
  • Discord Killfeed Channel (PvP kill messages)
  • Discord Damage Feed Channel (PvP damage messages)
  • Synchronization of Discord names (optional)

If you just changed the Discord server, save first and then reopen the Discord settings tab after the bot has been added there so the channel and category dropdowns can refresh for that server.

For the full integration model and role requirements, see Discord integration concept.

10) Verify log import health​

Many features rely on imported server logs (map activity, killfeed, player routes, log explorer, actions).

Check Server Admin → Log Explorer and confirm you see recent entries. If results are empty, wait a few minutes and re-check. For expected delays, see Logs import concept.

Next steps​

Continue with Second steps for deeper feature setup and optional enhancements.