How to Choose a Rust Console Server Bot: The Features That Actually Matter

On console, the bot is the whole toolbox

On console there are no add-ons to install, so running a server is refreshingly self-contained. There is nothing to sideload and nothing to break on patch day. Everything happens through two things working together: your native server settings and a bot.

Here is how they split the work. A bot connects to your server over WebRCON and runs the same admin commands you would enter by hand through the host panel, just faster and around the clock. The native server settings handle the heavy lifting for you, things like PvP toggles, gather scale, decay, and blueprint unlocks. The bot handles everything live: kills, kits, events, bans, and payouts. That is why the bot you pick matters so much. It is not an add-on. It is the platform your whole server runs on.

Must-have #1: it comes back on its own after a patch

Rust gets patched constantly, and the official console hosts reboot your server automatically when Facepunch ships an update. Every reboot drops the WebRCON connection. The question that separates a good bot from a bad one is simple: what happens in the next 60 seconds?

A good bot notices the drop and reconnects on its own, quietly, without you doing anything. A bad one sits there dead until you log into a dashboard and click reconnect, and it often lies about it, showing a green 'online' light while your killfeed and store deliveries have silently stopped. That failure always seems to land at the worst possible moment, in the first 24 to 48 hours after a Thursday wipe when your population and your donations both peak.

Before you commit to anything, read up on what causes a bot that keeps disconnecting and confirm the one you choose reconnects automatically and reports its status honestly. Auto-reconnect plus an honest live status is the single most important thing on this entire list. Nothing else matters if the bot is not actually connected.

The rest of the must-have list

Once reliability is handled, here is the short list every console server actually needs. If a bot is missing any of these, keep looking.

A live killfeed. Console has no built-in feed of who killed who, so the bot reads it off the server and posts it. It is the heartbeat of your Discord and the first thing players check. A good killfeed can also hand out kill rewards, which feeds straight into the rest of your economy.

Kits with emote binds. Players claim a kit by typing a command or doing an in-game emote, and the bot delivers the gear instantly. This covers your starter kit, your VIP kit, and your event loot.

Offline raid protection. This is the feature that keeps casual players from quitting. When a base owner logs off, their zone gets protected so they do not return to a floor of loot. On console this is done with an offline raid protection system that seals the base while the owner is away and opens it back up when they return. It is close to mandatory on any PvP server that wants a population past week one.

Role-based command permissions. Not everyone should be able to ban a player or spawn a helicopter. A proper bot lets you decide which Discord roles can run which commands, so your moderators get exactly what they need and nothing more. Pair that with a ticket system and your admin team can run itself.

Transparent store fees. If you plan to take donations, the cut the bot takes is real money out of your pocket every single month. That one deserves its own section, because it is where owners quietly lose the most.

The store fee is the number that quietly costs you the most

Here is the part almost nobody checks until it is too late. On console, real-money sales work one way: players pay on a simple web store, and your bot delivers the purchase in game automatically over WebRCON. Separately, an in-game Kit Vending Machine can sell kits for an in-game currency item, but that is play money. The web store is where real dollars come in.

Now the math. Say your server takes $1,000 a month in donations, which is very reachable on a healthy wipe cycle. A bot that runs a flat 3% real-money store lets you keep the rest and pay out on your own Stripe account, so you are out about $30 a month. A bot that takes a 20% cut costs you $200 a month for the exact same sales. Over a year that is $360 versus $2,400. Same players, same purchases, and the only difference is which bot you picked on day one. Vantic runs a flat 3% on the owner's own Stripe for exactly this reason. A low, transparent fee belongs on the must-have list, not the nice-to-have list.

Two rules keep you out of trouble no matter which bot you use. Keep everything you sell non-combat, so you never trigger pay-to-win backlash or a delisting. And never sell DLC or skins to players who do not own them, which a Facepunch rule from August 2025 specifically bans. Priority queue, colored names, custom tags, and kits of common gear are all fine. Selling anything that wins fights is not.

The nice-to-haves that make a server feel premium

These will not make or break your server, but they are what separate a server that feels thrown together from one that feels run by someone who cares. Add them once the must-haves are solid.

Leaderboards turn your killfeed data into competition, showing top killers, most farmed, and longest kill, and they give players a reason to keep grinding. A battle pass or seasonal progression gives returning players a track to chase every wipe, which is one of the strongest retention tools on console. A live map and radar let admins watch the action and catch cheaters. A server directory listing helps new players actually find you, which matters because the in-game community browser is crowded and unforgiving. And a web dashboard ties everything together so you can run the server from a browser instead of memorizing commands.

Pick the ones that fit your server's personality. A hardcore PvP server leans on leaderboards and raid alerts. A community PvE server leans on kits, events, and economy. You do not need all of it on day one, but you want a bot that can grow into all of it, so you never have to switch platforms just to add a feature later.

How to test a bot in ten minutes before you commit

You can judge most of this before you pay for a full month. Here is a quick shakedown.

First, connect it. On G-Portal you plug in your server IP, your RCON port, and your RCON password. That RCON port is not your game port. The game runs on 28015 over UDP, while WebRCON usually lives on 28016 over TCP, and mixing them up is the number one reason people see 'players can join but the bot will not connect.' Some hosts also need rcon.web set to 1. On Nitrado it is easier: a good bot links your account in one click and pulls the connection details for you, with no IP or password to copy by hand.

Second, make a kill and watch for the feed. If the killfeed shows up within a few seconds, the read path is working. If the bot connects but no killfeed ever appears, that tells you something about how well it is actually reading the server.

Third, and this is the real test, force a reboot or wait for the next server restart and see what the bot does. If it reconnects on its own within a minute, you found a keeper. If you have to log in and reconnect it by hand, picture doing that at 6pm on wipe day with 80 players waiting. That one test predicts your next six months.

How to pick once and never migrate

Migrating bots mid-season is miserable. You lose your kit configs, your store products, your player data, and usually a chunk of a wipe while you rebuild everything. The entire point of choosing carefully now is that you only do this once.

So score it simply. Does it reconnect on its own and tell the truth about its status? Does it cover the five must-haves: killfeed, kits, offline raid protection, role permissions, and a low, transparent store fee? Can it grow into the nice-to-haves without you switching platforms later? If the answer to all three is yes, you have found your bot.

If you want a shortcut, our breakdown of the best Rust Console bot options walks through this same checklist against what is actually available, so you can match features to your server type in a few minutes. Pick the one that clears the must-haves, and you will never have to think about this decision again.

Frequently asked questions

Keep reading

the best Rust Console bot comparison · why a Rust Console bot keeps disconnecting · the flat 3% Rust Console server store · offline raid protection settings · fixing WebRCON not connecting