Rust Dedicated Server Setup and Complete Oxide Plugin Configuration Guide

Rust has one of the world's most active hardcore sandbox PvP and server administrator communities. Unlike ordinary cooperative survival, Rust servers handle very frequent player data interactions, building decay (Upkeep), and periodic Wipes. A self-hosted dedicated server supports private group practice and survival, with Oxide / uMod plugins to extend gameplay freely. This article provides standard installation and routine operations guidance for Rust servers.

1. Server hardware baseline

2. Install the dedicated server with SteamCMD

Download the dedicated server anonymously through SteamCMD (AppID 258550):

steamcmd +login anonymous +app_update 258550 validate +quit

After the download, the main executable is in the root directory: RustDedicated.exe.

3. Network port planning

4. Startup arguments and server.cfg explained

Create a start_server.bat script:

@echo off
start RustDedicated.exe -batchmode ^
  +server.port 28015 ^
  +server.queryport 28017 ^
  +rcon.port 28016 ^
  +rcon.password "YourStrongRconPassword" ^
  +rcon.web 1 ^
  +server.hostname "LanGame Rust Dedicated" ^
  +server.identity "rust_instance_01" ^
  +server.maxplayers 30 ^
  +server.worldsize 3500 ^
  +server.seed 1337 ^
  +server.saveinterval 300 ^
  +server.globalchat true ^
  +server.description "Welcome to our Rust realm!"

Key arguments:

• +server.worldsize: Map size in meters (standard default 3500~4500).
• +server.seed: Procedural map generation seed; change it at a wipe to generate unique terrain.
• +server.identity: Instance identifier; saves, logs, and configuration folders are stored in server/<identity>/.
• +rcon.web 1: Enables the WebSocket RCON protocol, allowing modern web consoles such as RustAdmin to connect for administration.

5. Administrator permissions and periodic wipes

1. Grant administrator access

Enter these console commands to grant the highest administrator (Owner) permissions:

ownerid 76561198000000000 "AdminName"
server.writecfg

The command writes to server/<identity>/cfg/users.cfg automatically.

2. Standard wipe process

• Map Wipe: Stop the server, delete .map and .sav files under server/<identity>/, change +server.seed in the startup script, and restart to generate a new map.
• Full / Blueprint Wipe (BP Wipe): In addition to those files, delete the player.blueprints.*.db database files.

6. Choose an approach: manual configuration or LanGame Server Manager (LGSM)

Manual Rust maintenance requires frequent SteamCMD validation, remembering complex RCON ports, and writing scheduled wipe scripts.

We recommend the official open-source dedicated server management platform to automate routine administration:

• Tool overview and client: LanGame Server Manager (LGSM) product page
• Open-source repository: GitHub - SZSLGJCOM/LanGame-Server-Manager

LGSM features:

1. Automatic multiple-port and RCON configuration: Generates 28015/28016/28017 settings and an RCON key in one click, with direct interaction through the built-in web console.
2. Visual seed and map settings: Adjust map dimensions, seed, and multiplier rules directly in the interface without editing the command line.
3. Periodic Wipe assistant: Archives old save data and switches to a new seed in one click, automatically retaining or resetting player blueprints.
4. Server watchdog: Monitors process memory in real time and supports smooth restarts when nobody is online.