Rust Server Administration: A Complete Beginner’s Guide

So you’ve bought your first Rust dedicated server. The panel is staring at you, the server is running, and you have no idea where to begin. This guide walks you through everything — from first boot to a server your friends (or the public) will actually want to play on.

First Boot: Essential Configuration

When your Rust server starts for the first time, it generates a world and default configuration. Before inviting anyone, you’ll want to adjust the basics.

server.cfg

Your main configuration file. Here are the critical settings:

server.hostname "Your Server Name"
server.description "A short description of your server"
server.headerimage "URL to your server banner image"
server.url "Your website or Discord URL"
server.maxplayers 50
server.worldsize 3000
server.seed 12345
server.saveinterval 300

Key decisions:

• server.worldsize: Map size in meters. 3000 is small and action-packed. 4000-4500 is the sweet spot for most community servers. 6000 is huge and can feel empty without many players. Match your map size to your expected player count.

• server.seed: Determines map layout. Each seed produces a unique map with different monument placements, terrain, and biomes. Use rustmaps.com to preview seeds before committing. A bad seed (all monuments clustered together, or a map with poor resource distribution) will hurt your server more than bad settings.

• server.maxplayers: Set this realistically. A 100-slot server with 5 players looks dead. A 50-slot server with 30 players looks active. Start smaller and increase as your population grows.

• server.saveinterval: How often the world saves, in seconds. 300 (5 minutes) is standard. Lower means less data loss on crashes but more disk I/O.

Performance Settings

fps.limit 30
physics.steps 32
decay.scale 1.0
stability.strikes 10

• fps.limit: Server tick rate. 30 is standard for Rust. Don’t increase this — it won’t make the game smoother and will consume more CPU.
• decay.scale: Controls building decay rate. 1.0 is default. Set to 0 to disable decay entirely (only for private servers — public servers will run out of memory without decay).

Understanding Wipe Schedules

Wipes are the heartbeat of Rust. Understanding them is critical for running a successful server.

Forced Wipes

Facepunch (Rust’s developer) forces a map wipe on the first Thursday of every month. Every server, no matter what, resets its map on this day. This is tied to the monthly update patch.

Some monthly updates also force a blueprint wipe, meaning players lose their learned blueprints. Facepunch announces these in advance, but they happen a few times per year.

Voluntary Wipes

Between forced wipes, you decide your own wipe schedule. Common patterns:

• Weekly (Thursday): Most common for competitive and high-pop servers. Keeps things fresh and attracts players who want a level playing field.
• Biweekly: Good balance between freshness and allowing longer-term building projects.
• Monthly (forced wipe only): Best for casual, PvE, or roleplay servers where players want to invest time in their bases.

Your wipe schedule is a core part of your server’s identity. Players choose servers based on wipe cycles. Decide early and stick to it — changing your wipe schedule confuses and frustrates your player base.

Blueprint Wipes

Separate from map wipes, blueprint wipes reset players’ learned blueprints. Options:

• Wipe BPs with every map wipe: Forces players to re-progress each wipe. More competitive, attracts hardcore players.
• Keep BPs between wipes: Lets returning players skip early-game grind. More casual-friendly.
• Wipe BPs monthly (on forced wipe): A middle ground used by many community servers.

Plugins with Oxide/uMod

Rust’s plugin ecosystem runs on Oxide (now maintained as uMod). Plugins dramatically expand what your server can do.

Installing Oxide

1. Download the latest Oxide build for your Rust server version from umod.org
2. Upload the Oxide files to your server’s root directory, overwriting existing files
3. Restart the server
4. You’ll see an oxide/ folder created with plugins/, config/, data/, and logs/ subdirectories

Many hosting providers, including Witchly, offer one-click Oxide installation through the server panel.

Essential Plugins for Community Servers

Here are plugins that most community servers should consider:

Administration:

• Vanish: Lets admins go invisible to monitor players without being detected
• AdminRadar: Shows player positions, stashes, and tool cupboards to admins
• Better Chat: Customizable chat with groups, colors, and formatting
• Discord Messenger: Sends server events to your Discord

Quality of Life:

• Gather Manager: Adjust resource gathering rates (2x, 3x, etc.)
• Quick Smelt: Speed up smelting in furnaces
• Backpacks: Give players expandable inventory
• NTeleportation: Adds /home, /tpr (teleport request), and /town commands
• Kits: Starter kits and VIP kits

Anti-Cheat and Moderation:

• Rust:IO or RustMaps: Live map for players
• Clans: Formal clan/team system
• Admin Deep Cover: Advanced spectating tools

Plugin Performance Warning

Every plugin consumes resources. More plugins means more CPU and RAM usage, and potential conflicts between plugins. Follow these rules:

