How to Diagnose and Fix Lag on Your 7 Days to Die Server
Identify the source of lag on your 7DTD server and tune the key performance settings — zombie counts, view distance, and base simulation — to keep the server running smooth.
What Causes Server Lag in 7DTD
7DTD servers are CPU-heavy. The main contributors to lag:
- Too many active zombies (pathfinding is expensive)
- High player view distance forcing more chunk simulation
- Blood moon horde nights with max enemy counts
- Too many players on underpowered hardware
- Mods with heavy tick-rate processing
RAM and disk speed matter less than CPU single-thread performance for 7DTD.
Reading the Server Log for Lag Clues
Check UserData/Logs/ for the current log file. Search for:
[SRV] Slow frame: 523ms
This means a server tick took 523ms instead of the target ~16ms. Persistent slow frames = sustained lag. Occasional spikes during blood moons or new chunk generation are normal.
Also watch for:
Chunk generation took 842ms
High chunk generation times during exploration are common and usually not a concern unless they're happening constantly.
Key Settings to Tune
All in serverconfig.xml:
MaxSpawnedZombies
<property name="MaxSpawnedZombies" value="64" />
This is the most impactful setting for CPU load. It caps the total number of zombies active across the entire map at once. Default is 64.
Drop this first when you're having lag issues:
<property name="MaxSpawnedZombies" value="32" />
Players will notice slightly fewer zombies but servers stay responsive. For high player-count servers, going down to 24–32 is often necessary.
MaxSpawnedAnimals
<property name="MaxSpawnedAnimals" value="50" />
Less impactful than zombies but contributes. Lower to 25–30 if needed.
ServerMaxAllowedViewDistance
<property name="ServerMaxAllowedViewDistance" value="12" />
This caps how far players can set their own view distance. Higher view distance = more chunks being simulated simultaneously. Reduce to 6–8 on servers with more than 4–6 players:
<property name="ServerMaxAllowedViewDistance" value="6" />
BloodMoonEnemyCount
<property name="BloodMoonEnemyCount" value="8" />
Blood moon nights are lag spikes waiting to happen. If your server runs fine normally but tanks on horde nights, this is why. Reduce from the default (or your current value) to cut down simultaneous pathfinding load.
LandClaimCount
<property name="LandClaimCount" value="3" />
Each land claim area simulates sleeper respawning and protection logic. Players with many bases across a large world add background simulation load. Limiting to 1–2 per player reduces this.
Regular Restarts Help
7DTD has memory growth over long uptime sessions. Daily restarts (or every 12 hours on busy servers) keep memory usage in check and clear accumulated state. Schedule this during low-traffic hours.
Use the console to broadcast a warning before restart:
say "Server restarting in 5 minutes for scheduled maintenance."
Then:
shutdown
Blood Moon Performance Strategy
If blood moons cause severe lag spikes even with tuned settings:
- Reduce
BloodMoonEnemyCountto 16–24 - Ask players to build in the same area — distributed bases mean zombies pathfinding across the whole map
- Reduce
MaxSpawnedZombiesspecifically before horde night if you can manage it manually