Restrictions
This page explains how to use the Restrictions panel in the admin area — how to create, manage, and review bans and event-based restrictions.
Navigation path:
Server Admin→Restrictions
For a conceptual overview of how restrictions work, see Restrictions concept.
Access requirements
| Right | What it unlocks |
|---|---|
restrictions.view | Open the restrictions list and read details |
restrictions.create | Create new restrictions |
restrictions.edit | Edit, end and add notes or tickets to existing restrictions |
restrictions.delete | Delete restrictions that are no longer in force (cleanup only) |
players.warn | Warn players (see Warnings) |
The restrictions list
The list shows all restrictions created for your server. Use the Active and Expired tabs to switch between currently enforced restrictions and those that have already ended.
Filters
Use the filter bar to narrow the list:
- Type — bans, claim blocks or event restrictions, in any combination
- Player — restrictions on a specific player, including those that reach them through their account on another server of the organization or an alt sharing a device
- Faction — restrictions on a specific faction
- Ticket — restrictions linked to a specific ticket
- Created — a date range
The search field finds a restriction by its number, the name of a restricted player or faction, the code of a linked ticket, or words from its reason or lift reason.
Each row shows:
- Restriction type (Ban or Event)
- Who it targets
- Status badge (Pending / Active / Expired)
- How many violations have been recorded so far
Click any row to open the full detail and edit view.
Creating a ban
Bans block a player from joining your server. They are synced to Nitrado when Synchronize player lists is active in your Settings.
- Click New restriction and select Ban.
- The restriction drawer opens.
Setting the time period
- Starts at — leave empty for the ban to take effect immediately. Set a future date for a pending ban.
- Expires at — leave empty for a permanent ban. Set a date to issue a temporary ban.
Scope
A new ban applies to All organization servers by default — also a ban from Discord, the AI Companion, an action, a zone or an escalation. Switch to This server to ban the player only on the server you are on.
Adding targets
Click Add target to choose who the ban applies to.
- Choose Player and search for the player by name.
- Choose Faction to ban all current members of a faction.
- Enable Include all accounts to automatically extend the ban to all alt accounts sharing a device with the target. This is the recommended setting for all bans to prevent evasion through alt accounts.
You can add multiple targets to a single restriction if the ban covers a group of players.
Adding actions
Actions define what dzbot does when the ban is created. For bans the available trigger is On creation.
Useful actions on ban creation:
- Channel notification — post a message to your staff Discord channel so your team is informed immediately.
- Warning DM — send the banned player a private Discord message explaining the ban.
Description
Describe the reason for the ban, the evidence, and any relevant context. This becomes the first note of the restriction's history and is shown as its summary in lists. Only staff with restrictions access can see it.
It cannot be edited later. Anything that comes up afterwards — another incident, a talk with the player — is added as a new note.
Reason: cheating
Switch on Reason: cheating when the player demonstrably played with a device such as Cronus or XIM. These bans are the yardstick the Cheating-Index page measures other players against, so every one makes the comparison more precise. The switch can still be changed on an existing ban, and the ban form on the player dossier has it too.
Save
Click Save to create the ban. If Nitrado sync is active, the player is removed from the game server within seconds.
Creating an event restriction
Event restrictions watch for things that happen in the game and respond automatically.
- Click New restriction and select Event restriction.
- The restriction drawer opens.
Setting the time period
- Leave Starts at empty for the restriction to be active immediately.
- Leave Expires at empty if the restriction should run indefinitely.
Adding targets
Same as bans — add players or factions, with optional alt account coverage.
The violation counter on each target tracks how often that specific target has triggered this restriction.
Choosing trigger events
Select which in-game event types should trigger this restriction. You can select multiple event types. Common options:
- Kill events (player kills another player)
- Death events
- Chat messages
Setting a zone (optional)
If you only want the restriction to fire when events happen in a specific area:
- Click Draw zone to open the map editor.
- Click on the map to place waypoints and draw a polygon around the area.
- Enable Invert zone if you want the restriction to fire for events outside the drawn area instead of inside it.
Leave the zone empty if location does not matter.
Ignore server defaults (optional)
If your server has server default actions set up, they apply to all event restrictions automatically. Enable Ignore server defaults on a specific restriction if you do not want those defaults to fire for this one.
Adding actions
This is where you define what happens when the restriction triggers. Click Add action to add a step.
For each action, choose:
Action type:
| Type | What it does |
|---|---|
| Warning DM | Sends a Discord DM to the player who triggered the event |
| Channel notification | Posts a message to a Discord channel |
| Balance penalty | Deducts an amount from the player's balance |
| Automatic ban | Creates a ban on the player (with configurable duration) |
When to trigger:
| Option | When it fires |
|---|---|
| On every violation | Every time the event occurs |
| On the Nth violation | Only on exactly the Nth offense |
| From the Nth violation onward | On the Nth offense and every one after |
Example escalation chain:
| Action | Trigger |
|---|---|
| Warning DM: "You killed in the safezone. Next offense will have consequences." | On every violation |
| Balance penalty: −500 | From the 2nd violation onward |
| Automatic ban for 3 days | From the 4th violation onward |
Counting violations as warnings (optional)
Turn on Counts as warning under the restriction's actions to have every violation also write a warning on the player. Those warnings count toward your server's warning stages just like the ones your team gives by hand. Warning expires after (days) decides how long each of them counts; leave it empty and they never expire.
Off by default. The restriction's own actions still do the talking — a counted violation does not send the player a DM by itself.
Save
Click Save to activate the restriction. Violations will be recorded from this point forward.
Editing a restriction
Open any restriction from the list to edit it. You can change:
- Start and expiry dates, and the scope — optionally with a note saying why
- Reason: cheating on a ban
- Linked tickets (link several, or unlink one)
- Targets (add or remove)
- Actions (add, change triggers, or remove)
- Zone settings
Editing an active restriction takes effect immediately after saving. Every change lands in the history.
History
The History section in the overview tells the whole story of a restriction, newest first: when it was imposed, every change, every linked or unlinked ticket, every note, and when it was ended, ran out or was reactivated.
Each step shows who did it:
- a staff member, and whether it was done on the web, via Discord, via the AI companion or via MCP from a connected AI app (a companion step is always the staff member who approved it, or whose session ran it in Execute mode);
- an Action, with a link to the action and the run, and — where the event names one — what set it off, for example the review it was opened for;
- dzbot itself, for example when a restriction runs out, a zone rule bans someone or an unverified account's deadline passes.
Use Add note to record anything new about the case. Notes cannot be edited or removed; a correction is a new note.
Restrictions from before this history existed show entries marked backfilled. They were reconstructed from older records and may be incomplete.
Reviewing violations
When you open an existing restriction, the Violations section shows a full history of every time a target triggered it:
- Player name
- Which target was matched
- Timestamp
- Link to the original game log event (if still available)
Use this to assess how often a restriction has fired, verify escalation is working as intended, and build a case record for moderation decisions.
Ending a restriction
Ending is the normal way out of a restriction. Open the restriction and click End. You always have to say why it is being lifted — for example "appeal accepted in the ticket" or "wrongful ban". The same dialog lets you link a ticket.
The reason becomes the note of the Ended step in the history, together with who ended it and when.
Every other way of lifting a restriction asks for a reason too:
- setting Expires at to now or a past date, or Starts at to a future date, in the edit form;
- removing a player from an active ban under Targets;
- Unban on the Discord player card, and the AI companion's unban proposal.
Restrictions that simply run out and anything an automation does need no reason.
Deleting a restriction
Deleting is for cleaning up — a duplicate, something created by mistake. It needs restrictions.delete and sits in the … menu of the restriction.
- Only restrictions that are no longer in force can be deleted. End an active one first.
- You always have to say why.
- The restriction disappears from lists, but its history and a snapshot of what it looked like are kept. On a player's Moderation page, Show deleted lists them again, read-only.
Violations recorded for the restriction are removed with it.
Warnings
A warning is a player note with a warning mark. Your team gives one with Warn on the player's page or on the Discord player card; a restriction with Counts as warning gives one for every violation.
- Expiry: whoever warns decides whether and when the warning expires. Only warnings that have not expired count.
- Nothing disappears: expired notes and warnings stay on the player's page, in the Discord notes and in the search, marked as expired. They just no longer count.
- Per server: a warning counts on the server it was given on. The notes themselves are visible on every server of your organization, like all player notes.
- Telling the player: a warning can be sent to the player as a Discord DM (on by default) and can time them out on your Discord server. The timeout needs the bot permission Moderate Members and a bot role above the player's roles; if it fails, the Discord audit page says so.
Warning stages
Under Settings → Whitelist & Accounts → Warning stages you set what a number of active warnings leads to, for example:
| Active warnings | Ban |
|---|---|
| 3 | 1 day |
| 5 | 7 days |
| 7 | permanent (duration left empty) |
When a new warning brings the player to a stage, dzbot creates a normal ban: it appears in this list, names the warnings in its description, reaches Nitrado like any other ban, and lifting it needs a reason. If the player is already banned, the existing ban is extended instead.
How the stages behave:
- Only the highest stage reached fires. Jumping from 2 to 5 warnings bans for the 5-warning stage, not for both.
- The same warnings never fire a stage twice. After a stage has fired, it can only fire again once every warning that was active at that moment has expired — a fresh run of warnings, in other words.
- A warning that expires does not lift a ban that was already given.
- No stages (the default) means warnings never ban anybody.
Server default actions
Server default actions apply to all event restrictions on your server automatically. This lets you set up a "notify staff channel on any violation" rule once instead of adding it to every restriction individually.
To manage server defaults, open the restriction list and click Server defaults in the top-right corner.
Add one or more default actions:
- Warning DM — sent to the player who triggered any event restriction
- Channel notification — posted to a Discord channel of your choice on every event restriction trigger
A specific restriction can opt out of server defaults by enabling Ignore server defaults in its settings.
How bans reach the game server
Bans are synced to Nitrado automatically when Synchronize player lists is active in Settings. Without this setting enabled, bans are recorded in dzbot but will not take effect on the game server.
When a ban expires, dzbot removes it from the Nitrado banlist on the next sync. No manual action is required.
The setting counts per server. A ban for All organization servers only takes effect on the servers that sync their player lists. When you create or edit a ban, a warning names every server in its scope where sync is off. Turning the setting on first takes over the bans that so far only exist on Nitrado, then sends the ban list to Nitrado.