How to link Discord to your Rust server

Linking Discord to a Rust server means connecting each player's Discord account to the Steam account they play with, so your server can reward them in game. The player signs in once with Steam and once with Discord on a web page, your Discord bot checks that they are in your Discord server (and, if you want, that they boost it), and your Rust server runs a command, usually adding their SteamID to an Oxide or Carbon group. When they leave your Discord, the opposite command takes the reward back.

What linking actually does

Your Rust server only knows a player by their SteamID64. Discord only knows them by their Discord ID. Nothing in Rust connects the two, so linking is the step where a player proves both accounts belong to them:

1. The player opens a link page and signs in with Steam (that gives you their SteamID64).
2. They authorize with Discord (that gives you their Discord ID).
3. Your bot checks the condition you reward: member of your Discord server, booster of it, or both.
4. Your server runs the reward command with their SteamID, for example oxide.usergroup add 76561197960287930 discord.

From then on, the link is a fact you can check again: when the condition stops being true, the same system runs the removal command (oxide.usergroup remove …) and the in-game perks go away.

Need to check a SteamID by hand? The SteamID converter turns any format into the SteamID64 Rust commands expect.

The pieces you need

Whatever tool you use, a working Discord link on Rust always needs the same five things:

• A page where players sign in with Steam and Discord. Steam sign-in gives you a trustworthy SteamID; Discord OAuth2 gives you their Discord account. Typing a SteamID into a form proves nothing.
• A Discord bot in your server. Only a bot that is a member of your guild can check membership and boosts, and give or remove roles. Its own role must sit above the roles it hands out in Server Settings > Roles, or Discord refuses.
• A way to run commands on the Rust server. RCON, a plugin on the server, or your host's panel: something has to send usergroup add when a player links.
• A group with the perks. Create the group once, give it the permissions of your plugins, and the linking command only has to add players to it.
• A recheck. People leave Discord servers and stop boosting. Without a regular recheck, rewards stay forever.

Rewarding the link in game

The cleanest setup is one group per reward, created once on each server:

Two traps worth knowing:

• Use the prefix of your framework. Carbon refuses the oxide. commands; write c. commands on a Carbon server.
• Carbon only knows players who joined the server once. A c.usergroup add sent for a player who links before ever playing on that server is answered "Couldn't find that player." and nothing is given. The command has to be sent again at their first connection.

A missing group fails too: Oxide answers that the group doesn't exist, Carbon that it could not be found. Create the group first, then link.

Keeping rewards honest

Linking is not a one-time event. Decide what happens when the condition changes:

• Left your Discord server: the unlink command runs and the in-game group is removed.
• Stopped boosting: if you reward boosters separately (a booster group, for example), only that reward goes.
• Unlinked their account: every reward of that account is taken back.

A recheck catches all three. Run it on a schedule, and ideally when the player joins your server, so a change never waits days.

Discord roles for linked players

Linking works in both directions. Besides the in-game group, the bot can give a Discord role to every linked member, so you can open a "verified" channel or show who plays on your servers. The same hierarchy rule applies: the bot's role must be above that role.

On a Rust network you can go one step further and tie Discord roles to in-game groups: whoever holds the vip group in game gets your VIP role on Discord, and loses it when the group ends.

How Servycore does it

Account linking is the heart of Servycore, and every piece above is built in:

• Your community website has the link page. Players click Link Discord, Link Steam or Link Twitch. Your Discord members can also type /link to the Servycore bot, and on Rust the Servycore plugin adds an in-game /link command.
• Linking commands per provider: Steam group member, Discord guild member, Discord guild Nitro (boosters), Twitch follower and Twitch subscriber. Each has On link and On unlink commands with the {SteamID} and {SteamName} variables, sent through RCON, the Servycore plugin or your Pterodactyl panel.
• The usual commands are written for you. On a new Rust server, Servycore adds the usergroup add / remove commands for the providers your project uses at the first RCON connection, once it knows whether the server runs Oxide or Carbon.
• The Carbon trap is handled. A command answered "Couldn't find that player." shows Waiting for join, and on a server of the Control Center it is sent again at the player's first connection, in the order they linked and unlinked.
• Nothing gets lost. When a player joins a Rust server of the Control Center, Servycore sends the link commands that server missed for them (a new server, a command added later, one that failed while the server was down) and the unlink commands of an account they unlinked meanwhile. Their Discord status is also checked again at that moment if the last check is a day old or more.
• Roles follow. The Discord role you choose is given on link and removed on unlink, and groups can carry a Discord role of their own.
• Every command is logged. The command events page shows what ran, for whom and the server's answer, with a button to send a failed command again. Players who got no reward can click Check again on the link page.