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 existing restrictions |
restrictions.delete | Delete restrictions |
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 — show only Bans or only Event restrictions, or both
- Player — search for restrictions that target a specific player
- Faction — search for restrictions that target a specific faction
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.
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.
Case notes
Add a staff-facing note explaining the reason for the ban, the evidence, and any relevant context. Only staff with restrictions access can see this.
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 |
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
- Case notes
- Targets (add or remove)
- Actions (add, change triggers, or remove)
- Zone settings
Editing an active restriction takes effect immediately after saving.
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.
Deleting a restriction
Open the restriction and click Delete. Expired bans are removed from the Nitrado banlist on the next sync. Violation history is removed along with the restriction.
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.