Skip to main content

AI Companion — Usage

This page explains how to work with the AI Companion day to day, and gives you an idea of everything it can help with. If it isn't switched on yet, see AI Companion setup first. For the underlying ideas (modes, proposals, sessions, page awareness), see the AI Companion concept.

Opening the Companion​

Click the AI Companion button (the sparkles icon) in the top-right of the admin header. A panel slides in from the right.

On a ticket page you'll also find two shortcuts that open the Companion already focused on that ticket:

  • an Ask the Companion prompt on the ticket's Investigation tab, and
  • an "Unsure how to answer? Let AI do the talking" link next to the reply box.

From Discord​

You do not have to be in the panel at all. /ai starts a session from Discord: the bot opens a private thread and the conversation continues there, with the same cards and the same Approve, Reject and Reject with comment buttons. A Discord session starts in your default mode (see Ask or Execute); there is no switch in Discord. The thread is renamed from your first message like any other session, and a button closes it when you are done.

Give the command a prompt directly, or send it empty and the bot opens a small window for a longer one. Started inside a ticket channel, the session is about that ticket.

The Discord dossiers have a shortcut too: an order, a faction, a bounty, a bet, an event, a base alarm, a booking from /org, the rules and the player card each show an 🤖 Ask AI button if you may use the Companion. It asks for your question and starts the private thread already focused on what the dossier shows.

Sessions​

The Companion organises your work into sessions, like a chat history:

  • The button opens a list with Open and Archived tabs and a + New session button.
  • Each session is private to you, named automatically from your first message, and renamable.
  • Continue later closes the panel but keeps the session in your open list.
  • End session marks a session as done and moves it to the Archived tab.
  • The panel only closes through one of these two buttons. Clicking next to it or pressing Escape highlights them instead, so a conversation is never left behind by accident.
  • An open session is part of the page address, so reloading the page or sharing the link opens it again.
  • Sessions are kept for 12 months after their last activity, so you (and admins) can look back at what was asked and approved.
  • A session you don't touch for 7 days is archived for you. If it lives in a Discord thread, that thread is deleted along with it — the transcript stays in the Archived tab until it is deleted 12 months after the last activity.

Keep one session per task. A session's focus is fixed when you create it, so when you move on to a different player or ticket, start a fresh session rather than reusing an old one.

Talking to it​

Type what you need in plain language and press Enter (use Shift+Enter for a new line). You can write in German or English — for player-facing replies it will match the player's language.

A turn takes a few seconds to up to a minute, since the Companion may look up several things before answering. You watch it happen: a Working box lists every lookup as it runs, along with any notes the Companion makes on the way, and the answer is written out word by word below it. Once the turn is done the box folds into a short line such as "3 steps · 2 tools" — click it to see the path again.

You can keep typing while it works, but the next message is sent only once the turn is done.

If you asked the wrong thing, or it is clearly heading somewhere you did not intend, press Stop next to the message box instead of waiting it out. Stopping ends the work; whatever it had already written and proposed stays, and proposals are still yours to approve or reject.

Voice messages​

Rather talk than type? Press the microphone in the corner of the message box. It spins until your browser has the microphone ready — the first time, the browser asks for access — then a counter shows the seconds; start talking. Press the counter to stop. The recording is turned into text and lands in the message box, so you can fix a misheard player name before you press Enter. A recording can be up to 3 minutes long and stops on its own when the time is up.

In Discord, send a voice message in your companion thread, or as a reply to one of the Companion's answers. It reads the voice message and answers it directly — the recognized text is not posted, but you can read it in the session's transcript in the web app. Voice messages longer than 3 minutes are declined.

Turning speech into text is paid from the AI credit like everything else the Companion does — well under a cent per minute. The recording itself is not stored.

Ask or Execute​

Every session has a mode. Switch it under the message box with Ask / Execute:

  • Ask (the default) — every change the Companion wants to make waits as a card until you approve or reject it. Nothing is written before you decide.
  • Execute — changes run straight away. The chat still shows a card for every change, marked Executed, so you see exactly what was written and can have it corrected.

Lookups never wait for anything: reading data always runs immediately, in both modes. The mode applies to every kind of change alike — there are no changes that skip approval in Ask mode.

