Rust is one of the most rewarding games to host — and one of the more demanding. Here's the honest path from empty plan to a running, modded, regularly-wiped server.
Step 1 — Vanilla or modded?
Decide early, because it shapes everything else:
- Vanilla — pure Rust, no plugins. Simplest to run and the most "official" experience.
- Modded — you add a plugin framework and customise nearly everything (kits, gather rates, events, anti-cheat helpers). Two frameworks dominate: Oxide/uMod (the long-standing standard, huge plugin library) and Carbon (a newer, performance-focused framework that's largely Oxide-plugin-compatible).
Step 2 — Size your RAM
Rust is memory-hungry and a big map plus population is the main driver:
- 4 GB — a small vanilla server / small map with a handful of friends.
- 6–8 GB — a typical modded server, default map size, 30–60 players.
- 10 GB+ — large maps, heavy plugin stacks, big populations.
Map size matters as much as player count. A 4500-size map uses far more RAM than a 3000 one, regardless of how many people are on. If you're unsure, start smaller and scale — our plans upgrade in place.
Step 3 — Deploy on the panel
- Order a Rust plan and pick Rust at checkout.
- Your Pterodactyl panel login arrives by email within minutes.
- In the panel, set your server name, map size/seed and max players in the startup variables, then start it.
Step 4 — Install Oxide/uMod or Carbon
You have full file access , so modding is straightforward. Many Rust eggs let you flip a startup variable to auto-install Oxide or Carbon on boot; otherwise upload the framework files into your server directory and restart. Once it's loaded, drop plugin .cs files into the oxide/plugins/ (or carbon/plugins/) folder — they compile on the fly. Edit configs under oxide/config/ and reload with the console.
Step 5 — Wipes & scheduling
Rust servers "wipe" (reset the map and/or blueprints) on a schedule — weekly or biweekly is common. You're in full control: use the panel's scheduled tasks to automate restarts, and run map/blueprint wipes from the console or by clearing the relevant save files on your chosen cadence. Announce your wipe schedule to players — it's part of how Rust communities are advertised.
Step 6 — RCON & admin
The Pterodactyl panel gives you the live console (RCON) for commands like say, ban, and plugin reloads. Add yourself as admin via ownerid in the console, and you can manage the server live or remotely with any RCON tool.
Our Rust servers run on SSD storage on dedicated single-tenant bare metal with DDoS protection and daily backups, from €4.99/mo — see the Rust hosting page. Setup is automated; you're modding within minutes.
FAQ
How much RAM does a Rust server need?
4 GB for a small vanilla server, 6–8 GB for a typical modded server with 30–60 players, and 10 GB+ for large maps and heavy plugin stacks. Map size drives RAM as much as player count.
Oxide/uMod or Carbon — which should I use?
Oxide/uMod has the largest plugin library and is the safe default. Carbon is newer, performance-focused, and runs most Oxide plugins. You can try either with full file access; many people start on Oxide.
How do I wipe my server?
Schedule restarts and wipes from the panel, or clear the map/blueprint save files from the console/file manager on your chosen cadence (weekly/biweekly is common). You control it fully.
Do I get RCON access?
Yes — the panel includes the live server console (RCON), and you can connect external RCON tools too. Add yourself as admin with ownerid.
Originally published at overnight.host. We run a small, honest hosting company on dedicated bare metal — Linux & Windows VPS, game servers, web hosting. Live status at up.overnight.host.
Top comments (0)