Rust needs a strong machine: plan on at least 8 GB of RAM for a standard map with few players, and 12 to 16 GB for a large map, many players or many plugins. The first start takes several minutes while it generates the map.
1. Download it with SteamCMD
With SteamCMD installed:
# Windows
C:\steamcmd\steamcmd.exe +force_install_dir C:\rust +login anonymous +app_update 258550 validate +quit
# Linux (as the steam user)
~/steamcmd/steamcmd.sh +force_install_dir ~/rust +login anonymous +app_update 258550 validate +quit
2. The start script
Windows: create C:\rust\start.bat:
@echo off
cd /d C:\rust
:start
RustDedicated.exe -batchmode -nographics +server.port 28015 +server.queryport 28017 +rcon.port 28016 +rcon.web 1 +rcon.password "CHANGE_THIS" +app.port 28083 +server.hostname "My Rust server" +server.identity "myserver" +server.level "Procedural Map" +server.seed 12345 +server.worldsize 3500 +server.maxplayers 50 +server.saveinterval 300 -logfile server.log
goto start
The goto start restarts it if it crashes. To stop it for good, close the window.
Linux: create ~/rust/start.sh and make it executable with chmod +x ~/rust/start.sh:
#!/bin/bash
cd "$(dirname "$0")"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$(pwd)/RustDedicated_Data/Plugins/x86_64"
exec ./RustDedicated -batchmode -nographics \
+server.port 28015 +server.queryport 28017 \
+rcon.port 28016 +rcon.web 1 +rcon.password "CHANGE_THIS" \
+app.port 28083 \
+server.hostname "My Rust server" +server.identity "myserver" \
+server.level "Procedural Map" +server.seed 12345 +server.worldsize 3500 \
+server.maxplayers 50 +server.saveinterval 300 \
-logfile server.log
Run it in a screen session or as a service.
What each one does
| Parameter | What for |
|---|---|
server.identity | Name of the folder where everything is saved (server/myserver) |
server.seed / server.worldsize | Map seed and size (1000 to 6000). Bigger means more RAM |
server.maxplayers | Players at once |
server.saveinterval | How often it saves, in seconds |
rcon.password | Remote console password. Make it long and do not share it |
3. Open the ports
At least 28015 UDP (game) and 28017 UDP (to appear in the browser). Commands and details in the Rust ports guide.
4. Make yourself admin
Find your SteamID64 (the 17-digit number of your Steam profile) and type in the server console or over RCON:
ownerid YOUR_STEAMID64 "YourName"
server.writecfg
Rejoin the server and you will have permissions. For RCON, tools such as RustAdmin connect to YOUR_IP:28016 with the rcon.password; open that port on TCP only if you use it from outside.
5. Plugins with Oxide (uMod)
- Stop the server.
- Download Oxide for Rust from
umod.org/games/rust(there are Windows and Linux builds). - Extract the .zip into the server folder, overwriting when asked.
- Start it. An
oxidefolder appears: plugins (.cs) go inoxide/pluginsand load by themselves, no restart needed. Their settings live inoxide/config.
The most popular alternative is Carbon, compatible with most Oxide plugins.
6. The monthly forced wipe
Facepunch releases a mandatory update on the first Thursday of every month, around 19:00 UK time. That day:
- Stop the server and update it with the same SteamCMD command. Until you do, nobody with the updated game can join.
- Reinstall Oxide (or Carbon): the update overwrites its files and, without reinstalling, plugins do not load.
- That update brings a map wipe: the server starts a new map. Many take the chance to change
server.seed. Learnt blueprints are kept unless Facepunch announces otherwise or you wipe them yourself.