Network and Lag Troubleshooting
Tags: network, lag, troubleshooting
Lag reports blur together unless you triage fast. Use a repeatable checklist so you can separate server load, bad routes, and mod issues. This guide covers 7 Days to Die 1.0+ including crossplay troubleshooting.
Start with scope
- Everyone lagging: suspect server performance, host network, or DDoS.
- Only some players lag: suspect ISP route, Wi-Fi, or outdated client files.
- Specific areas lag: corrupted regions or heavy bases causing chunk churn.
- Crossplay-specific: if only console players lag, check 1.0 crossplay settings and platform-specific optimization issues.
Quick checks
- Watch CPU/disk during spikes; long saves or HDDs often feel like rubber-banding.
- Reduce view distance temporarily and note if hitching improves.
- Check logs for repeating errors, XML warnings, or mod stack traces.
- Verify crossplay configuration: ensure server is visible to console players in server browser.
- Test with different platforms (PC, PlayStation, Xbox) to isolate platform-specific issues.
Network path
- Ping and traceroute from affected players; compare to a clean VPN path. Include console players in testing.
- Restart router/firewall, refresh DHCP leases, and verify no new QoS rules were applied.
- If hosted, open a ticket with timestamps and traceroutes so provider can move you to a cleaner route.
- For crossplay: verify UDP port forwarding (26900-26903) reaches all platforms without blocking.
Network path
- Ping and traceroute from affected players; compare to a clean VPN path.
- Restart the router/firewall, refresh DHCP leases, and verify no new QoS rules were applied.
- If hosted, open a ticket with timestamps and traceroutes so the provider can move you to a cleaner route.
World and mods
- Look for oversized bases or trap chunks; trim excessive turrets and chunk loaders.
- Validate prefab/mod packs for missing assets; remove the newest mod if lag started after adding it.
- Run
repairchunkdensity after major updates to fix bloated saves.
Keep players calm
- Post a short status message with what you are checking and when the next update will land.
- Apply one change at a time and record the timestamp so you can correlate improvements.
- Schedule a restart after fixes and recheck pings once the server is back. See Updating & Downtime Management for planning maintenance windows.
Related Articles