Rust Server Setup Guide: From Zero to a Modded Community Server

This is the map. Each stage below is a deliberate step with its own detailed guide — follow them in order and you'll end with a running, modded, admin-controlled server that shows up in the community browser.

Step 1 — decide: rent or self-host

For almost everyone, rent from a game host. You get a control panel, DDoS protection, and predictable cost. Self-host only if you already have an always-on machine with a strong single-thread CPU and good upload bandwidth. Either way, the software steps below are the same.

Step 2 — install the Rust dedicated server

The base game server installs via SteamCMD (app ID 258550). Game hosts do this for you. Self-hosting:

steamcmd +login anonymous +app_update 258550 validate +quit

Launch it once with an identity and ports to confirm vanilla works before adding anything:

RustDedicated.exe -batchmode +server.identity "myserver" \
  +server.port 28015 +server.queryport 28017 \
  +server.hostname "My RGZ Server" +server.maxplayers 100

Step 3 — install Carbon

With vanilla confirmed working, add the modding framework. Carbon is the recommended choice for new servers — see Carbon vs Oxide for why — and the install is a file extraction over the server root: how to install Carbon. Verify with c.version before moving on.

Step 4 — configure server.cfg

Now tune the server to feel the way you want — gather, decay, world size, performance. The convars that matter (and the ones host panels hide) are in the server.cfg settings reference. Don't over-tune on day one; get it running, then adjust between wipes.

Step 5 — add your admins

Grant yourself ownerid and your staff moderatorid, then — critically — run server.writecfg so it persists. Full steps: how to add admin to your Rust server.

Step 6 — install your first plugins

Drop .cs files into carbon/plugins/. A sane starter set for a community server: a teleport plugin, kits, an economy backbone, and — if PvE — a PvE manager and zone manager. Browse the plugin directoryfor tested options with Carbon compatibility verdicts and config examples. If a plugin won't load, you already know where to go: Carbon plugins not loading.

Step 7 — go live and verify

• Make sure ports 28015 (game) and 28017 (query) are open and the server isn't private.
• Set a hostname, description, and header image so it looks legitimate in the browser.
• Connect from another machine via the community list to confirm it's visible.
• Validate every plugin config — our config validator catches broken JSON before it costs you a load.

Step 8 — the monthly maintenance loop

A server isn't set-and-forget. Every first Thursday: update the game, update Carbon (guide), update any plugins that broke, spot-check in-game. Build that habit and your server is the one that's up when players log in for fresh map — which is how servers actually grow.