Enshrouded "Server Overloaded" Fix
When Enshrouded shows "Server Overloaded" or players rubberband, the server is running out of CPU time or memory. Use the steps below to stabilize the instance without wiping your world.
Known Issue (November 2024+): Since the November 2024 update, many players report "Server Overloaded" warnings even on powerful hardware (Ryzen 7, 32GB RAM) with low server utilization. This appears to be a server software optimization problem, not a hardware issue. Workarounds are limited.
Common Causes
| Symptom | Likely Cause | Fix |
|---|---|---|
| Rubberbanding during combat | CPU saturated from too many active regions | Reduce slotCount and group players together |
| Server Overloaded warning | Memory leak or long uptime | Restart every 8-12 hours |
| Overloaded with few players | Post-Nov 2024 optimization issues | No fix yet - reduce slot count, frequent restarts |
| Slow interactions (chests, doors) | Network buffer full or heavy save | Lower player count, clear old backups, restart |
| Players far apart = lag | Server loads multiple regions simultaneously | Keep players in same biome when possible |
Step-by-Step Fix
- Reduce slot count. Lower the max players in
enshrouded_server.jsonand restart. - Restart on a schedule. Voxel worlds leak memory over time. Schedule restarts every 8-12 hours.
- Verify resources. Compare your hardware to Enshrouded requirements.
- Check save load loops. If the log shows repeated save loads, follow Troubleshooting.
- Keep updates aligned. Update server and clients after patches to avoid performance regressions.
Config Example
{
"name": "My Enshrouded Server",
"slotCount": 12,
"gamePort": 15636,
"queryPort": 15637,
"ip": "0.0.0.0",
"saveDirectory": "./savegame"
}
Tip: If 12 players are spread across different biomes, the server effectively loads 12 worlds. Encourage grouping for large raids.
Keep Embervale smooth. Host your Enshrouded server with Supercraft for optimized CPU clocks and managed restarts.