Each rule reads as WHEN something happens, IF conditions match, THEN do these actions. Rules run all the time, even when no staff is online.
Create a rule
- 1
Open the server and select Automation, then create a rule.
- 2
Choose the trigger.
- 3
Add conditions, or none to always run.
- 4
Add one or more actions in the order they should run.
- 5
Set a cooldown if the rule should not fire too often.
- 6
Test it against sample data, then turn it on.
Triggers
| Group | Examples |
|---|
| Players | Connected, disconnected, chat message, killed, banned, kicked, muted, reported, name changed, strike added, alternate account detected |
| Bans | Ban revoked, appeal submitted, appeal reviewed |
| Server | Crashed, status changed, world saved, wiped, claimed, new review |
| Operations | Command sent, team changed, plugin error, backup completed or failed, connection lost or restored |
| Schedule | Runs on a timetable you choose |
Actions
| Action | What it does |
|---|
| Notification | Discord webhook, your own webhook, in app, or Discord bot when enabled |
| Kick, Ban, Mute, Warn | Moderate the player who triggered the rule |
| RCON Command | Run any command, with values from the event |
| Give, Teleport | Give items or a kit, or move a player |
| Set Oxide Group | Add or remove a group or permission |
| Add Tag, Remove Tag, Add Note | Update the player's profile |
| Counter | Count events in a time window, for example chat messages per minute |
| Condition Gate | Stop the remaining actions if a condition fails |
| Tag Message | Post a labelled entry to the activity feed |
A rule without a server applies to every server in your organization. Pick a server to limit it.
Free organizations have a limited number of rules. Beta Tester access raises it.
