Skip to main content

What changes after setup

Setup is done. Before you run your server, these are the most important things that now work differently.

Restarts must go through dzbot​

This is the most critical change. Shop order delivery, subscription cycles, and mod file deployment all happen during dzbot-managed restarts. If you restart your server outside of dzbot — through Nitrado, another bot, or direct game panel controls — those hooks do not run.

What breaks with external restarts:

  • Shop orders stay pending or get delivered twice, because items are not cleared before the next restart cycle
  • Installed mods may end up in an inconsistent state

Action required: Disable every automatic restart routine you currently have — Nitrado's built-in scheduler, other bots, scripts. Set up your restart schedule in the dzbot Scheduler instead.

Mod-managed files regenerate on every restart​

If you use mods, dzbot writes to your server files on every restart. These writes build on a saved baseline — not on your last manual edit. Any change you make directly to a managed file gets overwritten the next time the server restarts.

What to do instead:

  • Use a custom mod for any file changes you need
  • If you must edit a managed file directly, make the change in the .original baseline file, not the generated output file
  • Never delete .original files — dzbot uses them to restore state on uninstall

See File changes for how the .original model works.

Player lists are managed in dzbot, not Nitrado​

With player list synchronization enabled, dzbot overwrites the Nitrado whitelist, ban list, and priority list on every sync. Any changes you make directly in Nitrado will be overwritten.

Manage all player access in dzbot — whitelisting in Players, bans in Restrictions, and access rights in Groups.

Players access shop features after linking their in-game account via Discord login. A player who says "I can't see anything" typically hasn't linked yet.

The process: players open your server's dzbot page, log in with Discord, and claim their in-game username. Log imports have a 10–20 minute delay (up to 60 minutes under load), so balance and position may not appear immediately after linking — this is expected.

See Player onboarding and Logs import.