Server Commands
Commands are the core of Servycore's automation. When a player links or unlinks their account, Servycore automatically executes commands on your game servers.
Prerequisites
- A connected game server (see Connecting Your Game Server)
- Commands enabled in your project settings
How Commands Work
Commands are triggered based on two events:
| Type | When It Fires |
|---|---|
| Auth (Authentication) | When a player meets the provider condition (e.g., joins your Discord, follows on Twitch) |
| Deauth (Deauthentication) | When a player no longer meets the condition (e.g., leaves your Discord, unfollows on Twitch) |
Adding Commands
Navigate to Panel > Your Project > Servers > [Your Server] > Commands and click Add Command.
Command Settings
| Field | Description |
|---|---|
| Active | Toggle to enable or disable this command |
| Type | Authentication (auth) or Deauthentication (deauth) |
| Provider | The account provider that triggers this command |
| Command | The command to execute on the server (max 450 characters) |
Available Providers
| Provider | Description |
|---|---|
| Steam Group Member | Triggers when player joins/leaves your Steam group |
| Discord Guild Member | Triggers when player joins/leaves your Discord server |
| Discord Guild Nitro | Triggers when player starts/stops boosting your Discord server |
| Twitch Follower | Triggers when player follows/unfollows your Twitch channel |
| Twitch Subscriber | Triggers when player subscribes/unsubscribes to your Twitch channel |
Command Variables
You can use the following variables in your commands. They will be replaced with the player's actual values when executed:
| Variable | Description |
|---|---|
{SteamID} |
The player's Steam ID |
{SteamName} |
The player's Steam username |
Example Commands
Rust - Discord Member Rewards
Auth command:
oxide.usergroup add {SteamID} discord
Deauth command:
oxide.usergroup remove {SteamID} discord
Rust - Welcome Message
Auth command:
say "{SteamName} has linked their account!"
Rust - Twitch Subscriber VIP
Auth command:
oxide.usergroup add {SteamID} twitch-sub
Deauth command:
oxide.usergroup remove {SteamID} twitch-sub
Command Events
Every command execution is logged. Navigate to Panel > Your Project > Servers > [Your Server] > Events to view the execution history.
You can search events by:
- Status (success/failed)
- Command text
- Player name, Steam ID, Discord ID, or Twitch ID
- Game server name
Re-executing Failed Commands
If a command fails, you can re-execute it from the events page (up to 3 retries). Note that re-execution is not available for Plugin connection type servers.
Duplicate Prevention
Servycore automatically prevents duplicate command execution. If the last command for a player on a given provider was already an auth, another auth command won't be sent again. The same applies for deauth commands.
Notes
- Commands are executed in real-time when the trigger event occurs
- During regular checking (if enabled on your plan), commands are re-evaluated for all players
- You can copy commands between servers in the same project to save setup time
Related Articles
Connecting Your Game Server
Connect your Rust, ARK, CS:GO, or Garry's Mod game server to Servycore via Plugin, RCON, o...
Discord Account Linking
Set up Discord account linking on Servycore — automatic role assignment, guild membership...
Steam Account Linking
Configure Steam account linking on Servycore — verify Steam group membership, automate in-...