Skip to main content

Discord commands

Players can do most everyday things right in Discord, without opening the app: check their balance, send money, look at orders, bet, place bounties, run their faction, switch base alarms and sign up for events. This page lists every command, what players can do with it and which extra buttons staff get.

How the commands work​

One command per area. Instead of dozens of commands, each area has one — /bank, /bet, /faction and so on. It opens a card (a "dossier"), and everything else happens through the buttons on it.

Only you see the answers. Every answer is private: nobody else in the channel sees your balance, your bets or your faction. You can use the commands in any channel of the server's Discord. They do not work in direct messages with the bot. The one exception is /logs, which opens a private thread.

Overview first, details on click. Commands like /bet or /places first show a list. Each entry has a button that opens its own card with the details and actions. If there are more than 20 entries, the buttons disappear and the card tells you to type the command with the entry's code instead.

Every entry has a short code. Bets, bounties, factions, orders, places, base alarms and events each carry a four-character code, shown in front of the entry and at the bottom of its card — for example K7QX. Type it after the command to open that entry straight away: /bet K7QX. Codes never contain 0, O, 1, I or L, so they cannot be misread; upper or lower case and a leading # do not matter. A code only works on its own server.

Money and deletions ask first. Before money moves (sending, paying in, withdrawing, settling a bet, paying an entry fee) or something is deleted or withdrawn, a confirmation card shows exactly what will happen. Nothing changes until you press the confirm button; Cancel or Back leaves everything as it was.

Typing amounts. Amounts are whole numbers. 5000, 5.000 and 5 000 all mean five thousand; 5k means five thousand, 1.5k one thousand five hundred and 2m two million. Anything that is not a whole number, like 5,5, is refused.

Times are shown in your own timezone, and the texts follow your Discord language (English or German).

Who may do what​

The commands check the same rights as the web app, from the groups of the player your Discord account is linked to. Discord roles and Discord permissions play no part: every member sees every player command, and the bot decides when you use it. A button you have no right for is not shown at all.

  • Link your account first. Almost everything needs your Discord account linked to your in-game player on that server — see /link. Without it, the bot tells you to link first. /event (browsing) and /rules also work unlinked.
  • Banned players lose everything except tickets, exactly as in the web app.
  • Platform administrators pass every check.

Several game servers on one Discord​

When a Discord is shared by several dzbot servers, the channel decides: a command answers for the server that owns the channel's category, and channels nobody claimed belong to the main server (see Multiple game servers in one Discord guild). Which server you play on does not matter. If you use a command in a channel of a server where you have no player, the bot tells you which server's channels to use instead.

/link name:<your in-game name> connects your Discord account to your in-game player — the same as claiming your account on the website. You do not need to have logged into the website before.

  • The name has to match your in-game name exactly.
  • If linking is turned off on the server, the player is already linked to someone else, or linking is blocked (for example because of a ban or a shared device), the bot says so. The reasons are the same as on the website — see Player onboarding.
  • If you are already linked, the bot tells you to whom.

There is no /unlink, just as there is no unlink on the website.

/bank​

Your balance and the treasuries of your factions.

  • Your balance is always shown.
  • Send money (needs player.shop_profile.give_money): enter the recipient's in-game name and the amount. Part of the name is enough, and the search covers every server of the organization. If the name matches one player exactly, that player is taken; if several match, you pick from a list (most recently online first, with the date they were last seen). The confirmation card names the recipient and warns when they have not linked an account. A transfer cannot be undone.
  • Transactions (needs player.shop_profile.see_transactions): your ten latest bookings.
  • Faction treasuries: every faction in which you may pay in or withdraw shows its balance, with a button for its ten latest bookings. Paying in and withdrawing happen in /faction.
  • Open in app leads to the full transactions page.

/shop​

The entry to the shop: your balance and your latest order, with buttons to Open shop, My orders (/orders), Manage places (/places, if you may use places) and — if you have any — your Subscriptions in the app. Needs player.shop.access.

Ordering itself stays on the website: the cart, delivery times and coupons do not fit into Discord.

/orders​

Your shop orders (needs player.shop.access).

  • /orders shows your latest order: status, total, items, refunds, when it was delivered or when it is expected (with the restart time), and the delivery location with an iZurvive link. If a faction paid, that is shown too.
  • More orders lists your 20 latest orders — the ones placed for you or by you. Each opens its own card.
  • /orders <code> opens one order directly. That also works for orders your faction paid for, if you may order for the faction.
  • New order in the shop and Open in app lead to the website. Cancelling an order is only possible there — see Shop system.

