Map choices affect performance and player experience. Bigger isn’t always better.
Table of Contents
- Player count vs map size
- Biome balance
- Performance tradeoffs
- Content pacing
- Hosting notes
1. Player count vs map size
Pick a size that keeps players interacting.
2. Biome balance
Offer variety without spreading players too thin.
3. Performance tradeoffs
Large maps increase load; balance with CPU resources.
4. Content pacing
Adjust events and wipes to fit your map.
5. Hosting notes
Use high-clock CPU hosting for better tick stability.
How map size impacts Rust server performance
Rust map size is the single biggest knob for server RAM and CPU at startup. The world is procedurally generated; everything is loaded in memory.
| Map size | RAM at start | RAM with 100 players | Boot time |
|---|---|---|---|
| 3000 | 2.5 GB | 6 GB | 30 s |
| 3500 | 3.5 GB | 8 GB | 45 s |
| 4000 | 4.5 GB | 11 GB | 1 min |
| 4500 | 5.5 GB | 14 GB | 1.5 min |
| 5000 | 6.5 GB | 18 GB | 2 min |
| 6000 | 9 GB | 24 GB | 3 min |
The "headroom" RAM (50-100 % above startup) is where save state, entity inflation, and base building live.
Player density vs map size
| Map | Slots | Player density | Feels like |
|---|---|---|---|
| 3000 | 50 | high | small KOTH-style server |
| 3500 | 100 | medium-high | popular vanilla |
| 4000 | 150 | medium | typical 100-pop community |
| 4500 | 200 | low-medium | room to roam |
| 5000+ | 250+ | low | mega-base / RP / build server |
Going below recommended density makes the map feel empty; going above it causes neighbor-base griefing and server-side load spikes from clustering.
Biome strategy: monument placement
+server.worldsize 4000
+server.seed 1234567
+server.salt 0
Same seed + size + salt = identical map. Test seeds before committing:
- rustmaps.com: shows monument layout for any seed before launch.
- Bias toward seeds with 4+ unique monuments and no two of same type adjacent.
- Avoid seeds where 2+ monuments are within 200 m of each other (lag hotspot).
Procedural vs custom maps
| Type | Setup effort | Player familiarity | Performance |
|---|---|---|---|
| Procedural (default) | none | high (rustmaps preview) | predictable |
| Custom map | upload, plugin | low (must learn layout) | varies (hand-placed quality) |
| Hapis (legacy) | one cvar | medium | smaller, less RAM |
For 95 % of community servers, procedural with a tested seed is the right answer.
Performance gotchas tied to map size
- Save file size: a 4500 map after 7 days has a 200-400 MB save. Saves can pause the world for 1-3 s; tune
server.saveinterval. - Entity count caps: a larger map permits more bases, more cupboards, more entities. Watch
entitycountconsole value; above 250k, fps and tick suffer. - Cargo / heli pathfinding: scales with map size; on huge maps, events take longer.
- AI navigation: NPCs precompute paths over the map; bigger map = larger nav data in RAM.
Picking the right size
| Player count goal | Map size |
|---|---|
| 25-50 | 3500 |
| 50-100 | 4000-4250 |
| 100-150 | 4250-4500 |
| 150-200 | 4500-5000 |
| 200+ build/RP | 5000-6000 |
If you under-size, players cluster and the server feels like a parking lot. If you over-size, players never meet and the server feels dead by week two.
