Skip to content
Mamba Host Docs

Rust Setup

Rust servers are CPU- and IO-intensive, so every plan runs on Dell PowerEdge R630 hardware (dual Intel E5-2680v4, 128 GB RAM, NVMe storage) with isolated cores, Oxide/uMod support, and automated wipe orchestration.

Before You Begin

Section titled “Before You Begin”
  • Decide wipe cadence (weekly/bi-weekly/monthly) and whether blueprint wipes follow the same schedule.
  • Prepare server.cfg, users.cfg, bans.cfg, and map seeds/custom maps (RustEdit .map files).
  • List plugins (Kits, Clans, Economics, AutoDoors, etc.) plus configuration files.
  • Optional: export analytics/Discord bots to log player stats or queue times.

Plan Sizing

Section titled “Plan Sizing”
Map SizePlayer TargetRecommended Plan
300050–100 playersStarter (≈6 GB RAM)
4000100–150 playersPro (≈8 GB RAM)
4500150–200 playersPremium (≈10 GB RAM)
5000+200+ playersPremium+ (12 GB+ RAM)

Upgrade when entity counts push frame time above ~16 ms or restarts take longer than a few minutes.

Provision the Server

Section titled “Provision the Server”
  1. Log into https://panel.mambahost.com → Create Server → Rust.
  2. Select plan/region and deploy (≈2 minutes).
  3. Copy RCON credentials from the console for RustAdmin/BattleMetrics.
  4. Enable backups and configure wipe schedule in the panel scheduler.

Configure Core Files

Section titled “Configure Core Files”
  • Download server.cfg (/home/container/server/rust/cfg/) and set hostname, description, URL, header image, and tags.
  • Set server.seed, server.worldsize, server.maxplayers, server.level, and server.headerimage via startup command or config.
  • Upload Oxide plugins (.cs) to /oxide/plugins/ and edit configs in /oxide/config/.
  • Schedule wipe tasks (map + blueprint) and broadcast countdown messages 60/30/15/5 minutes before the wipe using scheduler commands.

Performance & Maintenance

Section titled “Performance & Maintenance”
  • Limit entity counts: automate cleanups of dropped items, deployable spam, and stale bases using plugins like AutoPurge.
  • Run gc.collect or oxide.reload during off-peak hours to reclaim memory.
  • Back up world + player data before each wipe via panel snapshots.
  • Monitor CPU/RAM via panel graphs; correlate spikes with /oxide/logs/ errors or heavy plugins.
  • Use custom map sizes carefully—large maps drastically increase CPU/memory requirements.

Security & Stability

Section titled “Security & Stability”
  • Use strong RCON passwords distinct from panel credentials; rotate quarterly.
  • Install anti-cheat/anti-grief plugins (e.g., PlayerAdministration, AntiOfflineRaid).
  • Keep Oxide/uMod up to date. Apply updates during off-hours and restart once to load new hooks.
  • Store admin actions and player reports offsite for accountability (Discord webhooks, databases).

Operations

Section titled “Operations”
  • Publish wipe schedules on Discord/socials; automate announcements via n8n or bots.
  • Snapshot analytics after each wipe (population, queue times, revenue) for trend tracking.
  • Automate blueprint unlock giveaways or starter kits via scheduled commands.
  • Maintain staging/testing server for plugin updates before pushing to production.

Troubleshooting

Section titled “Troubleshooting”
  • High ping/lag: ensure plan matches map size/player count, remove heavy plugins, reduce server.worldsize, or lower entity limits.
  • Plugins fail to load: check /oxide/logs/Compiler/ for syntax errors or missing dependencies; update Oxide.
  • Crash after wipe: verify custom maps are not corrupt, regenerate from known seeds, or disable experimental monuments.
  • Players stuck on “Connecting”: confirm firewall ports (28015/28016) are open and upstream providers aren’t blocking UDP.
  • Blueprint wipe not running: ensure scheduler tasks use correct commands (e.g., bpwipe), and verify timezone alignment.
Section titled “Helpful Links”