Introduction
Welcome to RCEadmin
RCEadmin is an admin console for your RUST Console Edition servers on PS5 and Xbox — run entirely from your browser. Sign up, connect your server, and turn on the features you need.
Open betaRCEadmin is currently in open beta. It works and is used against live servers, but features can still change and the occasional rough edge is possible. New accounts are approved manually while we're in beta.
What you can do
Instead of typing raw RCON commands, you get a real cockpit for your server:
- A live console — the server's activity in real time, plus a command box.
- Moderation — kick, ban, warn and mute with one click, a ban manager and an audit log.
- Killfeed & stats — PvP/PvE kills, leaderboards and history.
- An in-game bot — auto-kits, scheduled announcements and emote triggers.
- Zones & raid protection, a visual kit builder, and more — as optional modules.
- Integrations — a Discord bot, a Discord webhook and raid alerts.
You choose which modules to run, per server, and turn them on and off any time.
The two "bots"
RCEadmin has two things people call a "bot," and they're completely separate:
- The in-game automation bot — the Automation module. It runs inside your game server: hands out a kit when a player emotes, posts a wipe reminder every Sunday, or rotates welcome messages into chat.
- The Discord bot — bridges your server to Discord: live feeds, a status card, online/offline alerts and slash commands like
/players, /card, /kick.
What you need
- A free RCEadmin account (see Create your account).
- A RUST Console Edition server and its connection details — currently RCEadmin works with G-Portal-hosted RCE servers on PS5 and Xbox.
Getting started
Create your account
Sign up in a minute, wait for your account to be activated, then log in to the console.
Sign up
- Go to rceadmin.com and click Sign up (or open the registration section on the home page).
- Enter your email, a username and a password (twice). Your account's interface language is taken from the language you're reading the site in.
- Agree to the terms and click Create account. You'll see a confirmation that your request was received.
PasswordsPick a strong password: at least 8 characters with upper- and lower-case letters, a digit and a symbol.
Activation
New accounts start in a pending state and are approved before they're fully active. During the open beta this is done manually, so there may be a short wait. While pending you can log in, but the console is read-only until your account is activated.
Log in
Once activated, open the console and log in with your username and password. From there you can connect your server and start enabling modules.
Secure your accountAfter your first login, consider turning on two-factor authentication in Settings → Security — especially since your account controls live servers.
Getting started
Connect your server
Add each RUST server you administer by entering its connection details. RCEadmin connects to it over WebRcon and keeps your RCON password encrypted.
What you need from your host
Three values, all from your host's panel — for a G-Portal server, the server's settings / RCON section:
- Server IP
- RCON port — the RCE default is
28016
- RCON password
Add it (Settings → Servers)
- Open the avatar menu → Settings → Servers.
- Fill Name (anything you like), Server IP, RCON port, RCON password, and optionally a Game language.
- Click Add server — the console connects and starts streaming the live feed.
- To edit later, select the row, change the fields and save (leave the password blank to keep the current one).
Game language
The optional Game language is the language of the messages that modules send into in-game chat — announcements, warnings, kit messages. It's a per-server setting, completely separate from your own panel language, and applies immediately.
Keep the RCON password safeYour RCON password is full control of your game server, so treat it carefully — RCEadmin encrypts it and never shows it back to you. RCEadmin currently works only with RCE servers hosted on G-Portal. How many servers you can add depends on your access.
Getting started
Enable modules
Every feature beyond the plain console is a module you turn on per server. You enable only what you want.
Each server has its own set of modules. Open Settings → Extensions to see the catalog — search, filter and toggle modules for the selected server. A module with its own screen then appears in the left sidebar under Modules.
Using the catalog
- Open Settings → Extensions — the "for <server>" hint shows which server you're configuring.
- Search or filter (All / Enabled / Disabled / Has UI) and toggle a module on or off.
- Open an enabled module from the sidebar to see its screen and settings.
The modules
Killfeed & StatsPvP/PvE kill feed, leaderboards, kill cards.
ModerationKick, ban, warn, mute, ban manager, audit log.
AutomationThe in-game bot: binds, schedules, announcements.
Zones & Raid ProtectionCustom Zones + offline base anti-raid.
Kit BuilderBuild kits visually and push them to the server.
Commands & DocsSearchable reference for every RCE command.
Colour TextBuild coloured <#RRGGBB> say strings.
Discord botFeeds, cards and slash commands in Discord.
Discord webhookSimple one-way channel mirror.
Raid alertsRF-broadcaster raid alerts via /raidlink.
NoteA few modules can't run together — for example the two Discord options (bot vs webhook). If you turn one on, the other turns off. Which modules you can enable depends on your access.
The console
Live console
Your server's activity in real time, with a command box and a dashboard strip of live stats.
When you open a server, the console shows the live event feed — chat, kills, joins and leaves, command replies — and a command box to send any RCON command. Above the feed, a dashboard strip shows connection status and server stats: hostname, map, player count, an online-count sparkline, and uptime. The panel keeps itself connected, and a Reconnect button forces the game-server link to re-establish if it drops.
Using it
- Pick a server from the switcher in the header.
- Watch the feed; type a command in the box at the bottom and press Send (or Enter).
- Use Clear to clear the on-screen feed, and the Colours checkbox to render
<#RRGGBB> colour tags instead of raw codes.
NoteWhile your account is pending activation, the console is read-only — you can watch the feed but inputs are disabled. If you have 24/7 bots, you also get a feed filter/search and an Export log button.
The console
Player roster
A live per-server roster and player history — who's online, who's been seen, and the teams on your server.
The console tracks who is online, total online time, session counts and RUST team membership for each server. In the Console view, a roster block shows Online, Seen and Groups tabs, and clicking a player opens a player card with their profile and team history. Because console servers expose no SteamID, everything is keyed by display name.
The three tabs
- Online — the live roster: ping, total online time, current team and team size.
- Seen — everyone ever seen: platform, online flag, total time, session count, first/last seen.
- Groups — the teams currently on the server, biggest first.
Tiers
You can give a player a tier — VIP, Moderator, Admin or Owner — which colours their name in the feed and roster. Tiers are also used by other modules (for example, the Automation bot uses them for access levels, and the Moderation module sets them when you grant access). Set a tier from the player card.
The console
Keep your bots running 24/7
Normally your bots and monitoring run while you're logged in. With 24/7 access, they keep working around the clock — even when you're logged out.
By default, the modules you've enabled (announcements, auto-kits, raid protection, killfeed, …) run while you have the console open. Turn on 24/7 access and they keep running continuously, so your server keeps getting scheduled announcements, auto-kits and monitoring whether or not anyone is signed in.
How to get it
You can see your status in Settings → Profile, which shows whether 24/7 access is on for you and how many of your servers are covered. Availability depends on your access — if it isn't enabled yet, the console shows a short note; reach out to us to have it turned on.
Good to knowOnce granted, your setup is remembered — your bots come back automatically after any restart, and each server's connection heals itself if the game server reboots.
Modules
Killfeed & Stats
Turns in-game deaths into a PvP/PvE kill feed, keeps per-player stats and leaderboards, and can announce kills to chat and to Discord.
Killfeed watches your server for death messages and records every one. It automatically tells PvP kills (player-vs-player) apart from PvE deaths (animals, NPCs, traps, suicides) and stores each one, so leaderboards and personal stats are always available. Optionally it announces kills in-game and posts rich "kill cards" to a Discord channel, and answers stats lookups that players trigger with quick-chat emotes.
Enable it
Settings → Extensions, toggle Killfeed on for the server. Discord kill cards and the /top command need your Discord bot linked (pick the channel in this module's Configure).
The Stats panel
- Total deaths recorded, with badges for whether PvP and PvE announces are on.
- PvP and PvE leaderboards — top players by kills; names open the player card.
- A recent feed with time, coloured kind badges, filter chips and a player search.
- A Configure button for the settings.
Key options
- Announce PvP / PvE — post kills to chat (both off by default, independent). Templates use placeholders
{killer}, {victim}, {cause}, {source}.
- Stats lookups — players check their own stats or the top boards with quick-chat emotes (RCE has no free chat, so lookups ride quick-chat tokens).
- Discord kill cards — style (full / text / compact), footer, and per-kind titles/text with a live preview.
NoteRecording is always on — stats accumulate even with announces off. The recent feed keeps 30 days of history (rolling leaderboards). On some servers the kill lines may need a quick calibration — reach out if kills aren't showing.
Modules
Moderation
A full moderation suite — kick, ban, warn, mute (chat & voice), a ban manager, warn auto-escalation, private notes and an audit log.
Moderation gives you one-click punishment actions that run the real commands on your server. It keeps a ban list, tracks warnings (with optional automatic escalation to mute/kick/ban), records private per-player notes, and logs every action. Because the console has no SteamID, everything is keyed by the player's display name — the same name shown in the playerlist and ban list.
Enable it
Settings → Extensions, toggle Moderation on per server. The live roster, presence and player card are already part of the console; this module adds the punishment layer on top.
The panel
- An action form: Target, Reason, Minutes, plus buttons — Look up, Kick, Warn, Remove warns, Mute/Unmute chat, Mute/Unmute voice, Note, and Ban.
- The ban list with Unban and Refresh.
- Most-warned players and the full audit log.
- Configure for escalation and announcement settings.
Warn escalation & announcements
You can map a warn count to an automatic action — e.g. 3 warns → mute chat, 5 → kick, 7 → ban. Per-action in-game broadcasts use placeholders {name} / {time} / {reason} / {admin}; a blank template stays silent (the default). Colours can be embedded with <#RRGGBB> tags.
NoteEverything keys off the display name — the target must match the playerlist/ban-list name exactly (there is no SteamID on console). The ban reason is kept in your audit log, not sent to the game. If your Discord bot is linked, you can also moderate with slash commands and sync tiers to Discord roles.
Modules
Automation (the in-game bot)
The in-game bot: command groups, chat/emote binds, cron schedules and rotating auto-announcements.
Automation is your server's built-in bot. It watches in-game chat and quick-chat emotes and reacts by running commands you define — handing out a kit when a player types "i need wood", teleporting them, broadcasting a wipe reminder on a schedule, or rotating announcements into chat. You build everything from reusable command groups, then bundle triggers into named presets you start and stop with a single play button.
Not the Discord botThis is the in-game bot — it runs commands on your game server. The separate Discord bot bridges activity to Discord. They're unrelated.
Enable it
Settings → Extensions, toggle Automation on per server. Command insert-pickers appear when the Kits and/or Zones modules are enabled, and the command search needs the Commands module.
The four building blocks
- Command groups — a named list of commands run in order with an interval between them.
- Binds — a chat phrase or quick-chat emote that calls a command group, gated by a required access level and cooldowns.
- Schedules — a cron expression that calls a command group at set times.
- Announcements — rotate a list of messages into chat on a fixed interval.
A Preset bundles binds/schedules/announcements; its ▶/⏹ button is the single on/off control. Four templates are seeded on first use: Auto-kit by emote, Teleport to a zone, Scheduled broadcast, Rotating announcements.
Example: auto-kit by emote
- Create a command group with
kit givetoplayer "wood" "{PlayerName}".
- Create a bind with trigger "i need wood" pointing at that group; set an access level + cooldown.
- Create a preset that references the bind, and press ▶.
Access levelsBinds can require a minimum level (owner > admin > mod > vip > all). A player's level is their tier, which you set on the player card. Placeholders include {PlayerName}, {GameConsole}, and cooldown text. A bind is live only while a running preset references it.
Modules
Zones & Raid Protection
Manage native RCE Custom Zones (the Fortify feature) and run per-player offline base anti-raid, driven by in-game emotes.
This module does two related jobs on top of RUST Console Edition Custom Zones. First, it's a manual zone manager: create, edit, delete and inspect any zone, with a one-click "raid window" toggle to open or close building damage. Second, it runs automatic offline raid protection — a player marks their base in-game with an emote, the bot reads the position and drops a protection zone around it, and that base is shielded while its owner/team is away.
Enable it
Settings → Extensions, toggle Zones & Raid Protection on. Configure opens the raid-protection settings.
The panel
- Custom zones tab — zone cards (name, shape, position, size, protected/raidable badge) with Edit, raid-window open/close, Info and Delete, plus a create/edit form.
- Raid protection tab — per-base cards (owner, position, radius, status) with Protect / Unprotect / Delete overrides.
- Sync — reconciles your saved zones against what's live on the server.
- Configure — registration, activation, protection effect, appearance and messages.
Registration & activation
Registration: team (default) — the player must be in a RUST team, and the team shares a zone cap; a base is auto-removed if its owner leaves the team. Activation: emote (the owner toggles protection with an emote while standing in their zone) or auto (protect while the whole team is offline, unprotect when anyone comes online). By default a protected base blocks only building damage.
The most important thing to knowThe settings are a template applied when a zone is created — changing them later does NOT rewrite existing zones. An existing base only picks up new settings (colours, block flags, messages) when it's re-created / re-applied. Also, the default emote triggers are best guesses — verify the real quick-chat token in-game.
Modules
Kit Builder
Build kits visually from an 800+ item catalogue and push them to your server — no console commands to type.
Kit Builder lets you assemble in-game kits visually. Browse a catalogue of RUST Console items (searchable, category-filtered), drag items into a RUST-style inventory (Wear / Inventory / Belt), set quantities, and see the kit build live. Saved kits are stored per server; a Send pushes them to the game, and a Sync mirrors the panel against the server's live kit list.
Enable it
Settings → Extensions, toggle Kit Builder on. The server must be reachable to Send or Sync.
Building a kit
- Enter a kit name.
- Drag items from the catalogue into Wear / Inventory / Belt (or click to drop into Inventory).
- Select each item to set its quantity and slot.
- Save (stores it) and/or Send (saves, then pushes to the server).
An Active & saved kits list shows your kits, previews their contents, and offers Load / Send / Rename / Disable / Delete plus Sync.
NoteSend is a full replace — it deletes the kit on the server first, then re-adds every item, so your edits reflect exactly. Handing a kit to a player is done by Automation (a bind that calls kit givetoplayer) — Kit Builder only creates and pushes the kit definitions.
Modules
Commands & Docs
A searchable in-console reference for every RUST Console Edition command, with descriptions, examples and click-to-insert.
This adds a Commands & Docs screen: a searchable, category-grouped catalog of every console command with its input signature, default value and a description. Each command carries a curated knowledge card — what it affects, ready-to-use examples, and extra search keywords. It's a pure reference; it never sends anything to your server on its own.
Enable it
Settings → Extensions, toggle Commands & Docs on. No setup needed.
Using it
- A search box matches command name, signature, description and keywords (including Ukrainian synonyms).
- Category filter chips and a grouped list, each row showing name, signature and default.
- A + button inserts a command into the console box; click a card to expand its details and examples.
Modules
Colour Text
Build coloured <#RRGGBB> strings for say announcements and server names, with gradients, presets, a message library and a live preview.
Type some text, pick colours, and Colour Text produces the coloured string that RUST Console Edition uses. It offers a gradient mode (1–8 colour stops blended across the characters) and a word-colours mode (a colour per word), plus a library of ready-made message templates for common server events. Everything runs in your browser.
Enable it
Settings → Extensions, toggle Colour Text on. No setup needed.
What you get
- A gradient builder and a word colours editor.
- Presets: built-in gradients (Rainbow, Fire, Ice, Toxic, Sunset, Ukraine) plus your own saved ones.
- A message library grouped by category (rewards, events, killfeed, moderation, store), each with a preview and Copy / Load.
- Copy the raw string, or Insert as say (prefills the console so you review and send it yourself).
NoteWhether RCE renders chat colour tags in-game isn't guaranteed — confirm on your own server; coloured server names are the safest use. Library templates are ASCII-only (RCE chat rejects emoji).
Integrations
Discord bot
Bring your server into Discord: live feeds, a status card, and slash commands like /players, /card, /kick, /ban.
This module connects your RUST server to a Discord server ("guild"). You choose which channels receive live feeds (joins, leaves, chat, world events, admin spawns, raw console, status), and manage player self-linking and the chat relay. A Monitoring tab shows everything the bot posted for your server with a searchable 30-day history.
Setup
- Invite the bot to your Discord server — press "Invite the bot" (this opens our official RCEadmin bot; you don't create or host anything).
- Generate a link code in the panel (single-use, valid ~10 minutes).
- In Discord run
/rce link <code> (needs the Discord "Manage Server" permission).
- Pick the feed channels per guild — Joins/Leaves, Chat, Server events, Admin spawns, Console, Status. (The kill feed channel is chosen in the Killfeed module.)
Slash commands
All replies are ephemeral (only the person who ran it sees them).
- Everyone:
/players, /card <name>, /top (needs Killfeed), /link-game / /unlink-game.
- Manage-Server users:
/rce link, /rce status, /rce unlink, plus moderation /kick /ban /unban /warn /mute /unmute (needs the Moderation module).
Feeds post into your chosen channels, and a Status channel shows online/offline alerts plus a live server card (players / uptime / map) updated every minute.
NoteThe Discord bot is the official RCEadmin bot — you just invite it, no token or setup on your side. It's mutually exclusive with the Discord webhook (turning one on turns the other off). Admin commands only work for people whose Discord is linked to a panel account that owns the server. /ban asks for confirmation first.
Integrations
Discord webhook
A lightweight, one-way mirror of selected server events into a single Discord channel via a webhook URL — no bot needed.
This is the simple alternative to the Discord bot. Instead of a full bot, you paste one Discord webhook URL and tick which events to forward — chat, joins/leaves, deaths, world events and moderation actions. It's outbound-only: it posts to Discord, with no slash commands, cards or two-way features.
Setup
- In Discord: Server Settings → Integrations → Webhooks → New Webhook, pick the channel, Copy Webhook URL.
- In the console: enable Discord Webhook on the server, paste the URL, tick the events you want, Save, then Send test.
The status screen shows your configured events and live counters (queued / sent / dropped / last error).
NoteMutually exclusive with the Discord bot. It relies on other modules for content: Deaths need Killfeed enabled, and Moderation events need Moderation enabled. Only Discord webhook URLs are accepted, and private admin notes are never mirrored.
Integrations
Raid alerts
RF-broadcaster raid alerts: players claim a frequency with /raidlink, and when their in-game alarm transmits, the module DMs the owner/team, posts to a staff channel, and/or announces in game.
RUST Console Edition exposes no structure-damage event, so a literal "a wall took C4" alert isn't possible. Instead this module uses the game's own RF (radio-frequency) system: a player wires an in-game trigger to an RF Broadcaster on a personal frequency, and the module detects when that broadcaster starts transmitting (the trigger fired). It then delivers a raid alert through the Discord bot and/or in game.
Setup
- A player runs
/raidlink in Discord and gets a unique frequency (identity comes from their /link-game gamertag).
- In game they wire a trigger → an RF Broadcaster set to that frequency. A Seismic Sensor is recommended (fires on nearby explosions = the actual raid); other triggers work too.
- You enable the delivery targets in this module's Configure.
Delivery targets
Four independent toggles: DM the owner (default on, online or offline), DM the whole team, Staff channel (also gets alerts for unclaimed frequencies), and in-game global announce (off by default, a public deterrent).
NoteWiring up a broadcaster never fires an instant false alert (the first check is a silent baseline), and a cooldown suppresses a flapping sensor. Delivery goes through the Discord bot, so a player must have run /link-game first.
Your account
Account & access
Your account controls live servers — here's what its status means and how to manage it.
Account status
Every account has a status:
- Pending — just registered, awaiting approval. You can log in, but the console is read-only.
- Active — approved; full access to your servers and features.
What you can do — how many servers you can add, which modules you can enable, and whether your bots run 24/7 — depends on your access. During the open beta this is set for you; reach out if you need more.
Your profile & password
Open the avatar menu → Settings:
Your account
Two-factor authentication
Protect your login with an authenticator app, plus one-time recovery codes.
Because your account controls live servers, it's worth adding a second factor. Once enabled, login asks for a 6-digit code after your password, using any standard authenticator app (Google Authenticator, Aegis, 1Password, …).
Turn it on (Settings → Security)
- Open Settings → Security → Two-factor authentication → Enable 2FA.
- Add the shown secret / QR code to your authenticator app.
- Enter the current 6-digit code and Confirm & enable.
- Save the recovery codes shown once — each works a single time, for when you lose your authenticator.
At login, after your password you enter a 6-digit code or one recovery code. To turn it off, use Settings → Security → Disable, confirming with a current code.
Your account
Appearance & language
Pick a design, a light or dark mode, and your panel language — per account, applied live.
Choose the look of your console and the language of the panel itself. Changes apply immediately to all your open sessions and are remembered on your account.
Choosing (Settings → Appearance)
- Pick a Design from the dropdown.
- Toggle Light / Dark (a quick sun/moon toggle also lives in the header).
- Choose your Language (also on the avatar menu).
Panel languages: English, Ukrainian, German and French.
NoteYour panel language is separate from a server's in-game game language — one is the language you read the console in, the other is the language modules use in in-game chat.
Roadmap
Roadmap
Where RCEadmin is and where it's going. It's a fast-moving open beta — this page is a direction, not a dated commitment.
✓ Available now
- The console — a live feed and command box for each of your servers, with a player roster and history.
- Your account — sign-up, two-factor authentication, and the option to keep your bots running 24/7.
- Modules — Killfeed & Stats, Moderation, Automation (the in-game bot), Zones & Raid Protection, Kit Builder, Commands & Docs, and Colour Text.
- Integrations — a Discord bot (feeds, live status card, slash commands, moderation from Discord), a Discord webhook, and RF-based Raid Alerts.
- Personalization — six themes and four panel languages (English, Ukrainian, German, French).
◆ In progress
- A smoother Discord setup — each module managing its own Discord feeds and commands from its own screen.
- This site & documentation — the home page, sign-up flow and these docs.
- Live-server polish — ongoing tuning against real in-game sessions.
○ Planned & exploring
- Smarter raid alerts — a graded raid "incident" that goes beyond a single ping: dwell time, group size, escalation and a live updating card.
- Events & minigames — packaged server events and game modes (KOTH, arena, BR) with countdowns, an announcer and auto-rewards.
- Pro plan — RCEadmin is free during the beta; a paid plan (more servers, no ads on your servers, priority support) will arrive once it's ready.
- More languages for the site and these docs, mobile polish, and the road to a stable 1.0.
Have a request?The roadmap is shaped by the people running servers on it. Join the Discord and tell us what you need most.