Staff with admin.orders.view also get:

  • All orders on the /orders card: the server's 20 latest orders, one line each with code, player, total, status and date. Staff who do not play on the server get this list straight away.
  • The Orders button on the player card: the same list for one player.
  • /orders <code> opens any order of the server, with the player's name, who placed it and the paying faction. Open in app leads to the order in the admin area. Refunds, redeliveries and changes stay in the app.

/places​

Your saved delivery places (needs player.places.access). Only your own places appear here; faction places are shown read-only in /faction and managed in the app.

  • The overview lists each place with its location on the map.
  • Save a place: give it a name and a position. Type the position as x z (for example 7500 8200), x, z, the in-game format <x, y, z> or iZurvive's x / z; a whole iZurvive link works too. Decimals use a dot, or a comma when something else separates the numbers (7500,5 / 8200,5). Leave the position empty to take the spot of your last emote in-game — do an emote where you are standing, then save.
  • A place's card shows its coordinates, an iZurvive link and the buttons Rename and Delete. Deleting asks first; orders and subscriptions that used the place keep their position.

More on places: Saved places.

/bet​

The server's bets — the bookmaker, which in the app lives under Casino → Bookmaker. Needs player.bookmaker.access, or admin.bookmaker.cancel for staff.

Players

  • The overview shows all running bets and the five latest settled ones. Open bets are highlighted.
  • A bet's card shows its outcomes, deadline, bookmaker and allowed stake. Whether the money on each outcome is shown depends on the bet — the same as on the website.
  • Bet on … — one button per outcome — asks for your stake. Your own stakes are listed on the card.
  • Refresh redraws the card with the latest numbers.

Starting a bet (needs player.bookmaker.create, or admin.bookmaker.cancel): Start a bet asks for a title, the outcomes (one per line, at least two), an optional deadline, optional stake limits like 100-5000 and an optional description. The deadline is either a duration from now (2d, 12h, 1d6h, 90m) or a date and time in the server's timezone (2026-09-30 20:00 or 30.09.2026 20:00). You become the bet's bookmaker.

Bookmakers (on their own bets) and staff with admin.bookmaker.cancel (on every bet) get:

  • Close betting — no new stakes; the bet waits for its result.
  • Settle — pick the winning outcome, confirm, and the pot is paid out immediately.
  • Cancel bet — confirm, and every stake is refunded.
  • Extend deadline — only the bookmaker, and only while the bet is open.

/bounty​

Bounties (needs player.bounties.access). See also Bounties.

  • Hitmen (player.hitman.access) and players who may cancel every bounty (player.shop.cancel_all_bounties) see all open bounties. A bounty's card also shows every account of the target with its last known position and an iZurvive link — for a bounty on a faction, every member.
  • Everyone else sees only the bounties they placed themselves.
  • Place a bounty: the target's exact in-game name, the amount and an optional reason. The money is taken from your balance right away. A bounty placed from Discord always covers all known accounts of the target; the website lets you choose "this account only" instead. Discord also has no switch to let faction mates and allies of the target collect: they never collect a bounty placed here, and a bounty on a player or faction allied with yours has to be placed in the app (see Allies and faction mates).
  • Bounty on a faction: the faction's name or tag, the amount and an optional reason. Whoever first kills any member collects it; you cannot place one on your own faction or one allied with it.
  • Withdraw — for whoever placed the bounty, and for players with player.shop.cancel_all_bounties on any bounty. It asks first, then refunds the person who placed it. Withdrawing someone else's bounty is recorded in the audit trail.

/faction​

Your faction and every other faction of the server (needs player.factions.access). See also Factions.

  • If you are in exactly one faction, /faction opens it directly, with an All factions button; otherwise you get the list of every faction on the server, yours first.
  • Someone else's faction opens as a short card with only its members, leaders and allies — what the faction list in the app shows everyone. Notes, treasury, base alarms and places stay with the members.
  • Staff with admin.factions.access open every faction in full.
  • The card shows the members and their faction rights, and — depending on your own faction rights — the treasury, the faction's base alarms and its places, the same way the faction page does.

What the buttons need (faction rights are the ones set per member inside the faction):

