Blog archive
Popular blog tags

Rust Private Servers: The Practical, No-Drama Guide

Saturday, November 1, 2025

Public Rust can be chaos—cheaters, queue times, random wipes, and rules that change overnight. A private Rust server gives you control: your map, your rates, your rules, your community. This guide covers hosting choices, performance tuning, plugins (uMod/Oxide), wipe strategy, and a simple maintenance routine you can copy-paste.

Want it done for you? Launch a ready-to-play Rust server here: Get a Rust server.
Curious who’s behind it or need other services? alejandro7.com.

Why Run a Private Rust Server?

  • No strangers, no drama – curate your Discord and keep the vibe consistent.

  • Custom gameplay – gather rates, stack sizes, kits, TP rules, map size/seed, monument spawns, vehicles, and more.

  • Predictable wipes – schedule wipes when it suits your community (and control BP vs. map wipes).

  • Performance – tune entities, plugins, and restart windows for buttery combat and building.

Hosting Options (Pick Your Path)

1) Managed Hosting (easiest)

  • Provision in minutes with a control panel (one-click restarts/updates/backups, uMod install, workshop maps).

  • Support on patch day when plugins break.

  • Perfect if you want to play, not babysit Linux services.
    👉 Get a Rust server

2) Self-Hosting (advanced)

  • Rent a VPS/dedicated box or use a home server.

  • Install SteamCMD, open ports, run RustDedicated as a service, wire RCON, automate backups and restarts.

  • Full control—also full responsibility on patch day.

The Essentials You’ll Touch

  • RustDedicated + server.cfg – Boot flags and CVar settings live here.

  • uMod/Oxide – Plugin framework (timed rewards, kits, economy, TP, admin tools, QoL).

  • RCON – Remote console via tools like RustAdmin or BattleMetrics RCON.

  • Backups & Wipes – Save rotations and a clear wipe policy (map, BPs, or both).

Fast Start (Managed)

  1. Pick a location close to your players.

  2. Name your server, set the admin (ownerID) and a strong RCON password.

  3. Choose rates (2x/3x?), map size (3–4k for 50–100 players), and seed.

  4. Add core plugins (below).

  5. Set scheduled restarts (e.g., daily off-peak).

  6. Share IP:Port + name; pin rules and wipe cadence in Discord.
    👉 Launch now: Get a Rust server

DIY Setup Cheatsheet (Self-Host)

Install & Update

  • Install SteamCMD → app_update 258550 -beta none validate for RustDedicated.

  • Create a service (systemd/Windows service) to auto-start and restart on crash.

Typical start command

 
RustDedicated -batchmode -nographics \ +server.hostname "My Private Rust" \ +server.port 28015 \ +rcon.port 28016 +rcon.password "CHANGE_ME" +rcon.web 1 \ +server.maxplayers 50 \ +server.identity "myserver" \ +server.level "Procedural Map" +server.seed 12345 +server.worldsize 3500 \ +server.saveinterval 300 \ -logfile "server.log"

Firewall/Ports

  • Open game port (e.g., 28015/UDP) and RCON (e.g., 28016/TCP).

  • If you set a query port, open that too.

uMod/Oxide

  • Install uMod so /oxide/plugins loads community plugins.

  • Keep a text list of plugins + versions for quick rollback.

RCON

  • Use RustAdmin/BattleMetrics RCON to watch logs, kick/ban, run commands, schedule messages.

Plugin Shortlist (Stable, Player-Friendly)

  • Admin/QoL

    • Admin Radar / PlayerDatabase – visibility and tracking for staff.

    • Stack Size Controller – bigger stacks reduce entity count and lag.

    • Auto Purge (inactive bases) – keeps entity count sane over time.

  • Gameplay

    • Kits – starter and donor kits (if applicable).

    • ZLevels Remastered – gentle progression for gather/craft.

    • BetterLoot / 2x–3x Gather – speed up early game without destroying balance.

    • NTeleportation – home/outpost/bandit TP with cooldowns to preserve PvP flow.

    • Rust Rewards – playtime or action-based rewards economy.

    • Vanish (admins) – investigate without interference.

  • Community

    • Discord Connect – link in-game chat to Discord.

    • Rules/Info GUI – show rules on first join and after wipes.