You also have a default mode for new sessions. When the current session's mode differs from your default, a Use for new sessions button appears next to the switch and makes it your default. Discord sessions (/ai threads and mentions) start in your default mode, so set it in the panel if you want Discord to execute directly.

Efficient or Smart​

Next to the mode you choose how capable the Companion should be in this session:

  • Efficient (the default) — fast and inexpensive; enough for most questions and actions.
  • Smart — noticeably more capable for tricky cases, accounting questions and long investigations, but each message costs considerably more of your AI credit. The ? next to the switch shows the current factor (about 20× as much as Efficient).

You can switch at any time; it applies from your next message. Use for new sessions stores your choice of mode and model as the default for new sessions, which Discord sessions use too.

Cards​

Every change appears as the same kind of card:

  • a title saying what will happen (or happened),
  • the fields that matter — for a change, the old value next to the new one,
  • the full text of a message, reply or note,
  • the code of a script,
  • a diff for rewritten texts such as rules, custom pages or mod files,
  • a link to the affected player, faction, ticket or other object, so you can double-check it.

Destructive changes — deleting something, banning someone, paying money out — are marked as such. Each card shows its status: Pending, Approved, Executed, Rejected or Failed.

A single answer can include several cards (for example a reply and an internal note, or two alternative replies). In Ask mode you decide each one separately:

  • Approve — carries the change out now, using the same logic as the normal admin pages.
  • Reject — discards it.
  • Reject with comment — discards it and sends your comment to the Companion as your next message. It drafts a corrected proposal right away. In Discord this is a third button that opens a small form.

Approving runs the change as you, with your rights, against how things stand at that moment. If what the card was based on has changed in the meantime — say someone edited the rules by hand — approving fails instead of overwriting that change. Ask the Companion for a new proposal.

There is no inline editing: to change a proposal, reject it with a comment or simply tell the Companion what to change. An admin looking at someone else's session on the Companion Sessions page can also reject with a comment; the comment is kept on the card, but it is not sent to the Companion on the owner's behalf.

Waiting for something​

Some things take time: an emote you just made in game reaches dzbot only once Nitrado hands over the server's log file — usually 5–15 minutes later — and a player may answer a ticket tomorrow. Instead of making you ask again and again, the Companion can wait for it and get back to you on its own.

Ask it in plain words — "tell me when my thumbs-up arrives", "let me know when SkEiTa1337 answers the ticket", "check the payout once the next kill comes in". It sets up a watcher: what it waits for and for how long (30 minutes unless it picks otherwise, at most 7 days). It can wait for:

  • game log events (a kill, an emote, a player connecting …),
  • an action running (successfully or with an error),
  • tickets (new, a new message from the player or the team, a status change),
  • orders (new, delivered, delivery taken back, refunded, cancelled),
  • reviews (opened, resolved),
  • wallet transactions.

While it waits, a strip above the message field shows each watcher with the time left; ✕ stops one. When the event arrives, the Companion continues the session by itself — its answer is marked Watcher fired and shows the event. If nothing arrives in time it says so (marked Timed out) and offers Another 30 min; for things where silence means nothing it may stop without a message.

You do not have to keep the Companion open. If it wakes up while you are elsewhere in the admin area, a notice pops up and the search field gets a small marker until you open the session; the session list shows Waiting and New. In Discord the answer arrives in the session's thread or channel.

A wake-up is an ordinary turn: it uses your AI credit once (waiting itself is free) and follows the session's mode — in Execute mode the Companion may carry out what you asked it to do once the event arrives. Without credit no turn runs; the watcher ends with No credit. Ending the session stops its watchers; writing a new message does not. At most 5 watchers wait per session and 50 per organization.

What the Companion can help with​

You don't need to learn any commands — just describe your goal. Below are the areas it understands today, to give you a sense of what's possible. Think of these as inspiration, not a fixed menu.

