How to Set Up a Rust Console Bot for Game Server Management

Step 1: have a Rust Console server

A bot manages a server you already rent. Rust Console Edition servers come from the official hosts, G-Portal and Nitrado, on PlayStation and Xbox. If you are starting from nothing, the beginners guide to Rust Console server rentals covers choosing between them. Nothing in the rest of this page needs anything installed on the server itself.

Step 2: add the bot to your Discord and sign in

Add Vantic to the Discord your community uses, then open the dashboard and sign in with Discord. There is no Vantic account to create and no password: the Discord you already have is the login, and who can change what inside the dashboard follows the roles your community already trusts. From here on, everything can be done from the dashboard or from Discord, and both read the same settings.

Step 3: connect the server

On G-Portal, open your server panel and copy three things: the server IP, the RCON port, and the RCON password. Paste them into the Connect Doctor on the dashboard. It tests the connection before it saves anything, and if a detail is wrong it names the field, so the classic mistake of pasting the game port instead of the RCON port is caught in seconds rather than discovered after an hour of nothing happening. The G-Portal setup page shows where each value lives.

On Nitrado there is nothing to copy. You approve Vantic on Nitrado's own consent page and pick your server from a list; the link renews itself. The Nitrado setup page walks through it. If a connection refuses to come up on either host, WebRCON not connecting lists the five causes and how to rule each one out.

Step 4: turn on the basics

Four things make a server feel alive on day one and take a minute each. Give the killfeed a channel, so every fight is posted the moment it happens. Set a channel for server-down alerts, so the first time your host restarts you are told what happened and whether you need to do anything. Ask players to link their gamertag to Discord with one command, which is what makes rewards, ranks and the store possible. And switch on your listing in the Rust Console server directory, so people looking for a server can find yours with live player counts.

Step 5: set your channels

Every feed goes to a channel you choose: the killfeed, wipe announcements, the offline-protection feed, raid alerts, the join-and-leave log, tickets. A sensible layout is one public channel for the things players enjoy, the killfeed and wipe news, and one staff channel for the things only admins need, alerts and logs. The dashboard's onboarding checklist tracks which of these are set and which are still waiting.

Step 6: then the features that keep players

With the basics live, the rest is about retention rather than setup. Offline raid protection is the single feature that most decides whether players stay after their first bad wipe, and players arm it themselves in game with two emotes. Kits bound to emotes hand out starter and VIP gear with a wave. The economy gives players a reason to log in daily. And the store on your own Stripe lets the server fund itself. None of these need to be on from day one; the Grow plan on the dashboard orders them for you.

The owner's checklist, in order

Before you start, have these three things open: your host panel, the Discord your community uses, and the Vantic dashboard. Then, in order: one, invite the bot to the Discord and give its role permission to see and post in the channels you will route feeds to, because a feed pointed at a channel the bot cannot post in simply stays silent. Two, sign in to the dashboard with Discord. Three, in the host panel copy the server IP, the RCON port and the RCON password, and on G-Portal check twice that it is the RCON port and not the game port next to it. Four, paste them into the Connect Doctor and wait for the test to pass; nothing saves until it does. Five, give the killfeed a channel and set a channel for server alerts. Six, post the link command in your Discord and ask players to link; five linked players is the point at which rewards, ranks and the store start to matter. Seven, turn on your directory listing. That is the whole first session, and it is usually done before the kettle boils.

Mistakes that cost owners an hour

The game port pasted where the RCON port goes is the classic. On G-Portal the two sit next to each other and look alike, and the result is a connection that never completes with no error from the game. The Connect Doctor catches it, but it is worth knowing why. A password with symbols that was copied with a trailing space is the second: it reads as a failed login, not a typo. A bot role without permission to post in a channel is the third; the bot is connected, the killfeed is on, and the channel stays empty. The fourth is only on hosts that move servers: after a migration the IP changes, and a bot pointed at the old one will retry forever. Vantic tells you when that has happened, and the fix is to paste the new IP in the Connection panel. If a connection still refuses, a bot that keeps disconnecting and WebRCON not connecting walk through every cause in order.

What a community assistant bot does all day

Owners sometimes search for a community assistant bot without knowing the name for what they want, and it is exactly this: the bot that handles the community side so the owner is not the help desk. It answers link requests, runs the ticket system so player reports stay private and organised, posts the feeds, hands out kits and rewards, runs events, and keeps the leaderboards honest. Set up once, it runs whether or not you are online, and it tells you when it needs you rather than making you check.

Frequently asked questions

Keep exploring

Rust Console servers for beginners · Rust Console bot for G-Portal · Rust Console bot for Nitrado · WebRCON not connecting · Rust Console bot with Australian support · the live network ladder