Add plugins incrementally: one at a time → restart → test → scan logs for errors.

Performance That Actually Feels Good

  • Hardware

    • Prioritize high single-core clock; Rust is sensitive to main thread time.

    • NVMe SSD for world saves; avoid HDDs.

    • RAM: 8–16 GB for modded medium servers; add headroom for entity-heavy builds.

  • World Settings

    • Worldsize 3000–3500 for 50–100 players; larger costs CPU and travel time.

    • Tune animal/scientist counts; excessive AI spikes server time.

    • Use stack size and purge to keep entity counts down.

  • Operational

    • Daily restart off-peak (memory and plugin GC stay fresh).

    • Watch entity count and server FPS; address lag before players complain.

    • Keep plugin count lean; remove anything nobody uses.

Wipe Strategy (Map vs. Blueprints)

  • Map wipe – resets bases and monuments; keeps BPs (optional).

  • BP wipe – resets researched items; great for fresh seasons.

  • Cadence – many communities do biweekly map wipes and monthly BP wipes; adjust to your group.

  • Patch day – plan your wipe window around the monthly game updates so you aren’t fighting hotfixes mid-cycle.

Tip: Post wipe dates at the top of your Discord and MOTD. Consistency = happier players.

Security & Moderation

  • EAC enabled (default). Don’t disable it.

  • Strong RCON password; restrict RCON to specific IPs if possible.

  • Use ownerID for the head admin; give moderatorID sparingly.

  • Keep an appeals channel in Discord with one-message, one-decision rules to avoid drama.

  • Log moderation actions.

Rust+ & Quality-of-Life

  • Enable Rust+ so players can pair the companion app with your server.

  • Scheduled in-game announcements (restart warnings, wipe countdowns).

  • Map link and Discord invite in your server’s description.

Maintenance Ritual (Copy/Paste)

  • Daily: auto-restart, quick log skim for red errors, check server FPS/entity count.

  • Every wipe: snapshot backup before wipe, test post-wipe spawn points and starter kits.

  • Patch day: announce downtime → backup → update server → update uMod & plugins → test with an admin alt → reopen.

  • Monthly: prune unused plugins, audit permissions, review feedback.

Troubleshooting Quick Wins

  • “Packet Flooding/Timer late/lag spikes” → check plugin loops, reduce AI, entity cleanup, confirm CPU isn’t pegged.

  • Players can’t connect → verify ports, correct IP:Port, RCON not blocking, server list visibility may lag—have them direct connect.

  • Plugin stopped working after update → update plugin, read issue tracker, temporarily disable to restore stability.

  • High entity count → enable purges, increase decay slightly, consider stack size increases, encourage smaller bases.

FAQ

How many slots can I run?
Depends on CPU and plugins. A well-tuned midrange CPU with lean plugins can handle 50–100 players smoothly. Heavy modpacks or huge maps need more muscle.

Do I need daily restarts?
Highly recommended. Memory, plugins, and entity churn all benefit from a clean slate.

Can I move my server later?
Yes. Copy the identity folder (saves/configs) and keep plugin versions aligned. Test on a staging instance first.

How big should my map be?
3k–3.5k is a sweet spot for mid-sized communities. Larger maps look cool but punish performance and travel time.

Ready to Build Your Own Rust Community?

Skip the sysadmin grind and start playing today:

👉 Get a Rust server

Need broader help (site, Discord, branding, integrations)?

👉 alejandro7.com

Set your rules, tune your rates, pick your map—and keep the wipes on your schedule. See you on the shore. 🛶🔧

Leave your comment
*