Support tickets

  • Open a new ticket with a player to start a conversation, with the opening message drafted for you.
  • Rewrite your rough notes into a calm, professional reply to a player.
  • Read the whole ticket conversation and summarise what the case is about.
  • Draft an internal, staff-only note on a ticket.
  • Pull in another ticket you remember that's relevant to the current case.
  • Manage the ticket itself: close, reopen or archive it, or move it to another support level — each drafted as a proposal you approve.
  • Work the ticket queue like the list page: "my open tickets", unassigned ones, a level or category, or a player's tickets — sorted by urgency or newest.
  • Assign or unassign a ticket, add a player or a whole faction as participants or remove one, rename it, request a response from the participants, mark who answers next, edit, delete or pin a message, repair its Discord channel, attach it to a review, or delete an archived ticket — each drafted as a proposal you approve.
  • Show what is pinned to a ticket as evidence, its saved log queries and the player and faction notes linked to it, and remove pins or queries that no longer belong.

Investigations

  • Search the game logs for kills, deaths, connections, building, money transfers and more, within a time range or around a location.
  • Correlate what players and factions were doing, and summarise the findings.
  • Check your server rules and judge a case against the actual wording.
  • Pin a relevant log event to a ticket as evidence.

Players

  • Find players by any criterion and rank them: who joined first, who is richest, who has more than a given balance, who has not played since a date, who is online right now, who was most active in a period — filtered by faction, access group, whitelist or ban status.
  • Look up a player's profile: identities, faction, balance, ban and whitelist status, last known position, linked Discord.
  • Check and adjust a player's balance (give, remove, or set an amount, with a reason). A player's wallet balance is org-wide — one balance shared across every server in the organization.
  • Search the transaction history of a player, a faction or the whole server — by period, category, text or amount — with totals and rankings, e.g. "who won the most at the casino this week?" or "what did this faction spend in September?".
  • Ban a player, add or remove them from the whitelist, or clear a player's claim block.
  • List a player's active bans in detail (reason, expiry, scope) and lift one — the ban is ended, never deleted, so the moderation record stays.
  • Check a player's linked accounts (detected via shared devices), including each account's ban status and any open multi-account reviews.
  • Summarise player activity over a period — session count, total playtime, last online — for one player or a whole list at once (e.g. "which faction members still play?").
  • Unlink a player's connected user account (their Discord/website login), so a different account can be linked afterwards.
  • Switch a player's main account to one of their device-linked accounts, with the balance carried over (see Switching the main account).
  • Merge two player records on the same server that belong to the same person. If both logged the same event at the same moment, the proposal says so in a warning — that usually means two different people.
  • Leave an internal note on a player.
  • Send a player a Discord DM, or grant/remove a Discord role.
  • Find out why a player cannot see a Discord channel: whether they are on your Discord server at all, which roles they have, which of dzbot's own roles are missing and why (not linked, rules not accepted, banned), and which role would unlock each hidden channel. This is checked live in Discord.
  • Read and edit a player's notes (text, tags, expiry, linked ticket) or delete a note written by mistake.
  • Edit a player's profile — display name, username, profile note — and their groups and individual access rights.
  • Set or delete player variables, disconnect a wrongly matched device, link a user account to a player that has none, or create a player record for someone who has not joined yet.

Factions

  • Look up a faction's details, members, and balance.
  • Review a faction's treasury history and adjust its balance.
  • Leave an internal note on a faction.
  • Look up a faction's details: members and their faction rights, staff notes, item spawns, base alarms, subscriptions and — with the right — its treasury and the members' alt accounts.
  • Review a faction's treasury history and adjust its balance.
  • Create a faction or change its name, colour, tag, flag or armband; delete a faction.
  • Add a player to a faction, remove them, or change their faction rights.
  • Review alliances, their open votes and the kills and hits between allies; found or rename an alliance, or act for a faction in one — invite, propose a removal, vote, withdraw or leave. The alliance's votes still apply.
  • Add, change or remove a faction's item spawns.
  • Leave an internal note on a faction (with tags and an expiry), edit or delete one.

