Running a 200+ player Rust server is one of the hardest challenges in game server hosting. Here's what it takes to pull it off without turning into a lag fest.
Hardware Requirements
For 200 players, minimum viable specs:
- CPU: Ryzen 9 7950X3D or equivalent (single-thread performance is everything)
- RAM: 24-32GB (16GB minimum, but you'll regret it)
- Storage: NVMe SSD with at least 150GB free (worlds grow fast)
- Network: 1Gbps with low latency to your player base
On Space-Node, the Building Plan (24GB, €30.90/mo) or Hammer (32GB, €41.80/mo) plans are designed for this scale.
Server Configuration
server.cfg Essentials
server.maxplayers 250
server.worldsize 4250
server.saveinterval 300
decay.scale 1.0
ai.think 1
ai.move 1
fps.limit 30
Map size: 4250 is the sweet spot for 200 players. Smaller maps concentrate players for more PvP, larger maps spread them out. Going above 4500 adds entity load without proportional benefit.
Save interval: 300 seconds (5 minutes) balances data safety with performance. Each save causes a brief lag spike - less frequent saves mean fewer interruptions.
Entity Management
Entities are the primary performance killer. On a 200-player server, you might have:
- 200+ player entities
- 5,000-20,000 building entities (walls, foundations, doors)
- 500-1,000 deployable entities (furnaces, boxes, sleeping bags)
- Hundreds of animal entities
- Loot spawns, ore nodes, vehicles
Decay Optimization
decay.scale 1.0
Keep decay at 1.0 or slightly above. Without decay, abandoned bases accumulate and entity count grows forever. Some large servers use decay.scale 1.2 to accelerate cleanup.
Animal Population
spawn.min_rate 0.3
spawn.max_rate 0.5
Reduce animal spawn rates. Animals have relatively expensive AI pathfinding. On a 200-player server, players generate enough activity - wildlife is secondary.
Oxide Plugin Optimization
Popular plugins with performance considerations at scale:
Gathering plugins (QuickSmelt, GatherManager): Generally safe. Minimal per-tick overhead.
Building plugins (RemoverTool, BuildingGrades): Safe if well-coded. Check that they don't scan entities unnecessarily.
Economy/Shop plugins: Database writes can cause tick lag. Use async database operations (MySQL over SQLite at this scale).
Anti-cheat: Essential but expensive. Profile their overhead with Oxide's profiling tools and choose lightweight options.
Teleport plugins: The teleportation itself isn't expensive, but cooldown tracking and pending teleport checks can add up at 200 players.
Plugin Profiling
Install Oxide's profiler:
o.profiler.start
(wait 2 minutes)
o.profiler.stop
o.profiler.dump
This shows exactly how many milliseconds each plugin consumes per tick. Remove or replace anything consuming more than 2ms average.
Monitoring
Essential Metrics
perf 1 # Enable performance monitoring
Watch for:
- Server FPS: Target 25-30. Below 20 means optimization needed.
- Entity count: Plot over time. Exponential growth means decay isn't working.
- Memory usage: Should stabilize, not continuously grow.
- Network out: High values indicate entity synchronization issues.
Wipe Day Preparation
Wipe day combines two expensive operations: world deletion and new world generation. For a 200-player server:
- Announce maintenance window (15-30 minutes)
- Stop the server
- Delete map files (keep player data if BP wipe isn't happening)
- Pre-generate the map if using a custom seed
- Start server
- First 30 minutes will be rougher than normal as the map generates around spawn
The Reality Check
Running a 200-player Rust server is not "set and forget." It requires:
- Active monitoring, especially on wipe days
- Regular plugin auditing
- Decay balance tuning
- Player limits if hardware can't keep up
- Community management to prevent exploitative building
But when it works - a thriving 200-player Rust server is one of the most rewarding experiences in game hosting. The energy, the politics, the raids - it all depends on the server performing well enough to not get in the way.