ButtonWho gets it
Depositmembers with the faction right Deposit; staff with admin.factions.access on factions they are not a member of
Withdrawmembers with the faction right Withdraw; staff with admin.factions.access on factions they are not a member of
Transactionsmembers with Deposit or Withdraw; staff with admin.factions.access
Invite member / Remove membermembers with Edit details; staff with admin.factions.access or admin.factions.edit_members
Member rightsmembers with Manage members; staff with admin.factions.access or admin.factions.edit_members
Alliancesevery member while the server allows alliances; founding, voting, leaving and withdrawing need Alliances (or faction admin); staff with admin.factions.access
Orders (opens the app)members with Order, Deposit or Withdraw; staff with admin.factions.access
🔔 alarm buttonsmembers with Base alarms, staff with admin.factions.access — if they may also use /base-alarm, where the buttons lead
Leaveevery member
  • Deposit and Withdraw move money between your own balance and the treasury and ask first. That also applies to staff: a withdrawal lands on the balance of whoever pressed the button.
  • Invite member needs the player's in-game name; the player must have linked an account and must not be in another faction. They get a DM with Accept and Decline and only join once they accept — see invites.
  • Member rights: pick a member, then tick the rights they should have and close the menu to save. Emptying the list takes all rights away. The server's limit on faction leaders still applies.
  • Alliances lists your faction's alliances and the open votes. With the right, buttons agree to or decline an invitation or vote, a menu founds a new alliance with one other faction — named "A & B" unless you choose another name — and a second menu leaves an alliance or withdraws a proposal of your own. Inviting a faction into an existing alliance, proposing a removal and renaming stay in the app. Each invitation and vote also arrives as a DM with buttons to answer right there — see Alliances.
  • Leave asks first. If you are the only faction admin, you pick who takes over first. If you are the last member, leaving dissolves the faction for good and pays what is left in the treasury out to you.

Founding a faction, and changing its name, flag, armband, places, subscriptions and ranks, stay in the app. Members show their rank in the card.

/base-alarm​

Your base alarms (needs player.base_alarm.access). See also Base alarms.

  • The overview lists the alarms you own. Faction alarms are reached from /faction; an alarm you are only notified by can be opened with its code.
  • An alarm's card shows whether it is on, its position, radius, price and payment state, the owner or faction, who else is notified, where alarms are delivered (direct message or channel), and who was near the base in the last 30 days — everyone the alarm protects left out.
  • Switch on / Switch off — for personal alarms everyone who sees the alarm; for faction alarms members with the faction right Base alarms, and staff with admin.base_alarm.edit.
  • Mute for me / Unmute — only for you; everyone who sees the alarm can mute it.
  • Delete (needs player.base_alarm.delete) — the owner of a personal alarm, or members with the faction right Base alarms for a faction alarm. Asks first and cannot be undone.

Creating an alarm and changing its position or recipients stay in the app, where the map is. Staff with admin.base_alarm.edit can open and switch any alarm of the server by its code (they need player.base_alarm.access too, like everyone using /base-alarm). Deleting other players' alarms is not possible from Discord.

/event​

The server's events (see Events). Anyone on the Discord can look, even without a linked account.

Players

  • The overview shows running events, upcoming ones and the five latest finished ones. Events still taking registrations are highlighted.
  • An event's card shows status, mode, entry fee, schedule, participants, prizes, your own entry (with your team's join code) and the current round or the result.
  • Solo events: Register. Team events: Create team (you get a join code and link to share) or Join with code. If there is an entry fee, a card states it before anything is paid.
  • Unregister, Leave team or Disband team (if you created the team — this unregisters every member) ask first. Paid entry fees are refunded.

Staff with admin.events.run get three more buttons while the event has not finished:

  • Check in (only if the event uses check-in) and Undo check-in open a list of participants where you tick several people at once. After each round of ticks the list is drawn again without them, so it shrinks as you work through it. Long lists come in pages of 25, sorted by name.
  • Withdraw participant works the same way, but first shows a confirmation card naming everyone it hits. Withdrawn participants get no refund and their open matches count as lost.

Everything else about running an event stays in the app — see Events (management).

/rules​

Shows whether you have accepted the server rules, a button to read them on the website and — if the server requires it and you have not accepted yet — Accept rules. The same button sits below the rules in the server's rules channel. Details: Server rules and Syncing rules to Discord.

/ticket​

Opens a support ticket: one request type opens its form directly, several show a list to pick from first. How it works in detail is in the Tickets concept.

Opening a ticket from Discord — with /ticket, a request-type panel or the older ticket panel — needs the right player.tickets.create, exactly like the website. Someone who has not linked their Discord account is judged by the server's default groups (see Settings). Banned players keep their ticket rights.

/player​

