Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteReduce server load before changing network settings. Move the world to a dedicated server, use a smaller surface world with fewer extra creatures and resources, disable caves when nobody needs them, and remove unnecessary mods. These changes address the causes most often reported for server lag: CPU-bound simulation, an increasingly large world state, a second caves process, and mod-related memory problems. Leave tick_rate and lag compensation at their defaults until you can verify the setting against current Klei documentation and test one change at a time.
Playing with friends? Godlike.Host runs hosted Don't Starve Together servers from 10 data-center locations, with free DDoS protection.
What “lag” means in Don’t Starve Together
Players use “lag” for several different failures. A dedicated server can be overloaded, an individual computer can render the game slowly, or packets can be delayed between players and the server. The remedies are different, so identify the symptom before editing files.
As an Amazon Associate I earn from qualifying purchases.
Simulation lag
When the server cannot advance the world fast enough, every player may see delayed actions, rubber-banding, creatures freezing and then moving in bursts, or interactions completing several seconds after they were made. Community reports describe DST simulation as largely limited by single-core CPU speed. That claim appears in a search summary of a Steam discussion rather than a captured official statement, so treat it as a practical lead, not a published benchmark. Adding unused CPU cores is not a guaranteed fix if one busy thread remains the bottleneck.
World-state growth
Players also report that a long-running world accumulates more items, creatures and resources. Each object adds work for the simulation and can make a previously smooth server deteriorate. A fresh world that performs well does not prove the hardware will remain adequate after a long campaign.
#1 Best Overall
- Tri-Band WiFi 6E Router - Up to 5400 Mbps WiFi for faster browsing, streaming, gaming and downloading, all at the same time(6 GHz: 2402 Mbps;5 GHz: 2402 Mbps;2.4 GHz: 574 Mbps)
- WiFi 6E Unleashed – The 6 GHz band brings more bandwidth, faster speeds, and near-zero latency; Enables more responsive gaming and video chatting
- Connect More Devices—True Tri-Band and OFDMA technology increase capacity by 4 times to enable simultaneous transmission to more devices
- Unique Design, More RAM, Better Processing - A unique housing design provides optimal heat dissipation, combined with a 1.0 GHz dual-core CPU and 512 MB High-Speed Memory, the AXE75 is designed for long-term reliability and performance.
- EasyMesh-compatible - Extend network range even more by adding EasyMesh-compatible routers, extenders, or wireless powerline adapters for a seamless, whole-home connection. Eliminate dead zones, drops, and lag as you move across your home.
Client or connection problems
If only one player is affected while everyone else moves normally, inspect that player’s graphics settings and background traffic first. If everyone freezes together, investigate server load. A poor route or forwarding configuration can also look like lag, but the material available for this guide does not establish a verified port number or a complete forwarding procedure.
The highest-impact fixes, in order
- Run a dedicated server instead of hosting from a player’s game client. A community comparison reports better optimization for the dedicated process.
- Reduce world-generation load. Choose a smaller surface world and avoid extra creature or resource settings when creating the world.
- Remove caves when they are not being used. If caves are essential, make the cave world smaller.
- Use no mods or only the minimum set. Add them back individually so a problematic mod can be identified.
- Limit simultaneous players to the group you actually have. Lowering the advertised maximum does not magically create CPU capacity, but it prevents an unexpectedly large session from consuming it.
- Leave tick-rate and lag-compensation settings alone initially. Conflicting community guidance makes these poor first experiments.
Dedicated server versus client hosting
Hosting through the game client makes one machine render a player’s game and simulate the world at the same time. Community reports describe the dedicated server as better optimized for the server role. A dedicated process also lets the host machine remain focused on simulation while players connect from their own computers.
| Arrangement | Typical risk | Best first action |
|---|---|---|
| One player hosts from the game client | Rendering, local background work and simulation compete on one machine; the host may experience a different symptom from everyone else. | Move the same cluster to a dedicated process and compare an identical scenario. |
| Dedicated server without caves | Only the surface simulation is running, so total process load is lower than a two-world cluster. | Use this as the baseline when caves are not part of the campaign. |
| Dedicated server with caves | The surface and cave worlds run as separate server processes on the same machine. | Keep caves only when needed and test a smaller cave world under real player load. |
What to check after moving
- Start with the same world and mod list so the move itself is the only changed variable.
- Have two or more players perform the actions that previously caused freezes or rubber-banding.
- Record whether the delay affects everyone or only the original host.
- If the dedicated process is still overloaded, continue with world size, caves, mods and player-limit changes instead of immediately raising tick rate.
Hardware priorities
There is no verified universal CPU, memory or player-count specification for every DST world. Community reports consistently point to CPU simulation work, with single-core speed often more useful than a large number of additional cores. Choose a machine that can sustain the expected group and world settings rather than relying on a headline core count. If performance degrades after hours or days, watch for a mod-related memory problem as well as CPU saturation; do not assume that adding memory alone fixes a simulation bottleneck.
Reduce the work created by the world
Choose a smaller surface world
Community advice repeatedly points to a smaller above-ground world as a way to reduce simulation work. When generating a replacement world, select a smaller map size and avoid optional settings that add extra creatures or abundant resources. Those settings increase the amount of state the server must maintain.
Why world age matters
A long campaign can contain more dropped items, tamed or hostile creatures, resource nodes and other persistent state than a new world. That growth explains why a server may feel smooth on its first evening and begin rubber-banding later. Compare activity at the same player count when testing; a quiet base and a large fight are not equivalent workloads.
Apply the change safely
- Back up the entire cluster before generating or replacing a world.
- Create a test copy with the smaller surface settings.
- Use the same number of players and the same actions that exposed lag on the original.
- Retest after the copy has been running long enough to expose the original symptom, not just during the first few minutes.
- Keep the smaller world only if it improves the shared experience; a smaller map changes exploration and resource availability.
Do not assume that deleting a few dropped items is equivalent to regenerating a world. Reports attribute long-term slowdowns to the total population of items, creatures and resources, not to one particular object. If the existing save is valuable, preserve it and use a separate test cluster rather than experimenting directly on the only copy.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #2
- Please update the firmware upon initial setup of the router, as it greatly enhances the device's performance and ensures a superior user experience.*** 【WiFi 6 Standard with ultra-low latency】Wi-Fi 6 speeds up to 6 Gbps to let you enjoy smoother 4K streaming, gaming, video calls and more, DDR4 1GB / eMMC 8GB
- 【High Speed Gaming Router】Dominate with uninterrupted performance with the ultimate MT6000 gaming internet router, equipped with 8-stream Wi-Fi 6 technology, the Flint 2 delivers blazing speeds, ensuring a stable and high-speed connection during intense multiplayer battles.
- 【Rapid OpenVPN & Wireguard speed】Wireguard VPN and OpenVPN speeds up to 900Mbps and 880Mbps respectively, giving you complete control over your gaming, streaming and working bandwidth. Actual speed may differ depending on internet service provider, network environment, VPN server location, VPN service provider, etc.
- 【AdGuard Home Supported】Enabling the use of a DNS server for blocking unwanted tracking and offers a convenient web interface for filtering selected digital advertisements. Users can take full control of their online experience and enjoy a clutter-free browsing environment with ease.
- 【Mass device connectivity】Experience enhanced online connectivity with our higher storage capacity, catering to over a hundred devices and fulfilling the requirements of DIY users seeking to install additional plugins. Enjoy stable and reliable connections, ensuring seamless performance and accommodating a wide range of digital needs.
Decide whether you need caves
A DST cluster with caves runs a second server process. Both processes consume resources on the same machine, so caves can be the decisive difference between a comfortable and an overloaded cluster.
If your group never enters caves
Disable caves for that cluster. This removes the second process and its associated world state. Make the decision before starting a new campaign or after a complete backup, because changing world structure can affect an existing save. Tell players that the test is intentional so they do not mistake the missing cave entrance for a broken save.
If caves are part of the campaign
Keep them, but generate a smaller cave world and test surface and cave travel with the expected number of players. Watch for lag that appears only when players are split between the two worlds; that pattern points to total server load rather than a single crowded location. Test both players gathered in one world and players divided between worlds, because the process arrangement is different in each case.
Reduce and isolate mods
Community reports include cases in which mods leak memory. That is not evidence that every mod leaks, but it makes a no-mod test essential. Mods can also add entities, checks or UI work that changes the server’s workload. A mod that appears fine in a short session may still be responsible for a gradual decline after a long uptime.
Recommended Free Tools
A controlled mod test
- Back up the cluster and note the complete enabled-mod list and its order.
- Run the dedicated server with all optional mods disabled.
- Reproduce the lag using the same world activity and player count.
- Keep the server running long enough to see whether the original gradual slowdown returns.
- If the lag disappears, re-enable one mod at a time and run the same test for each addition.
- Remove the mod that brings the problem back, or contact its maintainer with a reproducible description.
Do not change world size, caves, player count and mods in one test. You will not know which change helped, and a mod may appear harmless only because another setting reduced the load. Keep a written list of the last known-good combination so a rollback is quick.
Set a realistic player limit in cluster.ini
Hosting documentation places max_players in the [GAMEPLAY] section of cluster.ini. A Klei forum settings guide reports a default of 16, while a GitHub sample lists a valid range of 1 to 64. Neither figure should be treated as a current official performance guarantee. One hosting guide says groups of roughly four to 16 players commonly work and that higher values require stronger hardware.
Rank #3
- 𝐆𝐢𝐠𝐚𝐛𝐢𝐭 𝐖𝐢𝐅𝐢 𝐟𝐨𝐫 𝟖𝐊 𝐒𝐭𝐫𝐞𝐚𝐦𝐢𝐧𝐠 – Up to 5400 Mbps WiFi for faster browsing, streaming, gaming and downloading, all at the same time. Performance varies by conditions, distance to devices, & obstacles such as walls.
- 𝐅𝐮𝐥𝐥 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐖𝐢𝐅𝐢 𝟔 𝐑𝐨𝐮𝐭𝐞𝐫 – Equipped with 4T4R and HE160 technologies on the 5 GHz band to enable max 4.8 Gbps ultra-fast connections.Power:12 V 2.5 A
- 𝐂𝐨𝐧𝐧𝐞𝐜𝐭 𝐌𝐨𝐫𝐞 𝐃𝐞𝐯𝐢𝐜𝐞𝐬 – Supports MU-MIMO and OFDMA to reduce congestion and 4X the average throughput
- 𝐄𝐱𝐭𝐞𝐧𝐬𝐢𝐯𝐞 𝐂𝐨𝐯𝐞𝐫𝐚𝐠𝐞 - Covers up to 2,000 sq. ft. High-Power FEM, 6× Antennas, Beamforming, and 4T4R structures combine to adapt WiFi coverage to perfectly fit your home and concentrate signal strength towards your devices.
- 𝐌𝐨𝐫𝐞 𝐕𝐞𝐧𝐭𝐬, 𝐋𝐞𝐬𝐬 𝐇𝐞𝐚𝐭 – Improved vented areas help unleash the full power of the router
| Setting | Location | Reported value or range | How to use it |
|---|---|---|---|
max_players |
[GAMEPLAY] in cluster.ini |
Default 16 in a Klei forum guide; 1–64 in a GitHub sample | Set it to the largest group you genuinely expect, then test under that load. These are community/sample values, not verified Klei performance limits. |
tick_rate |
[NETWORK] in cluster.ini |
15 default and 10, 15, 30 or 60 allowed in one Klei forum guide; another source conflicts | Leave the existing/default value until official documentation and a controlled test support a change. |
Lowering max_players does not reduce load while the same number of people are online. It does prevent a server configured for 64 from accepting an unexpectedly large session and gives you an honest capacity target. Set the limit to the real group size, not to a theoretical maximum you never use.
Editing a cluster safely
- Stop every server process in the cluster, including both surface and cave processes.
- Copy the complete cluster directory to a dated backup.
- Edit the relevant
cluster.ini, preserving section names and the existing syntax. - For a multi-machine cluster, check every copy. Some settings must match across cluster machines; a Steam community setup guide specifically lists
tick_rateamong them. - Start the cluster and verify that the intended player limit is shown before inviting the full group.
- If the server fails to start or behaves differently, stop it and restore the backup rather than stacking more edits on top.
Why you should not “fix” lag by raising tick rate
The available guidance conflicts. A Klei forum settings guide reports a default tick_rate of 15 and allowed values of 10, 15, 30 and 60. A separate Steam setup guide says Klei recommends the default except for LAN play and discusses values that divide evenly into 60, including 15, 20 and 30. A 2026 hosting blog instead claims the default is 30 and says 60 doubles CPU load; that conflicts with the Klei-derived material and should not be treated as authoritative.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Because the default and valid values are not consistently documented, changing the setting can make diagnosis harder or increase CPU demand. Keep the current/default value for the first round of fixes. If you must investigate it, work on a copy of the cluster, change only tick_rate, test at the same player count and world activity, and restore the previous value if performance worsens. Do not change it simply because another server advertises a higher number.
Lag compensation: treat online advice as unverified
One 2026 blog recommends disabling lag compensation, but that recommendation was not confirmed against official Klei documentation. Do not use it as a generic fix. Keep the existing setting while you establish whether the problem is simulation load, a client, or the network path. Test any later change separately and record the before-and-after behavior for every player. A setting that changes how movement feels can mask, rather than remove, an overloaded simulation.
Client-side changes for one affected player
When the server is smooth for everyone else, the affected player can try the low-risk habits commonly cited in forum advice:
- Enable Netbook Mode in the game settings.
- Lower texture quality.
- Close background applications that consume CPU or memory.
- Pause downloads and uploads while playing.
These steps target rendering and local resource contention; they do not repair a CPU-bound dedicated server. If every player is affected at the same moment, return to server-side load testing instead of asking each player to lower graphics settings. If only the host is affected in a client-hosted game, moving to dedicated hosting is a stronger test than changing every player’s graphics options.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- 𝐅𝐮𝐭𝐮𝐫𝐞-𝐑𝐞𝐚𝐝𝐲 𝐖𝐢-𝐅𝐢 𝟕 - Designed with the latest Wi-Fi 7 technology, featuring Multi-Link Operation (MLO), Multi-RUs, and 4K-QAM. Achieve optimized performance on latest WiFi 7 laptops and devices, like the iPhone 16 Pro, and Samsung Galaxy S24 Ultra.
- 𝟔-𝐒𝐭𝐫𝐞𝐚𝐦, 𝐃𝐮𝐚𝐥-𝐁𝐚𝐧𝐝 𝐖𝐢-𝐅𝐢 𝐰𝐢𝐭𝐡 𝟔.𝟓 𝐆𝐛𝐩𝐬 𝐓𝐨𝐭𝐚𝐥 𝐁𝐚𝐧𝐝𝐰𝐢𝐝𝐭𝐡 - Achieve full speeds of up to 5764 Mbps on the 5GHz band and 688 Mbps on the 2.4 GHz band with 6 streams. Enjoy seamless 4K/8K streaming, AR/VR gaming, and incredibly fast downloads/uploads.
- 𝐖𝐢𝐝𝐞 𝐂𝐨𝐯𝐞𝐫𝐚𝐠𝐞 𝐰𝐢𝐭𝐡 𝐒𝐭𝐫𝐨𝐧𝐠 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧 - Get up to 2,400 sq. ft. max coverage for up to 90 devices at a time. 6x high performance antennas and Beamforming technology, ensures reliable connections for remote workers, gamers, students, and more.
- 𝐔𝐥𝐭𝐫𝐚-𝐅𝐚𝐬𝐭 𝟐.𝟓 𝐆𝐛𝐩𝐬 𝐖𝐢𝐫𝐞𝐝 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 - 1x 2.5 Gbps WAN/LAN port, 1x 2.5 Gbps LAN port and 3x 1 Gbps LAN ports offer high-speed data transmissions.³ Integrate with a multi-gig modem for gigplus internet.
- 𝐎𝐮𝐫 𝐂𝐲𝐛𝐞𝐫𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐂𝐨𝐦𝐦𝐢𝐭𝐦𝐞𝐧𝐭 - TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
Network checks without guessing a port
When players cannot connect, disconnect frequently, or see delays that do not coincide with server activity, investigate the network path separately from simulation load. Check the host’s forwarding or triggering configuration, firewall rules, router behavior and whether background uploads are saturating the connection. A commonly repeated UDP port number appears in community summaries, but it is not tied here to a citable, version-specific Klei page, so do not treat an unverified number as a universal requirement. Confirm the correct port and protocol in current Klei or hosting documentation for the exact server version.
Network troubleshooting should not be mixed with world-generation changes. First establish whether all connected players experience the same freeze. A forwarding mistake normally prevents connection or causes disconnections; it does not explain a world that consistently slows when many entities are active.
A repeatable troubleshooting workflow
- Classify the symptom. Ask whether everyone experiences the delay, whether it occurs only in caves or only on the surface, and whether one computer is affected.
- Reproduce it. Use a fixed player count and repeat the same high-activity actions. Avoid comparing a quiet base to a crowded fight.
- Establish a baseline. Keep the current world, cave setting, mods, player limit and tick rate unchanged for one test session.
- Apply one high-confidence change. Start with dedicated hosting, then test world size, caves and mods in that order.
- Retest after the world has been running. A short improvement followed by renewed lag can indicate accumulating state or a mod-related memory problem.
- Test player capacity. Repeat the scenario with the actual maximum group instead of judging capacity from a solo session.
- Separate network tests. Only after server load is understood should you investigate forwarding, firewall or route issues.
- Roll back cleanly. Restore the backup when a change damages the world or makes the symptom worse.
Symptom-based decisions
| Observed pattern | Most useful next test |
|---|---|
| Everyone rubber-bands, including on the surface | Move from client hosting to a dedicated server; then reduce world size and optional spawns. |
| Lag appears when caves are active or players split between worlds | Disable caves for a test, or use a smaller cave world. |
| Performance worsens over a long campaign | Compare a backed-up fresh test world, inspect the mod list, and consider accumulated items, creatures and resources. |
| Only one player stutters while others are fine | Try Netbook Mode, lower texture quality and stop local background traffic. |
| Lag begins after adding a mod | Disable all mods, then re-enable them one at a time. |
| Players cannot connect at all | Check forwarding, firewall and the version-specific port documentation rather than changing world settings. |
| Changing tick rate is being proposed as the first fix | Do not change it yet; the documented defaults conflict and the setting can increase load. |
Common mistakes that waste troubleshooting time
- Changing several variables together. A smaller map, fewer mods and a different tick rate cannot tell you which change mattered.
- Testing only when nobody is playing. The relevant load occurs during combat, building, travel, cave transitions and large multiplayer gatherings.
- Assuming a new world proves the old one is corrupted. Long-running state can simply be heavier; compare the same activity before replacing a valuable save.
- Raising the advertised player limit “just in case.” A high limit can invite a session your hardware was never tested to support.
- Editing a live cluster. Stop every process and keep a complete backup before changing
cluster.inior world settings. - Trusting a single blog’s tick-rate claim. Defaults and allowed values conflict across community material, so preserve the known-good setting.
- Blaming the network for synchronized freezes. If every player freezes at the same moment during heavy simulation, reduce server work first.
What a sensible final configuration looks like
For a small private group, the conservative configuration is a dedicated server, a modest surface world, no unnecessary extra creatures or resources, caves disabled unless they are part of the plan, and no more mods than the group needs. Set max_players for the expected group rather than an aspirational maximum. Leave tick_rate and lag compensation unchanged until an official, version-specific explanation and a controlled test justify otherwise.
Keep a written record of world settings, enabled mods, player count and each change. That record turns “the server is lagging” into a reproducible comparison and lets you restore the last known-good cluster instead of guessing.
Frequently Asked Questions
Why is my Don’t Starve Together server lagging for everyone?
Synchronized rubber-banding usually points to simulation load. Use a dedicated server, reduce surface-world size and optional spawns, disable unused caves, minimize mods, and test with the real player count before changing tick rate.
Does a dedicated server perform better than hosting from the game client?
Community comparisons report that the dedicated process is better optimized for server work. It also separates world simulation from the host player’s rendering and local background applications.
Best Value
- DUAL-BAND WIFI 6 ROUTER: Wi-Fi 6(802.11ax) technology achieves faster speeds, greater capacity and reduced network congestion compared to the previous gen. All WiFi routers require a separate modem. Dual-Band WiFi routers do not support the 6 GHz band.
- AX1800: Enjoy smoother and more stable streaming, gaming, downloading with 1.8 Gbps total bandwidth (up to 1200 Mbps on 5 GHz and up to 574 Mbps on 2.4 GHz). Performance varies by conditions, distance to devices, and obstacles such as walls.
- CONNECT MORE DEVICES: Wi-Fi 6 technology communicates more data to more devices simultaneously using revolutionary OFDMA technology
- EXTENSIVE COVERAGE: Achieve the strong, reliable WiFi coverage with Archer AX1800 as it focuses signal strength to your devices far away using Beamforming technology, 4 high-gain antennas and an advanced front-end module (FEM) chipset
- OUR CYBERSECURITY COMMITMENT: TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
Can caves cause server lag?
Yes. A cluster with caves runs a second server process on the same machine. Disable caves when they are unnecessary, or generate a smaller cave world and test players together and split between worlds.
How many players should I allow in cluster.ini?
Set max_players to the largest group you genuinely expect. Community documentation reports a default of 16 and a sample range of 1–64, but neither is a verified performance guarantee; higher player counts need stronger hardware and testing.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Where are max_players and tick_rate configured?
Both are in cluster.ini. max_players is listed under [GAMEPLAY]; tick_rate is listed under [NETWORK]. In a multi-machine cluster, check every copy because some settings must match.
Should I increase tick_rate to reduce lag?
No, not as a first step. Community sources disagree about the default and allowed values, and a higher rate can increase CPU work. Keep the current value, or test one change on a backed-up copy only after confirming version-specific documentation.
Should I disable lag compensation?
Treat that advice as unverified. Keep the existing setting while you determine whether the problem is server load, a client, or the network. If you test a change, isolate it and compare the same scenario before and after.
What if only one player is lagging?
Have that player enable Netbook Mode, lower texture quality, close CPU- or memory-heavy applications, and pause downloads or uploads. If everyone else is smooth, those client-side checks are more appropriate than changing the server world.
Can mods create lag over time?
Community reports include mod-related memory leaks and extra simulation work. Run a no-mod test, then add mods back one at a time using the same activity and player count. Remove the mod that reproduces the problem.
Is there a confirmed DST server port I should forward?
A port number is repeated in community summaries, but it is not established here as a universal, version-specific fact. Check current Klei or hosting documentation for the exact server version and protocol instead of guessing.
The Bottom Line
Start with load, not exotic settings: use dedicated hosting, a smaller world, fewer optional spawns, no unused caves and minimal mods. Set a realistic max_players, back up the cluster before every edit, and leave tick_rate and lag compensation at their existing values until controlled testing and current Klei documentation support a change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
