Skip to main content

v3.32.0

A big update: the servers of your organization now share one casino, and you can keep your team in dzbot. New servers decide for themselves whether dzbot takes over cfggameplay.json and the Nitrado player lists, and files in tickets, notes and your books are now private. Plus a free sign-up for the server list alone, and a round of fixes.

Action needed​

  • If your staff should use the new team page without full organization access, grant them the new rights under Organization → Groups: View team, View personal data of the team, Manage team. Groups with full organization access already have them. Docs

One casino for your organization​

Your organization's servers now share one casino: daily limits, spins and free games count across all servers, the slot jackpot is one pool for everyone, and poker tables, the roulette wheel and the voice/chat rooms are shared — players of all your servers sit at the same tables. Docs

Your team in dzbot​

Under Organization → Team every staff member gets a record with role, linked player, contact and bank details for refunds, your own fields (for example a signed team agreement with a "signed on" date and its older versions) and documents of several files each. A member's page also lists the inventory they hold and the expenses that concern them; the inventory holder and manual bookings can now point to a team member. Docs

Good to know​

  • If your organization has more than one server and uses the casino: the casino settings (stakes, limits, rake, timings) are now one set for the whole organization. You still change them in any server's Settings → Casino, and a change applies to every server. Where your servers had different values, the strictest limit any server had set now applies and the other values come from your oldest server; the jackpots of your servers were added up. Docs
  • dzbot no longer switches your server onto cfggameplay.json on its own. New servers move over in the setup wizard's new cfggameplay step, which carries your Nitrado gameplay switches (base and container damage, respawn dialog, personal light, night lighting) into the file so nothing changes in game. Until then the shop, mods and zone spawns can't be set up. Existing servers are already on the file and need to do nothing. Docs
  • If you switch cfggameplay.json off in Nitrado, dzbot no longer turns it back on: shop deliveries and mods pause and the admin area asks you to move over again. Docs
  • New servers start with player list sync off: dzbot no longer takes over the Nitrado ban list, whitelist and priority list on its own. The setup wizard asks who manages them; existing servers keep their setting. Docs
  • Wherever you ban someone, whitelist them or grant priority (web, Discord player card, AI Companion), dzbot now tells you on the spot when that entry won't reach your Nitrado server. The yellow "player list sync is off" banner only appears once dzbot actually holds such entries. Docs
  • Subscriptions keep a history: open a subscription under Admin → Subscriptions → Active and switch to the History tab to see every respawn, pause, cancellation, tier, owner, position and price change — with when and who — next to every billed restart, failed spawn and refund. The AI Companion can read the same history when a player asks what happened to their vehicle. Docs
  • Expenses and incomes have a "Team member" column and filter, and receipt uploads suggest the team member a receipt belongs to. Docs
  • The AI Companion can look up and update team members, hand inventory items to them and link bookings; it reads a member's personal data only after you approve that single read on a card. Docs
  • A player's referral link is the same on all servers that share a Discord server, a new member can link their account on any server of your organization and the referrer is still credited — once per person — and the reward amount is one setting for the organization. Docs
  • During the Pro trial, the admin navigation marks every Pro page with a Pro icon, and each Pro page says at the top how many trial days are left, whether players lose it too afterwards, and that everything set up there is kept. The setup wizard and the billing page say the same. Docs
  • The item editor warns when an item set contains a vehicle: shop orders aren't saved by the game, so a vehicle bought as an item set is gone after the next restart. Sell vehicles as a spawn subscription instead — the AI Companion warns about it too. Docs
  • The AI Companion finds its way through large custom mod files (a big types.xml, object spawner JSON) more reliably before editing them. For MCP clients: grep_custom_mod_files is new, read_custom_mod_file now reads by offset and limit.
  • Server owners who only want to be on the server list can now sign up for that alone, with a short setup and without dzbot changing their server's files or player lists until they switch that on: dzbot.de/dayz-server-listing. Docs
  • Your listing page takes a Discord invite link, so the Discord button shows even without the dzbot bot on your Discord (Admin → Listing). Docs
  • dzbot Support tickets take text files — configs, XML files such as events.xml or types.xml, logs — in the web app and in your ticket channel on Discord, so you can show us your setup directly. Docs
  • dzbot Support answers short things faster: a thank-you or a request for details or files can reach you within minutes, prepared by our AI assistant; every answer about your case and every change to your server is still checked by a person from the dzbot team. Docs
  • Files in dzbot Support tickets arrive in the Discord ticket channels as real attachments instead of links.
  • developers.dzbot.de uses the same top bar as dzbot.de, so moving between the platform, the server list, the map, the wiki and the developer docs feels like one site; the server list's logo reads DZSERVERS.

Fixed​

  • Ticket and note attachments, receipts, invoices and inventory documents could be opened by anyone who had the file's link, without logging in. They are now only shown inside dzbot to people who are allowed to see the page they belong to; old links to such files no longer open.
  • Players could see files the team attached to internal notes in their ticket. Those files now stay with the team.
  • Orders on a server that doesn't load cfggameplay.json are no longer marked delivered without ever spawning.
  • A cancelled spawn subscription billed per restart now shows as "Ended" with its end date on the subscriptions page. Before, it kept saying "Active" with the pause and respawn buttons, so the cancel looked like it had not worked — it had, nothing was charged after it.
  • The subscriptions page no longer crashes for players with a monthly subscription that has been through a restart.
  • A timed Discord role, for example from a subscription, is no longer removed when it runs out on one server while a subscription on another server sharing the Discord server still pays for it, and it no longer runs two timers.
  • Files you post in your dzbot Support ticket channel on Discord reach our team reliably; a file we cannot take (too large, unsupported type) is no longer dropped without anyone noticing.
  • The docs no longer say that vehicles bought in the shop survive a vehicle wipe — that applies to vehicles from spawn subscriptions. Docs