Everyone can use /player. Players see their own profile and statistics; staff with admin.players.view can look up any player and act on them — whitelist, notes, warnings, money, bans, claim blocks, DMs, free items and the player's orders, each with its own right. There is no separate /warn: warnings are given from the player card. Details: Acting on a player from Discord.

/logs​

For staff with admin.logs.view — the Log Explorer in Discord. /logs takes no options: it opens a private thread with you, and you search inside it.

The thread holds messages that are redrawn in place whenever something changes:

  1. Filters: players, types, time and position, each with a Change button, plus Reset filters, Open in Log Explorer (the website with the same filters) and Close (deletes the thread).
  2. The results: 39 events per page in three lists of 13, newest first, one line each with time, what happened and a 📍 link to iZurvive when the event has a position. Details next to each event shows the whole event, links to the players involved and the map.
  3. ◀ ▶ below the lists turn the page.

Change opens a form filled with the current filter; sending it updates the thread:

  • Players, three ways that add up:

    • Names, one per line — the full name or a part that fits only one player. If a name fits several players, the filter message asks which ones you mean with a list right below the filters.
    • Discord members: picks every account linked to that member's Discord account.
    • Factions by their Discord role: picks every member of the faction the role belongs to.

    Members and factions bring their alt accounts (sharing a device) too, if you have admin.players.see_alt_accounts — the same as the faction quick filter on the website. Up to 100 players; everything empty means all players. Names the bot could not use are listed as a note on the filter message. With many players, Open in Log Explorer leaves the players out of the link (Discord limits its length).

  • Types: three lists, split alphabetically (Discord allows 25 entries per list). Nothing picked means all types.

  • Time: the last hour, 6 hours, 24 hours (the default), 3 days, a week or a month — or Custom range with From and To, typed like 20:00, gestern 20:00 / yesterday 20:00, 21.09. 18:00, 2026-09-21 18:00 or -2h, in the server's timezone. Typing a new From is enough; an empty To means now. A time the bot cannot read is ignored, with a note.

  • Position: paste coordinates — copied from iZurvive (7512.3 / 3021.5), a whole iZurvive link or the in-game <x, y, z> — and a radius in metres (100 if empty, at most 5000). Leave the coordinates empty to search everywhere again.

Every button checks admin.logs.view again for whoever presses it. Discord shows private threads to members with Manage Threads in that channel as well, so they can see the results too. Threads are deleted a week after they were opened. The thread belongs to the server of the channel you typed /logs in.

/server​

For staff. Opens the server at a glance; each part only shows with the right the website asks for, and the command opens with any one of them.

  • Online now — players with an open session (admin.players.view).
  • Last restart and next restart from the restart schedule.
  • Orders waiting for the next restart, plus those scheduled for later (admin.orders.view).
  • Tickets open and in progress (admin.tickets.view).
  • Switches for whitelist, account linking and Discord nicknames. admin.settings.view shows them, admin.settings.edit adds one button each to switch them on or off. A switch is saved and logged exactly like on the settings page, including the whitelist sync to the game server.
  • Restart now (admin.server.restart): a confirmation says how many waiting orders the restart will deliver; then it restarts like the button on the settings page.
  • Site alerts (admin.site_alerts.view): the banners on top of the website that have not ended yet, switched-off ones included. Each opens its own card to switch it on or off, edit or delete it (each with its admin.site_alerts.* right; deleting asks for confirmation). New alert asks for type, title, message, duration (2h, 3d or an end like 30.09.2026 20:00; empty = until switched off) and start (empty = right away). Times are in the server's timezone. Title and message are written in the server's language; other languages stay as they are and can be edited on the website.

/org​

For staff. Your organization's books at a glance — the same numbers as the accounting dashboard (org.accounting.access, or admin.accounting.view on the server; the server must belong to an organization): income, expenses and result of this month and this year, the three biggest income types of this month, and the 10 latest bookings. Each booking opens a card with category, amount, date, status and, where there is one, the document number and the vendor's invoice number. Amounts are real money, not the in-game currency. Booking and cancelling stay on the website.

Leaderboards in a channel​

Not a command, but part of the same set: dzbot can keep one message with your leaderboards up to date in a channel. See Discord Leaderboard Channel.

For server admins​

There is nothing to set up. The commands exist on every Discord that has the dzbot bot, as soon as the server is connected; which buttons a player sees follows the rights of their groups. The only Discord setting that belongs to this set is the optional leaderboard channel.

To keep a feature out of Discord, take the matching right away in Groups — that removes it from the website too, because both check the same right.