Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Vintage Story’s documented server target is one tick every 33.3333321 milliseconds, or 30 ticks per second. That number is a scheduling target, not a promise that every tick will finish on time. When a tick takes longer, players see delayed block updates, entity movement and interactions. Effective tuning starts by finding what consumed the slow tick, then changing one setting that addresses that workload while recording the gameplay trade-off.
Godlike.Host offers hosted Vintage Story servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The safest controls are in serverconfig.json: view-distance limits, mob-cap scaling, block-tick budgets and player limits. Lower-level values in servermagicnumbers.json can affect chunk generation, sending and threading, but the official documentation warns that aggressive values can overload the server, clients or network. Treat those settings as workload-specific experiments, not a universal performance preset.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What server tick rate means in Vintage Story
A server tick is one simulation update: the server processes world logic, entities, block updates, chunk work and persistence, then starts the next update. The Server Config page describes TickTime as the desired milliseconds between ticks and lists 33.3333321, calculated as 1000 / 30. If all work completes within that interval, the server can maintain the 30-tick-per-second target.
TickTime is not a performance switch and lowering it does not make a CPU complete work faster. If a tick needs 45 ms, a 33.333 ms target cannot force it to finish sooner; the server falls behind until the workload drops. A warning such as “a tick took 48401ms” means that particular tick lasted about 48.4 seconds, not that the server normally runs at 0.02 ticks per second. The Vintage Story forum post “Server overloaded. A tick took 48401ms to complete”, posted in March 2025, shows how one server’s diagnostic breakdown included several work categories and save activity. It is an example of useful evidence, not a typical result or proof of a universal cause.
#1 Best Overall
- EXACT-MATCH UPGRADE — 128GB (4X32GB) kit DDR4-3200 (PC4-25600), 2Rx4 Registered ECC, 1.2V, CL22, 288-pin. The precise rank, voltage, and timing your server's memory controller expects, so it's recognized at full capacity and runs at its rated speed.
- VERIFIED FITMENT — Compatible with Xeon Scalable, PowerEdge, ProLiant, ThinkSystem, Supermicro. Spec-matched to your board's memory-population rules.
- ENTERPRISE STABILITY — Registered (buffered) architecture offloads the memory controller so every slot runs fully populated at full capacity, while ECC catches and corrects single-bit errors on the fly — stopping silent data corruption and unplanned reboots before they reach production.
- CHECK YOUR CONFIG — Server and motherboard memory support varies by model. Consult your system or motherboard manual for supported capacities, approved DIMM population order, and installation steps before purchase.
- LIFETIME SUPPORT — Backed by a lifetime replacement warranty and free US-based technical support.
Players may describe this as “lag,” but the remedy depends on whether the time was spent in the main simulation loop, entity spawning, chunk generation, network delivery, physics, memory pressure or saving. Measure first; otherwise a setting change can reduce view distance or mob populations without touching the real bottleneck.
Prepare before editing configuration
- Record the environment. Write down the Vintage Story version, operating system, player count, active mods, world size and when the warnings occur. Note whether the problem appears during exploration, combat, farming, automation or saving.
- Make a rollback copy. Stop the server cleanly and copy
serverconfig.jsonand, if you will edit it,servermagicnumbers.json. Keep the original files with the date in the filename so you can restore known-good values. - Check the generated file for your version. The English Server Config page says its defaults were last verified for version 1.20.0, while the current page can contain a snapshot whose fields differ by release. Use the
serverconfig.jsongenerated by your installed version and consult matching documentation rather than pasting an older file wholesale. - Separate multiplayer changes from single-player worlds. The Configure a server guide notes that the same settings file can be loaded for single-player worlds. If server experiments must not alter single-player behavior, use a separate game installation.
- Capture a comparable baseline. During a repeatable workload, record the warning text or log excerpt, approximate tick duration, online players and what everyone was doing. Change one relevant value, repeat a similar workload and keep the result with the configuration copy.
Use the tick breakdown to locate the bottleneck
Look for the category that dominates a slow-tick report instead of treating every warning as a memory problem. A breakdown showing chunk generation points toward a different intervention than one dominated by entities or saving.
Recommended Free Tools
| Evidence in logs or symptoms | Likely area to investigate | First settings to consider | Trade-off |
|---|---|---|---|
| Long pauses while players explore new terrain; chunk-generation work is large | World generation and chunk queues | Advanced chunk-request, generation and thread controls in servermagicnumbers.json |
Slower exploration or delayed chunks if reduced; excessive increases can exhaust CPU, memory or network |
| Many entities or mobs; spawning work dominates | Mob-cap scaling and entity simulation | SpawnCapPlayerScaling |
Fewer mobs relative to concurrent players |
| High block-tick work; farms or machines create heavy simulation | Random and scheduled block ticks | MaxMainThreadBlockTicks, RandomBlockTicksPerChunk, BlockTickChunkRange, BlockTickInterval |
Slower growth, fewer updates or less responsive simulation depending on the control |
| Network or client strain while new areas appear | Chunk sending and client delivery | ChunksToSendPerTick and related magic-number controls |
Slower visual loading; higher values can overload clients or the network |
| Large save activity in the slow-tick report | Persistence workload and storage contention | Confirm the timing and storage conditions before changing simulation limits | Reducing unrelated settings may not affect save pauses |
This classification is a troubleshooting framework, not a benchmark. The published documentation does not provide a guaranteed tick reduction for any particular value.
Core server settings that affect workload
MaxChunkRadius: cap player view distance
MaxChunkRadius is the highest view distance a player may select. Larger radii keep more chunks available around players and require more RAM. The configuration guide specifically lists lowering maxchunkradius as a setting to consider when performance is poor. Lower the cap when chunk memory or delivery is implicated, and tell players that the change limits the maximum view distance; it does not increase the simulation speed of every other task.
Rank #2
- Samsung DDR5 Memory RAM | Part Number: M321R8GA0BB0-CQK
- Single 64 GB Module; DDR5 DIMM 288-Pin; Speeds up to 4800 MHz, PC5-38400 (PC5-4800B)
- ECC Registered RDIMM; 2Rx4 (EC8, 10x4); JEDEC DDR5 standard 1.1V
- Compatible for select DDR5 Servers and Workstations; *Not Compatible with Desktop or Laptop Computers*
- Note: EC8 (10x4) ECC Registered modules can not be mixed with EC4 (9x4) ECC Registered modules or with different ECC types such as ECC Unbuffered, ECC Load Reduced or Non-ECC Unbuffered; (Refer to your system's manual for memory seating and channel guidelines)
SpawnCapPlayerScaling: scale mobs with online players
The setting increases the mob cap by its value multiplied by player count and the base cap. A value of zero means the cap does not scale with online players. The guide names lowering spawncapplayerscaling as a performance option. Doing so can reduce entity-spawn pressure as a server fills, but it also means fewer mobs are supported relative to the number of players. Do not claim a fixed tick improvement: the result depends on how much entity work was actually consuming the tick.
MaxClients: limit concurrent connections
The documented default for MaxClients is 16. The configuration page explicitly notes that higher values require more RAM and CPU. This is an admission-control limit, not a capacity guarantee: a machine may struggle below 16 players if the world, mods or workload are demanding.
Block-ticking controls and their gameplay effects
Block ticks are simulation work, so changing their budgets can improve a specific bottleneck while changing how the world behaves. The documentation explains each control but does not publish universal optimal values or controlled performance gains.
| Setting | Documented role | What players may notice |
|---|---|---|
MaxMainThreadBlockTicks |
Maximum number of blocks ticked per server tick | A lower ceiling can limit per-tick work, but pending updates may take longer to process |
RandomBlockTicksPerChunk |
Number of random ticks assigned per chunk | Higher values make grass regrow faster; lower values can slow random-growth and similar processes |
BlockTickChunkRange |
Chunk distance from players for random ticks | The page gives four chunks as up to 128 blocks; reducing the range limits simulation farther from players |
BlockTickInterval |
Milliseconds between random-tick system runs | A longer interval spaces random-tick work and changes simulation timing |
Change only the control that matches the evidence. For example, reducing random-tick range will not fix a server whose report is dominated by chunk generation, and reducing the main-thread block budget may merely create a backlog if the world constantly produces updates. Test farms, crop growth and machines after each change so an apparent performance gain is not an unacceptable gameplay regression.
Rank #3
- A-Tech RAM Memory compatible for select DDR4 Server and Workstation systems only; (*WILL NOT WORK with Desktop or Laptop Computers/PCs*)
- 32GB RAM Kit (2 x 16GB Modules); DDR4 DIMM 288 Pin; Speeds up to 2400MHz PC4-19200 (PC4-2400T)
- ECC Unbuffered UDIMM; 2Rx8 - Dual Rank x8; JEDEC DDR4 standard 1.2V
- Improves system performance, workload capacity, and reduces bottlenecks by increasing memory (RAM) resources
- Note: This memory is ECC Unbuffered and cannot be mixed with different ECC types such as ECC Registered, ECC Load Reduced, or Non-ECC Unbuffered; (Memory compatibility can vary among different system models and their installed components; please verify compatibility and follow memory channel guidelines to ensure maximum performance)
Advanced chunk and thread controls
servermagicnumbers.json contains controls for how many chunks are requested and sent per tick, chunk-generation limits and chunk-thread timing. These values sit below ordinary server configuration because they can interact with hardware, player movement and network bandwidth. The Server Config documentation cautions: “Setting this value too high might overburden the client or the network.” That comment is attached to ChunksToSendPerTick; sending more chunks can make a player’s client or connection the new bottleneck even if the server CPU has spare time.
Requesting or generating too many chunks at once can instead overburden server resources and make the server unstable. Do not copy aggressive numbers from a forum post without understanding which version, hardware and workload produced them. Keep a rollback file, alter one related value, and test with a player exploring the same type of terrain that triggered the warning.
Physics and world-generation threads
The current configuration page documents MaxPhysicsThreads as a range of 1–8 CPU threads and MaxWorldgenThreads as 1–6. These are ranges, not recommendations or benchmarks. More worker threads can improve throughput when the corresponding task is genuinely CPU-bound, but they can also compete with the main tick, operating system and database or storage work. Adjust them only after the breakdown points to physics or world generation, and test stability at the intended player count.
A repeatable tuning procedure
- Reproduce the problem. Use the same approximate player count and activity that normally triggers warnings. Record the longest tick and the diagnostic categories shown around it.
- Choose one intervention. Match the setting to the dominant category: view distance for chunk pressure, mob scaling for entity pressure, block-tick controls for block simulation, or advanced chunk/thread values for generation and delivery.
- Apply a conservative change. Edit the installed version’s generated configuration, preserve formatting and comments where possible, and restart the server if that setting is read only at startup.
- Repeat the workload. Explore comparable terrain, run the same farm or machine area, or reproduce the same save condition. Record whether tick warnings, category times and player-visible delay changed.
- Check side effects. Verify view distance, mob populations, crop growth, machine behavior, chunk loading and client/network symptoms. A lower tick time is not a success if it simply moves the delay to chunk delivery or changes the game in an unwanted way.
- Keep or roll back. Save the tested configuration with a date and description. Restore the backup if the server becomes unstable or the trade-off is unacceptable, then try a different single variable.
Practical playbooks by symptom
Players lag mainly while exploring
First inspect chunk-generation and sending categories. Lowering MaxChunkRadius limits the maximum area each player can request and reduces the RAM requirement associated with larger view distances. If generation itself dominates, evaluate the relevant magic-number queue and world-generation thread settings cautiously. If players see delayed terrain but the server tick remains healthy, investigate sending limits and client or network saturation rather than reducing unrelated block ticks.
Rank #4
- OWC 32GB UPGRADE: Consists of 2pcs of 16GB DDR4 2666MHz PC4-21300 CL19 2RX8 ECC SO-DIMM 1.2V 260-pin Memory Modules Compatible with Synology part numbers D4ECSO-2666-16G, D4ES01-16G
- Compatible for Synology NAS DiskStation, RackStation, FlashStation, & NVR DVA Servers models: DS1522+, DS1618+, DS1621+, DS1621xs+, DS1819+, DS1821+, DS2419+, DS2419+II, DS2422+, DS3018xs, DS3617xs, DS3617xsII, DS3622xs+, DVA3219, DVA3221, FS1018, RS1221+, RS1221RP+, RS822+, RS822RP+
- INCREASED PERFORMANCE: Memory Upgrades are the Most Effective and Easy Way to Boost the Performance of Your Server, Micro Server or NAS System
- INDUSTRY LEADING: Consumer Friendly Advanced Replacement Program and Limited Lifetime Warranty, which Includes Free Tech Support by Other World Computing
- EASY INSTALLATION: In Most Cases Installing Memory is an Easy DIY project. Watch our OWC Basic Installation Video for help.
The server slows as more players join
Check entity and chunk work as player count rises. Lower SpawnCapPlayerScaling if mob-cap growth is the dominant category, accepting fewer mobs per player. Lower the view-distance cap if memory and chunk work scale with the number of players. If the intended population exceeds the machine’s tested capacity, reduce MaxClients rather than allowing connections that make the simulation unusable.
Farms or machines cause periodic long ticks
Inspect block-tick work during the event. Test MaxMainThreadBlockTicks and random-tick settings one at a time, then verify that growth and machine behavior remain acceptable. A longer BlockTickInterval changes when random-tick work runs; it does not remove the work permanently, so compare both peak tick duration and how quickly updates catch up.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWarnings coincide with saving
If the diagnostic output shows save activity, do not assume view distance or mob scaling is the cure. Record when saves occur, whether storage contention is present and whether the same pause appears with a quiet world. Keep simulation changes separate so you can tell whether a save-related pause was actually affected.
Common mistakes to avoid
- Treating 30 TPS as guaranteed.
TickTimeis the desired interval, not a promise of achieved throughput. - Changing several values at once. You lose the ability to identify which setting helped or caused a side effect.
- Blindly copying magic numbers. The documentation warns that high chunk-send values can overburden clients or networks and that aggressive generation settings can destabilize a server.
- Assuming RAM alone fixes lag. More memory helps only when memory pressure is the diagnosed constraint; the documentation gives no universal RAM requirement or player-capacity figure.
- Ignoring the client and network. A server can finish its tick while chunk delivery still overwhelms a player’s machine or connection.
- Testing with a different workload. A setting that helps exploration may do nothing for a machine room or save pause; compare like with like.
What capacity claims the documentation does—and does not—support
The published configuration establishes defaults, ranges and trade-offs, not a universal hardware specification. It states that higher MaxClients values require more RAM and CPU and that larger MaxChunkRadius values require more RAM. It does not establish an ideal amount of RAM, a guaranteed player count, expected FPS, or a fixed percentage of tick improvement from any setting. Hardware compatibility, mod load, world age and player behavior must be evaluated on the actual server.
For a current and reliable baseline, compare your installed version’s generated files with the matching Server Config documentation and the general advice in the Configure a server guide. Keep the forum diagnostic example as a reminder to read the breakdown, not as a benchmark.
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.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →
