How to Start a Rust Server: Step-by-Step Guide

Step 1: Start Your Rust Server

In your Zeros Host panel, create a new server and select Rust. You will be prompted to choose a map size (common sizes are 2000 to 4000: smaller maps suit low player counts, larger maps suit 50+ players) and a seed (an integer that determines the procedural map layout). Click Start. The server downloads assets on first boot, which can take a few minutes. Watch the console for the line Server startup complete before connecting.

Step 2: Configure server.cfg

Your main server configuration lives at server/<identity>/cfg/server.cfg. Open it in the panel file manager or Browser IDE. Key settings to set on a fresh server:

server.hostname "My Rust Server"
server.description "2x gather, active admins. Wipes first Thursday."
server.maxplayers 50
server.worldsize 3500
server.seed 12345

# Decay -- 1.0 is default, 0.5 halves decay rate, 0 disables it
decay.scale 0.5

# Server tag for in-game browser filtering
server.tags "monthly,vanilla,NA"

Save and restart the server. The hostname and description appear in the in-game server browser within a minute of restart.

Step 3: Install Oxide or Carbon for Plugins

Both Oxide and Carbon are supported on Zeros Host Rust servers. In the panel, find the Mod Manager or the dedicated Oxide/Carbon install option. You only need one framework. Oxide is more established with a larger plugin library; Carbon has better performance characteristics and active development. Either works for a standard Rust server.

After the server restarts with Oxide loaded, you will see [Oxide] lines in the console confirming it is active.

Step 4: Install Plugins

With Oxide or Carbon installed, upload plugin files (.cs) to oxide/plugins/ or carbon/plugins/. Use the panel file manager to drag and drop .cs files directly, or use the Mod Manager to search uMod by plugin name and install without leaving the browser. Common starter plugins include Clans, Economics, NoDecay, and GatherManager.

After uploading, the plugin loads automatically without a server restart (hot-load). Check the console for the load confirmation line.

Step 5: Set Up RCON

RCON lets you run console commands remotely without being in-game. Add these lines to server.cfg:

rcon.password "yourpassword"
rcon.port 28016
rcon.web 1

Restart after saving. Test RCON by sending the command 'server.hostname': it should return your configured server name.

Step 6: Force Wipe Day

Rust force wipes happen on the first Thursday of every month, when Facepunch pushes a mandatory update. On this day: wait for Facepunch to release the update (usually early afternoon UK time), update your server binary via the panel, wipe the map by deleting the server/<identity>/ save files or using the panel wipe function, optionally set a new seed in server.cfg, and restart. Note: automatic wipe scheduling is on our roadmap but is not a current feature: wipes are a manual action.

Step 7: Managing Players

Give yourself owner access by adding your Steam64 ID to server.cfg. Common admin commands work from both RCON and the panel console directly:

# In server.cfg
ownerid 76561198000000000 "YourName" "owner"

# Via RCON or panel console
kick <steamid> "reason"
ban <steamid> "reason"
server.save    # force a save