Accounting

  • Answer questions about your accounting the way the Accounting page would: this month's and this year's income, expenses and result, the monthly trend, totals per category.
  • Evaluate it further than the page does: costs and income per server, top donors, VAT in a period, how hosting costs developed — any total over any period, grouped by month, category, server, player or vendor.
  • Look up single entries in full — line items, VAT, the fees of a donation, refunds, attached receipt names — and the inventory, including book values and what was disposed of.
  • Check whether a donation reward was paid. The Companion matches each payment to the reward it triggered, spots a payment that arrived but never triggered your donation actions, and drafts the missing payout for you to approve.
  • Record a support payment that came by PayPal, bank transfer or cash, after checking it is not booked yet — with your donation actions paying the usual reward — and reverse a manual payment that was booked by mistake.
  • Issue and cancel invoices for income entries (it asks you for the recipient's name and address when the amount needs them), and turn uploaded receipt photos and PDFs into expense drafts, or discard an upload.
  • Change your donation page text.
  • It cannot book, edit or refund other entries, refund Stripe payments or change the inventory. Reading needs the accounting view right; recording support payments the record right; invoices, receipts and the donation text the accounting/monetization manage rights (on the server or the organization).

Shop and orders

  • Find a player's orders and inspect what was bought and delivered.
  • Refund an order, or re-deliver items a player paid for but didn't receive.
  • Gift a player items for free — either a ready-made shop kit or specific items.

Bases and territory

  • Locate a player's or faction's base for a raid, by combining base alarms, recent building activity, and detected bases — so you don't have to hunt down coordinates yourself.
  • Locate a player's or faction's base for a raid, by combining base alarms, recent building activity, and detected bases — so you don't have to hunt down coordinates yourself.
  • Browse the detected bases like the Bases page — by size, decay status or the clean-up queue — and look one up in full.
  • Rename a base, record an on-site check ("still standing" or "gone"), or delete a wrongly detected base.
  • Find base alarms by code, owner, faction, date or location; place a new alarm, change one (position, radius, price, owner, faction, extra players, Discord channel, active) or delete it.

Leaderboard, casino and bounties

  • Read the current leaderboard standings for any category and period.
  • Diagnose why a player is missing from the leaderboard — usually a ban on one of their linked accounts — and draft the fix.
  • Explain how the casino works (games, access rights, free games, spin limits) and where casino access is granted.
  • Explain the bounty system (placement, payouts, the hitman cut, linked-account targeting) and route bounty automations to actions or the scheduler.

Server rules

  • Read the current rules and quote the exact wording relevant to a case.
  • Update the rules for you — reword a rule, add or remove one, or rewrite the whole ruleset. The change is drafted as a proposal showing the exact diff, and an approved change lands in the rules history like a manual edit.
  • Keep your language versions in sync. Rules are written per language, and the Companion sees all of them: when you ask for a new rule it writes it in every language you maintain — and it can add a language version that does not exist yet. All languages travel in one proposal, so you approve the change as a whole.
  • Publish the updated rules to your Discord rules channel afterwards (also as a proposal you approve).

Server settings

  • Look up how your server is configured — the same options you edit on the Settings page — and explain where a given behaviour is controlled instead of you hunting for it.
  • Change a setting for you — for example, remove a flag from the pool players can pick when founding a faction (the "available flags"), or adjust another General, Access, Economy or Discord option. The change is drafted as a proposal showing the old and new value, which you approve. Credential and organization-level settings are off-limits to the Companion.

Custom pages

  • Read one of your custom info pages — just paste its link (e.g. .../pages/trader) or name the page, and the Companion reads its content.
  • Edit an existing page for you — reword or restructure its content, or change its navigation title, headline, subheadline or icon. The change is drafted as a proposal showing the exact diff, which you approve.
  • Keep your language versions in sync. Page text is written per language, and the Companion sees all of them: a change is applied to every language you maintain, in a single proposal.
  • Creating or deleting pages, and changing who can see a page (its visibility), stay in the admin Pages screen — the Companion doesn't do those.

Discord

  • Read a Discord message or a channel's recent messages from your linked Discord server — just paste a Discord link, or reference a channel, and the Companion reads it back to you. This is read-only; the Companion never posts, edits or deletes anything in Discord here.
  • It can only read channels in your own linked Discord server, never another community's.

Zones

  • List the map zones on your server and what each one enforces (no-build, no-kills, linked-only).
  • Check which zones a coordinate falls inside — e.g. whether a kill or a build event happened in a managed zone — so you can judge a case against the right zone policy.
  • List the map zones on your server and what each one enforces (no-build, no-kills, linked-only), and look up a zone's whitelist, ignored groups and map display.
  • Check which zones a coordinate falls inside — e.g. whether a kill or a build event happened in a managed zone — so you can judge a case against the right zone policy.
  • Create, change or delete a zone: name, shape, policies, whitelisted players and ignored groups, and how it shows on the public map.

Actions (automations)

  • Explain how actions work and help you design one from a plain-language goal ("reward players for killing zombies", "alert Discord on a donation").
  • Write the complete Lua script for you, using the correct event data, functions and config fields — and check that it compiles before proposing it.
  • Create, edit or delete a custom action, all as proposals you approve; the proposed script is shown in full on the card so you can read it first.
  • Search the action marketplace and install a ready-made action, or uninstall one you no longer want.
  • Enable or disable an action.
  • Read an existing action's script, configuration and recent run logs to help you work out why it isn't behaving as expected.

Scheduler (time-based automations)

  • Explain the difference between actions (which fire on a game event) and scheduled tasks (which run on a clock), and help you set up the right one from a plain-language goal ("post the active bounties to Discord every day at 20:00", "restart the server every night", "wipe vehicles weekly").
  • Build the schedule for you — one-off at a set time, or recurring (hourly, daily, weekly, monthly) — without you needing to know any cron syntax.
  • For a recurring job built from live data (like a daily bounty post), write the underlying action script for it too.
  • Create, edit or delete a scheduled task, all as proposals you approve.
  • Pause or resume a scheduled task.
  • Read an existing scheduled task's configuration and recent run logs to help you work out why it didn't run as expected.

Restrictions

  • Search all restrictions on the server — bans, claim blocks and event restrictions — by status, kind, player, faction or ticket, including ones that reach a player through an alt account and ones that were deleted.
  • Open a restriction with its targets, automatic actions, linked tickets, violations and full history.
  • Extend or shorten a restriction, move its start or make it org-wide; end any restriction with a reason; put an alt under the same ban or take someone off; link or unlink tickets; delete a restriction created by mistake once it no longer holds anyone.

Ticket setup

  • Create and edit ticket categories, including their texts per language and the intake form, reorder or delete them, and post, remove or rebuild their Discord panels.
  • Create, rename, reorder, dissolve or repair support levels (Discord category and role) — proposals you approve. Reordering or dissolving levels changes who sees which tickets, so it needs access to every level.

Events and achievements

  • Find events and look one up in full: settings, prize table, participants and teams, the bracket with every match and result, points standings, final placements, and the payout preview of a finished event.
  • Set up an event in plain language ("a 1v1 boxing tournament on Friday at 20:00, 500 entry fee, the winner gets 70 % of the pot"), also from one of your templates, or change an existing one. Publish it, close registration, cancel it, close it and pay out the prizes, each as a proposal you approve.
  • Run the event day: enter or remove participants, check them in, group solo players into a team, draw a phase (the proposal shows the exact pairings), start matches, enter results, open a bet on a match, award or remove points, and close or reset a phase.
  • Create, change and delete event templates, including saving an existing event as a template.
  • Read achievements and seasons and see who has made how much progress. Create or change an achievement, conditions and rewards included, raise a player's progress on a manual condition, and create, copy or delete seasons. Replacing an achievement's conditions resets everyone's progress on it, and the proposal says how many players that affects.

Oversight and investigation

  • Answer "who changed what" from the audit trail: who changed a setting, who banned or unbanned a player, what a staff member did on a given evening — filtered by player, field, action or time, for this server or the whole organization.
  • Work the review queue: list and open multi-account, fresh-account and account-sharing reviews with their evidence and history, and propose claiming, commenting, closing with a note (optionally accepting the combination), opening a ticket from a review or revoking an accepted combination.
  • List, file and decide log requests (approve, optionally narrowed, or reject with a note to the requester).
  • Read the game-server audit (errors the game logs about types.xml, events and spawner files) and the Discord audit (missing channel permissions), and propose marking entries as fixed or ignored.
  • Summarise the dashboard: players online, the last 7 days (active and new players, retention, playtime, shop, PvP, money flow, busy hours), orders, tickets per status and supporter, casino figures for the last 24 hours, 7 or 30 days.

Shop, coupons and casino

  • Find, create, change or delete shop kits and shop categories: price, items, whether a kit is for sale, which player groups may buy or see it, and order limits.
  • Look up coupons with their conditions and recent redemptions, and create, change, pause or delete them.
  • Manage the wheel of fortune: see every prize with its win chance, add, change or remove prizes, and mark custom wins as handed out.
  • Run bookmaker bets: list bets with every stake, start a bet, close, settle or cancel one, hand it to another bookmaker, or refund a single stake. Before you approve a settlement, the card shows how much will be paid out.
  • List bounties and refund an open one to the player who placed it.

Mods

  • See which marketplace mods are installed (with their configurations, versions, auto-update and recent transfer errors) and browse the marketplace mods available for your map.
  • Install, update, uninstall or remove a mod, change the settings of one of its configurations or add another configuration, switch automatic updates on or off, change the load order, or push all mods to the game server right away — each drafted as a proposal you approve. Paid mods still have to be bought in the Mods screen.
  • Read your custom mods, their files and config, and search inside a file even when it is very large.
  • Create, rename, switch off, give an expiry date to or delete a custom mod; add, edit or delete its files (targeted edits, shown to you as a diff before you approve), its config fields and its config values.

Access rights and organization

  • See which access groups exist on the server and in the organization, what each one allows or denies, and who is in it — or which groups one player belongs to.
  • Add a player to a group or remove them (how someone gets or loses a staff role), create, rename or delete groups, and change individual rights of a group or of one person's organization rights. The proposal card lists every right that changes, from what to what; if any of those rights was changed in the meantime, approving fails instead of overwriting it.
  • Look up a person at the organization level: their accounts on every server, organization rights and groups, org-wide restrictions and balance.
  • Check the organization's servers at a glance — subscription state, players online, log activity and health warnings such as a lost Nitrado link.
  • Work through the organization's linked-accounts list (accounts sharing a browser or an internet address).
  • Read and change organization-wide settings such as the organization name, currency, tax rate or invoice details.

Referrals

  • Show each player's invite with its uses, credited joins and rewards, and the joins nobody could attribute.
  • Credit an unattributed join to an invite or dismiss it, and link a credited join to the game account the newcomer plays — which pays the referrer the referral reward.

Spawn subscriptions

  • Find booked subscriptions by code, owner, item or status, and list the offers players can buy.
  • Book, change, pause, delete or respawn a subscription, and create, change or delete an offer.

This documentation

  • Answer "how does X work" and "where do I set that up" from this manual instead of from guesswork, and link the page it took the answer from so you can read on.
  • Find the right page when you don't know what a feature is called — describe what you want to achieve and let it look.
  • Read a whole documentation page and summarise it, or apply it to your situation ("what does this mean for my server?").

Wherever the lists above say "proposal you approve", that is Ask mode: everything that changes data waits for your approval, without exception. In Execute mode the same changes run straight away and each one shows up as an Executed card.

Good habits​

  • Be specific. "Refund order 4821 because the trader was offline" works better than "fix this order".
  • One task per session. Start fresh sessions for new cases.
  • Let it do the lookups. You usually don't need to paste IDs — describe the player or ticket and it will find them.
  • Read every card. In Ask mode before you approve it, in Execute mode right after it ran. The Companion is a strong drafter, but you make the call.

Limits​

  • The Companion takes a limited number of steps per turn. When it runs out, it answers with what it found so far and what is still open; reply "continue" and it carries on.
  • Only one turn runs at a time per session. You can stop a running one rather than wait for it.
  • Word-by-word answers appear in the panel. In Discord the answer arrives as one message when the turn is done.
  • It sees exactly what you see. On a server with ticket support levels, a ticket in a level you do not hold stays invisible to the Companion too — it will report that it cannot find it rather than reading it out to you.

Tell us what you need next​

The Companion is focused on ticket support today and we are steadily expanding what it can do across the platform. We'd love to hear your use cases and feature requests — tell us what you'd want it to handle next on our Discord.