Skip to main content

Settings

This page explains all settings currently available in the admin panel and what they do in daily server operations.

Navigation path:

  • Server Admin -> Settings

Generalโ€‹

Server nameโ€‹

Name used across dzbot where the original game server name is too long. Use a short project/community name for clean UI and messages.

Subdomainโ€‹

Your player-facing URL is based on this value: <subdomain>.dzbot.de. Keep it short and easy to share.

Email addressโ€‹

Used for important server-related communication.

Timezoneโ€‹

Used for scheduling behavior (for example scheduler task execution times). If times look wrong, verify this setting first.

Languageโ€‹

Portal default language for your server context. If a player has not chosen a language yet, this setting defines default communication language.

Server is activeโ€‹

Master on/off switch for server functionality. When disabled, feature execution is paused, but connection updates to Nitrado still continue so you can reactivate quickly.

Players and Accessโ€‹

Whitelist enabledโ€‹

Only players on whitelist can join. Admins are automatically whitelisted. For reliable enforcement through dzbot, keep Synchronize player lists enabled.

Auto-whitelist linked playersโ€‹

Players are added to whitelist automatically after successful account linking. Recommended for faster onboarding and less manual work. For this to reach your game server automatically, keep Synchronize player lists enabled.

Include cross-server alt accounts in ban listโ€‹

When enabled, bans with Include all accounts active will also cover device-linked accounts from other servers in the ban list exported to Nitrado.

This means: if a player is banned and that ban targets all linked accounts, any username registered on a different server using the same device is automatically included โ€” even if that account has never played on the current server.

Requires Synchronize player lists to be enabled for the expanded ban list to reach your game server.

Disabled by default โ€” opt in if you want platform-wide coverage across all servers sharing the same device.

For more details on how alt account coverage works in restrictions, see Restrictions concept.

Player position verificationโ€‹

Adds a verification step during account claim. Improves security against incorrect/abusive claims.

Smart Whitelistโ€‹

If enabled and configured, players who register but do not finish verification in time are temporarily blocked until they verify. Set to -1 to disable this behavior.

Default Groupsโ€‹

Groups automatically assigned to new players. Useful for baseline permissions and starter access.

Discordโ€‹

Discord Serverโ€‹

Connects dzbot to your Discord guild. This field shows the Discord servers available through your connected Discord account, so you can select a server even before the dzbot bot has joined it. After saving a new selection, dzbot checks bot installation status in the background. If a server you expect is missing, reconnect your Discord account so dzbot can refresh the guild list with the guilds OAuth scope. If dzbot is not installed yet, the warning link on this page opens Discord's bot authorization dialog with the selected server preselected.

Discord Support Channelโ€‹

Choose the Discord text channel for support/task notifications (for example log access requests).

Discord Online Players Channelโ€‹

Choose the Discord text channel where dzbot keeps an updated online players message.

Discord Base Alarms Categoryโ€‹

Choose the Discord category where dzbot creates and manages base alarm channels.

Discord Killfeed Channelโ€‹

Choose the Discord text channel where dzbot posts PvP kill events.

Discord Damage Feed Channelโ€‹

Choose the Discord text channel where dzbot posts PvP damage events.

Discord Tickets Categoryโ€‹

Choose the Discord category where dzbot creates support-ticket channels.

Discord Tickets Channel Prefixโ€‹

Controls the prefix used for Discord ticket channel names. Use a short, readable prefix such as ticket or support.

Discord Tickets Support Roleโ€‹

Choose the Discord role that should always see and work all ticket channels.

Tickets Auto Archiveโ€‹

If enabled, closing a ticket archives it immediately. This removes the Discord channel instead of leaving it in the closed state and sends the reopen/view DM flow to participants.

Owned Discord Categories (shared guilds)โ€‹

Only needed when two or more game servers share one Discord guild. Select the Discord categories that belong to this server; incoming Discord events in channels inside them (tickets, AI companion) are routed to this server. Leave the list empty to make this server the fallback that handles everything not claimed by another server.

See Multiple game servers in one Discord guild for the full setup guide and pitfalls.

Discord dropdown behaviorโ€‹

  • The guild, channel, and category fields load live data from Discord.
  • Select and save Discord Server first.
  • After saving, reload Server Admin โ†’ Settings โ†’ Discord to refresh the available channel and category dropdowns for that server.
  • If a previously saved Discord selection is no longer available, dzbot keeps the saved value until you replace or clear it.

Synchronization of Discord namesโ€‹

Synchronizes Discord nicknames with in-game player names. Makes support and moderation easier.

Economyโ€‹

Currency Symbolโ€‹

Display label for prices and balances (for example Coins).

Price for Base Alarmโ€‹

Hourly price for base alarm usage. Set to -1 to hide base alarm purchasing from normal shop navigation and prevent hourly billing for active alarms.

Casino Initial Jackpotโ€‹

Jackpot reset amount after a jackpot win.

Casino Minimum Betโ€‹

Lowest bet amount allowed in casino.

Blackjack Min Betโ€‹

Lowest amount a player may place on a blackjack hand.

Blackjack Max Betโ€‹

Highest amount a player may place on a blackjack hand.

Casino Free Games Per Dayโ€‹

Number of free casino plays each player gets per day. Set to 0 to disable only the daily server free games. Free games are consumed before paid spins and do not count against the paid daily spin limit. Wheel of Fortune bonus free games are separate stored player rewards and can still exist even when this setting is 0.

Wheel of Fortune Spin Limitโ€‹

Maximum number of wheel spins each player can use during the configured interval. Set to 0 to disable free spins. If the Wheel of Fortune Spin Price is also 0, the wheel is disabled entirely.

Wheel of Fortune Spin Intervalโ€‹

Defines when the wheel spin limit resets. Available values are day, week, and month.

Wheel of Fortune Spin Priceโ€‹

Price players pay per spin when they have no free spins remaining. Set to 0 to disable paid spins.

When both the spin limit and spin price are 0, the wheel is fully disabled. When the spin limit is 0 and the spin price is greater than 0, the wheel runs in pay-to-spin only mode โ€” players always pay the configured price per spin without any free spins.

Display odds on Wheel of Fortuneโ€‹

Controls whether the wheel visually exposes the configured prize odds.

When enabled, slice sizes match the configured prize weights. When disabled, all slices use the same visual size so players cannot infer odds from the wheel layout.

Hitman payout (in %)โ€‹

How much bounty value is paid to the killer. Remaining amount stays with server logic.

Minimum bounty amountโ€‹

Minimum value required when players create a bounty.

Integrationsโ€‹

Synchronize player listsโ€‹

Synchronizes restriction (ban), priority, and whitelist lists from dzbot to your game server.

Important behavior:

  • Enabling this makes dzbot your source of truth for those lists.
  • Existing entries on the game server are overwritten.

If you previously managed these lists manually in Nitrado, create/update the corresponding player entries in dzbot before enabling sync.

High-impact side effects to knowโ€‹

  • Changing Subdomain updates your server subdomain mapping.
  • Changing Discord Server triggers a Discord bot installation check.
  • Changing Whitelist enabled or Auto-whitelist linked players triggers a server list sync update job with nitrado (see whitelist).

These are expected behaviors and help keep your server state in sync.