1. Only install plugins you actually need
2. Test new plugins one at a time
3. Monitor server performance after adding plugins
4. Keep plugins updated — outdated plugins cause crashes
5. Remove plugins you’re not using rather than just disabling them

RCON: Remote Console Access

RCON (Remote Console) lets you run server commands without being in-game. It’s essential for server administration.

Setting Up RCON

In your server startup parameters, ensure RCON is configured:

+rcon.web 1
+rcon.port 28016
+rcon.password "your_secure_password_here"

Security warning: Use a strong, unique password. RCON gives full server control — anyone with access can wipe your server, ban everyone, or worse. Never share your RCON password, and change it if anyone who had access is no longer trusted.

RCON Tools

• RustAdmin: Desktop application for Windows. The most popular option with a GUI for player management, console commands, and server monitoring.
• WebRCON: Browser-based RCON client. Lighter weight, works from any device.
• rcon.io: Web-based tool, convenient for quick commands.

Useful RCON Commands

status                          # Show connected players
kick "playername" "reason"      # Kick a player
ban "playername" "reason"       # Ban a player
unban "steamid"                 # Unban by Steam ID
say "message"                   # Send server-wide message
server.save                     # Force save
server.writecfg                 # Write config to disk
oxide.reload PluginName         # Reload a specific plugin
inventory.give "name" item qty  # Give items to a player

Performance Tuning

Rust servers are resource-hungry. Here’s how to keep things running smoothly.

Hardware Requirements

For a Rust server, expect to need:

Players	RAM	CPU	Map Size
10-25	6-8 GB	High clock speed	3000
25-50	8-12 GB	High clock speed	3500-4000
50-100	12-16 GB	Dedicated high-perf	4000-4500
100+	16+ GB	Premium tier	4500+

Rust is heavily CPU-dependent. Clock speed matters more than core count.

Entity Count Management

Entities (placed objects, resources, animals, dropped items) are the primary driver of server lag. A typical Rust server with 50 active players can accumulate hundreds of thousands of entities.

Keep entity counts under control:

• Enable building decay (don’t set decay.scale to 0 on public servers)
• Set reasonable building limits via plugins
• Clear dropped items periodically
• Use plugins that automatically remove abandoned structures

Garbage Collection

Rust’s server process can consume large amounts of memory. Monitor memory usage and restart the server if it approaches your allocation limit. Many admins schedule a restart during low-population hours (typically 4-6 AM).

A common pattern:

• Restart every 12-24 hours during active wipe cycles
• Restart daily during quieter periods

Announce restarts 10-15 minutes in advance so players can find a safe spot.

Network Considerations

Rust requires good network connectivity. High-ping players experience rubber-banding and hit registration issues. If possible, choose a server location close to your target player base.

Managing Your Community

Technical setup is only half the battle. A Rust server lives or dies by its community.

Rules

Post clear rules and enforce them consistently. Common rules include:

• No cheating/hacking
• No racism or hate speech in chat
• No exploiting game bugs
• Specific raiding rules (if applicable — offline raid protection, raid times, etc.)
• Group size limits (solo/duo/trio servers are popular for a reason)

Staff

As your server grows, you’ll need help. Recruit moderators from your active player base — people who play regularly and demonstrate maturity. Give them the minimum permissions they need (kick, mute, teleport for investigation) and escalate bans to senior admins.

Never give RCON access to moderators. RCON is admin-only.

Handling Cheaters

Rust has a cheating problem. Your tools:

• EAC (Easy Anti-Cheat): Runs automatically. Catches most public cheats.
• Server-side anti-cheat plugins: Complement EAC with plugins that detect suspicious behavior
• Admin spectating: Use Vanish and spectate mode to investigate reports manually
• Combat log review: Rust logs combat interactions. Review these when players report suspicious deaths.

Ban swiftly when evidence is clear. Document bans (Steam ID, reason, evidence) in case of disputes.

Getting Started on Witchly

Witchly’s Rust hosting runs on dedicated hardware with high-clock-speed CPUs — the resource profile that Rust demands. Our panel supports one-click Oxide/uMod installation, automated backups before each wipe, and RCON access out of the box.

You get full SFTP access for plugin management, real-time resource monitoring to keep tabs on entity counts and memory usage, and the ability to scale your plan up as your population grows.

New to Rust server hosting? Sign up at Dashboard and deploy a free server to experiment with the settings, plugins, and configuration covered in this guide — no payment required.

Summary

Running a Rust server is more involved than most games, but the reward is a thriving community built around your vision. Start with the basics — good configuration, a clear wipe schedule, essential plugins — and grow from there. Don’t try to install 50 plugins on day one. Get the fundamentals right, attract a small core player base, and iterate based on what your community actually wants.