An overloaded warning means the server simulation took too long to complete a tick. A single slow tick can be a temporary spike; repeated warnings mean the workload is repeatedly exceeding the CPU, storage or memory headroom available to the server. Capture a tick log before changing settings, then work from the least disruptive fixes: put the world on an SSD, keep at least 4 GB of RAM free, reduce chunk and entity ranges, test without third-party mods, and make sure every machine runs the same current game version.
Playing with friends? Godlike.Host runs hosted Vintage Story servers from 10 data-center locations, with free DDoS protection.
This guide explains what the warning means, how to distinguish server lag from a client frame-rate problem, how to find the expensive operation, and which settings reduce load without deleting or corrupting your world.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What an overloaded warning actually measures
Vintage Story advances its world in simulation ticks. During each tick the server processes player actions, entities, block updates, chunk work, world generation, mod code and other scheduled tasks. If one tick takes longer than the time available before the next tick is due, the server falls behind. The warning reports the duration of that slow tick in milliseconds.
The official issue tracker includes an example warning in which a tick took 697 ms. That is a long individual delay, not a statement that every server tick runs at 697 ms. Treat the number as evidence of a stall at that moment and look for a pattern: occasional spikes usually feel like a brief hitch, while warnings that continue during normal play indicate sustained overload or an operation that keeps recurring.
#1 Best Overall
- High-Efficiency Performance: The SSD 1TB SATA adopts 3D NAND flash memory, which achieves a read speed of up to 560MB/s and a write speed of up to 510MB/s. Get a faster data transfer experience and improve your work efficiency.
- Upgrate Your Computer: The SATA 1TB SSD achieved faster app load and response times, and faster boot-up and shut-down, compared to HDDs. The internal SSD adopts advanced SLC Cache Technology, which improves overall computer performance.
- Reliability and Stability: The 2.5 SSD 1TB supports garbage collection, advanced wear-leveling technology, RAID, ECC, TRIM, and S.M.A.R.T, which makes the SATA SSD more reliable and stable. With the characteristics of shockproof, the SSD hard drive can keep your data safe, without worry even if your computer drops.
- Wide Compatibility: The 2.5'' SSD built-in SATA III 6Gb/S interfaces, witch backwards compatible with SATA II and SATA interfaces. The Internal SATA SSD is compatible with Windows, Linux, and Mac OS, and compatible with laptops, desktops, and all-in-one computers.
- 3-Year Service: Our SSDs come with a 3 years after-sales service and lifetime technical support. If you have any questions, please contact us and we will sincerely and professionally solve the problem for you.
How a slow tick appears to players
- A disconnected or warning icon appears even though the player’s internet connection has not dropped.
- Blocks reappear after being placed or removed because the client is waiting for the authoritative server state.
- Animals stop moving or update in bursts.
- A broken block takes noticeably longer before its drops appear.
- Movement and interactions feel delayed while the client’s frame rate may remain normal.
These are simulation delays. They are different from a computer rendering too few frames, which is a client-side problem and requires different remedies.
Server lag or client lag? Identify the failure first
Do not change several variables before deciding which side is slow. Use the symptoms and measurements below as a first classification.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| What you observe | Most likely side | What to check next |
|---|---|---|
| Blocks pop back, animals freeze, interactions wait, or the server reports long ticks | Server simulation | Capture logticks, then inspect server-main.txt for the largest contributors. |
| Low frames per second, stutter while turning the camera, or a frozen local display with no delayed world updates for other players | Client rendering or client resources | Check the affected computer’s frame rate, graphics settings and client mod load separately. |
| Only one player has delays while others act normally | That player’s client or network path | Compare the player’s frame rate and connection with another player before changing server settings. |
| Every player experiences delayed actions at the same time | Shared server workload | Record tick timings during the event and correlate them with autosave, chunk loading, entities or mods. |
A low frame rate does not prove the server is overloaded, and a disconnected icon does not prove the internet is at fault. The tick log is the useful measurement when the world itself is late to respond.
Capture a tick log before making changes
Logging the worst ticks gives you a baseline and prevents guesswork. Reproduce the slowdown while watching the server console, rather than collecting a log during an unrelated quiet period.
- Start the server and have a player reproduce the delay in the area where it normally occurs. Note the approximate time, location and action that triggered it.
- At the server console or through an administrator command channel, run
/debug logticks 100. The command records detailed information about long ticks. - Let the server run long enough to capture the problem. If the slowdown happens during exploration, travel through the same area; if it happens during a save, wait for the next save cycle.
- Run
/debug logticks 100again to disable logging. Leaving verbose tick logging enabled indefinitely is unnecessary overhead and makes later logs harder to read. - Open
%appdata%/VintagestoryData/Logs/server-main.txton the server machine. Find the largest tick durations and the operations listed as contributors. - Classify the entries as entity work, chunk loading or generation, mod activity, autosave activity, or another recurring operation. Change one relevant variable at a time and repeat the same reproduction test.
The goal is not merely to find the largest number. It is to learn whether one operation creates rare spikes or whether the same contributor consumes the budget on nearly every tick. That distinction determines whether a configuration change will help or whether the workload itself must be reduced.
Rank #2
- THE SSD ALL-STAR: The latest 870 EVO has indisputable performance, reliability and compatibility built upon Samsung's pioneering technology. S.M.A.R.T. Support: Yes
- EXCELLENCE IN PERFORMANCE: Enjoy professional level SSD performance which maximizes the SATA interface limit to 560 530 MB/s sequential speeds,* accelerates write speeds and maintains long term high performance with a larger variable buffer, Designed for gamers and professionals to handle heavy workloads of high-end PCs, workstations and NAS
- INDUSTRY-DEFINING RELIABILITY: Meet the demands of every task — from everyday computing to 8K video processing, with up to 600 TBW** under a 5-year limited warranty***
- MORE COMPATIBLE THAN EVER: The 870 EVO has been compatibility tested**** for major host systems and applications, including chipsets, motherboards, NAS, and video recording devices
- UPGRADE WITH EASE: Using the 870 EVO SSD is as simple as plugging it into the standard 2.5 inch SATA form factor on your desktop PC or laptop; The renewed migration software takes care of the rest
Rule out mods and version mismatches
Use a vanilla-only isolation test
Third-party mods can add entities, block behaviors, timers and world-generation work. For a clean comparison, temporarily run the server with only Vintage Story’s vanilla Survival, Creative and Essential mods. Test the same location and action that produced the warning.
If the warnings stop, restore the additional mods in groups rather than all at once. After each group, repeat the reproduction and inspect the tick log. This identifies a problematic group without forcing you to remove every mod permanently. Server and client installations must be treated together: a mod that changes world content generally needs matching files and versions on both sides.
Match the game version everywhere
The dedicated server and every connecting client should use the same current Vintage Story release. The hosting guidance listed stable release 1.22.7 when it was checked; release numbers change, so verify the current stable build in the game’s official channels instead of treating 1.22.7 as permanently current. Update the server and clients together, then retest before attributing a warning to hardware.
Lowest-risk changes to make first
Apply these in order, recording the result after each change. They reduce bottlenecks without deleting entities or altering the world’s content.
Move the savegame to an SSD
The Vintage Story performance guidance is explicit: Make sure the savegame is on an SSD.
An SSD lowers storage latency for chunk reads, writes and saves. Move the actual world save, not only the game executable, and confirm that the server is launching that moved save. Keep a known-good backup before changing its location so you can restore the original if the path is configured incorrectly.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #3
- SPEED UP COMPUTER: The fanxiang 1TB SSD 2.5 Inch SATA SSD achieves blazing read and write speeds of 520MB/s, facilitating rapid file and data transfers
- UPGRADE YOUR COMPUTER: Compared to HDDs, the 1TB SATA SSD boots up at least 50% faster, enabling instant productivity or gaming sessions
- LONG-LASTING DURABILITY: The 2.5 SATA SSD 1TB incorporates 3D NAND TLC chips, offering a longer lifespan in writes compared to QLC, ensuring a more reliable data storage solution
- EXTENSIVE COMPATIBILITY: The S101 1TB SATA III SSD is compatible with desktops, laptops, all-in-one PCs, supporting various operating systems like Windows, Linux, and Mac OS, meeting the needs of diverse devices
- 3-Year Service: Fanxiang S101 1TB SSD solid state drive provides 3 years after-sales service and lifetime technical support. If you have any questions, please contact us and we will sincerely and professionally solve the problem for you
Leave at least 4 GB of system RAM free
Before starting the server, keep at least 4 GB of physical RAM available for the operating system and the server’s working set. Close unrelated memory-heavy applications and check the host’s memory monitor while the problem is reproduced. If free memory disappears during exploration or a save, reducing view distance alone may not solve the stall; remove competing workloads or use a machine with more memory.
Reduce the maximum chunk radius
In serverconfig.json, try MaxChunkRadius = 10 or a lower value. A smaller maximum limits how far the server must keep chunks loaded for players, reducing chunk generation, loading and update work. The trade-off is a shorter available view distance. Change the setting, restart the server if required by your administration method, and test from the same player position.
Give the CPU more scheduling headroom with TickTime
In serverconfig.json, try TickTime = 40 or TickTime = 50, using the syntax and capitalization already present in your file. This lowers the server simulation rate from the default cited in the performance guidance and gives a busy CPU more time between simulation steps. It can make updates feel less immediate, so treat it as a measured compromise: compare interaction responsiveness and tick-log durations after each value.
Limit distant entity tracking
In servermagicnum.json, try DefaultEntityTrackingRange = 3. The guide describes this as reducing the range at which distant creatures remain active from 128 to 96 blocks. Fewer distant entities need to be tracked and updated, while creatures close to players continue to behave normally. Test farms, animal pens and areas with many loaded creatures after changing it.
Do not remove the per-tick entity-spawn limit
The server configuration documentation warns that removing the per-tick entity-spawn limit can cause severe lag. Do not “fix” a full spawn queue by deleting that safeguard. If the tick log points to spawning, reduce the workload that creates the demand—such as excessive loaded areas or a mod that repeatedly requests entities—and keep the protection in place.
Rank #4
- Boot up faster. Load files quicker. Improve overall system responsiveness
- 300% faster than a typical hard drive
- Improves battery life because it’s 45x more energy efficient than a typical hard drive
- Micron 3D NAND – advancing the world's memory and storage technology for 40 years
- Crucial 3-year limited warranty
Settings at a glance
| Change | Where | Effect | Trade-off or caution |
|---|---|---|---|
| Use an SSD for the save | Storage location used by the server | Reduces latency for chunk I/O and saves | Move the real save path and retain a backup. |
| Keep 4 GB or more RAM free | Host operating system | Leaves headroom for the server and avoids memory pressure | May require closing applications or upgrading the host. |
MaxChunkRadius = 10 or lower |
serverconfig.json |
Limits maximum loaded/view distance and chunk work | Players see a shorter usable horizon. |
TickTime = 40 or 50 |
serverconfig.json |
Provides CPU headroom by lowering the simulation rate | Updates can feel less frequent; test responsiveness. |
DefaultEntityTrackingRange = 3 |
servermagicnum.json |
Reduces distant-entity tracking from 128 to 96 blocks as described by the guide | Far-away creatures are tracked over a shorter range. |
| Keep the entity-spawn limit | Server configuration | Prevents unbounded per-tick spawning | Removing it can cause severe lag. |
Make one change, restart or reload using your normal server procedure, and reproduce the same event. If you change radius, tick timing, entity tracking and mods simultaneously, you will not know which change helped or what caused a new side effect.
Understand recurring pauses, especially autosave
Autosave can produce a visible pause even on a correctly configured server. The troubleshooting guidance states that an autosave every few minutes can cause one to two seconds of lag while it saves. It describes that pause as unavoidable when autosave is used to protect progression. A fast CPU and an SSD can reduce the duration, but they cannot guarantee that the pause disappears.
Use the tick log to separate an autosave pause from a continuous overload. A short, regular spike that aligns with the save event points toward save I/O. Warnings that continue between saves point instead toward entities, chunk work, world generation or mods. Do not disable progression-protecting autosaves merely to hide a warning; first improve storage and CPU headroom and verify whether the pause is within the expected one-to-two-second pattern.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Read the workload pattern in the log
Entity-heavy ticks
Entity contributors are likely when the worst ticks occur near animal pens, farms, crowded bases or areas with many loaded creatures. Test the same area with the entity tracking range reduced to 3 and compare the log. If the warning follows a particular pen or base, reduce unnecessary loaded creatures or investigate the mod that creates them rather than raising the spawn allowance.
Chunk loading and world generation
Chunk-related contributors commonly appear while a player travels into unexplored terrain or when several players spread out. Reduce MaxChunkRadius, avoid generating large new areas while the server is already busy, and test again from a known loaded region. A server that is smooth at an established base but stalls during exploration has a different bottleneck from one that lags everywhere.
Best Value
- Upgrade your laptop or desktop computer for faster startups, data transfers, and application loads
- Sequential read speeds of up to 550MB/s
- Faster performance and more reliable than traditional hard drives
- Shock and vibration resistant with no moving parts
- [1TB] 480TBW
Mod work
If a contributor appears only with a particular mod group enabled, keep the vanilla-only result as your control. Add groups back until the warning returns, then check that mod’s current release and configuration. Do not assume that a mod is at fault solely because it is installed; use the repeatable before-and-after tick log.
World-generation or one-time spikes
A single large tick during a one-time operation can be a spike rather than a permanent capacity limit. Record whether the warning repeats when the same action is performed again. If it does not, monitor rather than making aggressive world-wide changes. If it repeats at the same location or action, treat it as a recurring workload and continue isolating the contributor.
When local hosting is no longer enough
If the SSD, memory, range, tick-time and mod checks do not restore stable ticks, the host may simply lack single-core CPU headroom or fast enough storage for the number of players and the loaded world. The official troubleshooting guidance notes that many concurrent players require additional hardware.
Compare a local machine with a managed host using the same measurable criteria, not a generic “more powerful” label:
| Decision axis | Questions to answer | Why it matters |
|---|---|---|
| Single-core CPU headroom | What is the CPU margin during the worst logged tick, not only at idle? | Simulation work can bottleneck one core while overall CPU usage looks moderate. |
| Free RAM | Does the machine still keep at least 4 GB free during saves and exploration? | Memory pressure can turn a normally adequate host into a stuttering one. |
| SSD latency | Is the world stored on an SSD, and does the provider identify its storage tier? | Chunk and save operations depend on storage response time. |
| View and entity limits | Can you set maximum chunk radius and entity tracking range? | These controls let you trade visual range for predictable simulation load. |
| Mods and versions | Can the host run your mod set and the current server build, with clients matched? | A host that cannot keep versions aligned creates compatibility failures before performance is considered. |
| Backup and restore | Can you create, download and restore a world backup on demand? | Performance tuning should not put progression at risk. |
| Player geography | Where is the server located relative to most players? | Physical distance affects network latency independently of simulation speed. |
| Build availability | Does the provider offer the current Vintage Story release? | Old server builds can miss multiplayer performance improvements and create version mismatches. |
Managed hosting is appropriate when you cannot provide the required CPU, RAM and SSD capacity or do not want to maintain updates and backups. It is not a substitute for diagnosis: a poorly configured or mod-heavy world can overload a larger machine too.
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 minuteA repeatable recovery procedure
- Write down the warning duration, player count, location and action that trigger it.
- Classify the symptom as simulation delay or client frame-rate trouble.
- Capture a controlled
/debug logticks 100sample, then disable logging with the same command. - Inspect
server-main.txtand identify the largest recurring contributor. - Confirm the server and clients use the same current release; the guide’s 1.22.7 reference is historical and should not be assumed current.
- Run a vanilla-only test with Survival, Creative and Essential, then restore mod groups methodically.
- Verify the save is on an SSD and that at least 4 GB of RAM remains free during the test.
- Apply one configuration change: lower
MaxChunkRadius, tryTickTime40 or 50, or setDefaultEntityTrackingRangeto 3 according to the contributor you found. - Repeat the same workload and compare both player experience and the largest logged tick.
- If the server still falls behind, evaluate a host with more single-core CPU headroom, SSD storage, adequate memory, controllable ranges, current builds and usable backups.
What not to do
- Do not treat one 697 ms example as a universal threshold or assume every warning requires a new host.
- Do not change many settings before collecting a baseline log.
- Do not remove the per-tick entity-spawn limit; the documentation warns that doing so can create severe lag.
- Do not disable autosave solely because its expected one-to-two-second pause is visible; use the log to distinguish it from continuous overload.
- Do not troubleshoot a client frame-rate problem by lowering server simulation settings when other players see no delay.
- Do not leave server and client versions mismatched after an update.
Bottom line
Start with evidence: reproduce the warning, log the longest ticks, and identify whether entities, chunks, mods, world generation or autosave is responsible. Then use the least disruptive controls—SSD storage, 4 GB of free RAM, a lower maximum chunk radius, a tested TickTime of 40 or 50, and an entity tracking range of 3—while preserving the entity-spawn safeguard. If those measures and a vanilla/version-matched test still cannot keep up, the remaining fix is more capable single-core CPU, memory and SSD capacity, whether on your own machine or through managed hosting.
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.
