Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The best settings for a modded Minecraft server are conservative distances, workload-based memory allocation, and measured changes rather than a copied JVM flag list. Use view-distance=10 as a documented starting reference, keep simulation-distance equal to or slightly below it, then lower both when profiling shows chunk-loading or tick pressure. Leave RAM for the operating system, use fast CPU cores after assigning a reasonable heap, and profile with spark during the activities that actually cause lag.
There is no universal configuration for every modpack. A lightly populated exploration server, an automation-heavy world, and a server generating new terrain can need very different settings. The procedure below gives you a repeatable way to find the right balance on Forge, Fabric, or a compatible loader.
![Minecraft: Story Mode – A Telltale Games Series [Online Game Code]](https://m.media-amazon.com/images/I/51R9dPuwNaL._SL160_.jpg)
What the important server settings actually control
Two values in server.properties have the largest immediate effect on a modded server: view-distance and simulation-distance. They reduce different kinds of work, so changing only one can leave the real bottleneck untouched.
view-distance: chunks sent to players
view-distance controls the radius of chunks the server sends to each client. A larger value lets players see farther, but it also increases chunk transmission, loading, and the amount of world data that must be kept available around every player. Several players travelling in different directions multiply that work.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
simulation-distance: chunks that remain active
simulation-distance controls the radius in which the world continues actively ticking. Entities, redstone, crops, machines, mob farms, and other mod systems can stop updating outside this area. Lowering it can substantially reduce tick work, but it also changes gameplay: farms may pause sooner, distant redstone may stop, and mobs or automation outside the active area may behave differently.
Why the values should be tuned together
Forge server guidance recommends lowering both distances when needed and keeping simulation distance equal to or marginally lower than view distance. Setting simulation distance above view distance asks the server to simulate chunks players are not receiving, which spends tick time without improving what they can see. Keeping the values together makes the trade-off explicit: view distance controls what clients receive; simulation distance controls what the server actively updates.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 safe starting point in server.properties
Paper’s current reference lists view-distance=10 as a default baseline. Treat that as a documented reference, not a guarantee that 10 is optimal for your modpack or hardware. Begin there only if the server remains responsive under a representative workload; otherwise profile and reduce both values.
| Setting | Starting approach | What to watch | Gameplay trade-off |
|---|---|---|---|
view-distance |
Use 10 as a baseline reference, then lower it when chunk loading or network delivery is expensive. | Chunk-generation spikes, slow exploration, client-side stalls, and per-player load. | Players see less terrain at once. |
simulation-distance |
Set it equal to or slightly below view-distance. |
Tick time, entity and machine activity, farm behavior, and redstone updates. | Distant farms, mobs, and automation may stop updating sooner. |
| Heap allocation | Assign only what the modpack and workload need; do not consume all physical RAM. | Garbage-collection pauses, memory growth, operating-system pressure, and swapping. | Too little memory causes allocation pressure; too much can starve the rest of the machine. |
Change these values while the server is stopped, keep a copy of the original file, and restart before evaluating the result. A setting that looks fine while one player stands still can fail when several players explore, generate terrain, run farms, and load machines simultaneously.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
How to choose view-distance and simulation-distance
Start with the documented baseline
- Record the current values and the Minecraft version, loader, modpack version, Java version, player count, and hardware.
- Set
view-distanceto 10 if you need a neutral reference point. - Set
simulation-distanceto 10 or a marginally lower value, never higher than view distance. - Restart and reproduce normal play before deciding whether the values are acceptable.
Lower distances when the profile identifies pressure
If spark shows that chunk loading or generation consumes a large part of the tick budget, lower both distances by one step, restart, and repeat the same travel route. If the profile instead shows entity logic, block ticking, or a particular automation system consuming time while players remain near established terrain, reducing simulation distance is the more direct test. Lower view distance as well when sending and maintaining distant chunks remains expensive.
Check gameplay before keeping a lower value
- Travel through a new area and watch for delayed chunk appearance or generation stalls.
- Stand at the normal operating position of farms and confirm that crops, mobs, redstone, and machines update as intended.
- Test the farthest automation or redstone circuit that players are expected to use.
- Ask players whether the reduced horizon is acceptable; a technically stable server can still feel wrong if exploration visibility is a core feature.
Do not compensate for a mod that performs badly by reducing distances indefinitely. Once the profile points to a specific subsystem, investigate that mod’s configuration, update path, or compatibility instead of hiding the problem with an increasingly small active world.
How much RAM does a modded Minecraft server need?
There is no honest single number for every modded Minecraft server. Required memory depends on the Minecraft and loader versions, the modpack, world size, player count, exploration rate, entity population, automation, and how long the server stays online. Forge specifically warns against allocating excessive RAM, especially when self-hosting, because the operating system, drivers, file cache, and other services still need memory.
Use a workload-based allocation
- Start with a reasonable heap allocation that leaves clear headroom for the operating system and any other services on the machine.
- Run the server through a normal session that includes the busiest expected combination of players, exploration, chunk generation, machines, and mob activity.
- Use spark to observe heap use, instance memory, and garbage-collection behavior rather than judging by the amount of RAM installed.
- If the heap repeatedly approaches its limit and garbage collection becomes frequent or causes pauses, increase allocation in a controlled step and repeat the same workload.
- If the process rarely needs the allocated heap while the host is under memory pressure, reduce the allocation and retest.
More heap is not automatically faster. An oversized allocation can leave too little memory for the operating system and file cache, cause contention with other applications, or make garbage-collection cycles more disruptive. Conversely, a heap that is too small can trigger repeated collection and allocation failures. The useful value is the smallest allocation that remains stable during the server’s real peak workload with operating-system headroom.
Rank #3
![Minecraft Dungeons: Standard Edition – Windows 10 [Digital Code]](https://m.media-amazon.com/images/I/41TayT2RhCL._SL160_.jpg)
- Fight your way through an all-new action-adventure game, inspired by classic dungeon crawlers and set in the Minecraft universe!
- Play with up to four friends or brave the dungeons alone. Battle new-and-nasty mobs across action-packed, wildly varied levels, in a quest to defeat the evil Arch-Illager!
Why copied JVM flag strings are risky
Custom JVM arguments interact with the Java version, garbage collector, heap size, operating system, and modpack behavior. Forge guidance says to test before and after using custom arguments; it does not provide a one-size-fits-all recipe. Establish a baseline, change one JVM setting or argument at a time, and retain a change only when tick timing, pause behavior, and memory use improve under the same workload. If a change makes pauses longer, increases memory pressure, or produces crashes, revert it rather than stacking another flag on top.
CPU and hardware priorities
After assigning a reasonable heap, fast CPU cores can matter more than additional RAM. A modded server combines the core game tick with chunk generation, entity AI, block and fluid updates, automation networks, and mod-specific systems. Modern Minecraft is not purely single-threaded, so additional fast cores can help some workloads, but the benefit depends on how the loader and individual mods schedule work.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Match hardware to the workload
- Many players exploring: prioritize strong single-core performance and enough additional cores for concurrent chunk generation and background services.
- Automation-heavy bases: prioritize fast tick execution and profile the machines, entities, and block updates that remain active near players.
- Frequent new-world generation: expect short CPU and storage spikes during travel; evaluate the server while players are actually generating terrain.
- Self-hosting: reserve capacity for the operating system, backups, monitoring, and other applications instead of assigning the entire machine to Java.
Buying or assigning more RAM cannot repair a CPU-bound tick. Confirm the bottleneck with a profile before changing hardware or hosting resources.
Measure before tuning with spark
spark is a profiler for Minecraft clients, servers, and proxies. Install the build that matches the exact Minecraft version and loader, then profile the server during representative play instead of while everyone is idle.
Rank #4
- 8,800 MINECOINS — Get 8,800 Minecoins to spend on creator-made content in the Minecraft Marketplace.
- MINECRAFT MARKETPLACE — Browse a constantly updating library of content from Minecraft creators, with new content available every week.
- CREATOR-MADE CONTENT — Use Minecoins to get Marketplace content such as skin packs, mash-up packs, mini-games, and adventure maps.
- ACCESS ACROSS DEVICES — Once redeemed and linked to your Microsoft account, your Minecoins and purchases are available on supported devices that run Minecraft, including Android, iOS, Windows, and Xbox.
- A GIFT FOR PLAYERS — Give Minecraft players Minecoins to spend on content in the in-game Marketplace.
Capture a useful baseline
- Note the server version, loader, modpack revision, Java version, CPU, available memory, current distances, and concurrent players.
- Start a spark profile before the workload begins.
- Run normal travel, enter and leave the busiest base, activate automation, load mob farms, and generate new chunks if those activities occur on your server.
- Include the busiest expected player period; a profile with one idle player cannot validate a public server configuration.
- Stop the profile and record tick time or TPS stability, chunk-loading responsiveness, heap and instance memory, and garbage-collection behavior.
Read the profile by symptom
| Observed symptom | Likely direction for investigation | First controlled test |
|---|---|---|
| Tick time rises during exploration and chunk generation. | Chunk generation, loading, storage, or CPU capacity. | Lower both distances, repeat the same route, and inspect the profile for the responsible subsystem. |
| Tick time rises near a base with machines or mobs. | Entity logic, block ticking, automation, or a mod subsystem. | Temporarily reduce simulation distance and profile the base again; then inspect the named mod or system. |
| Long pauses coincide with garbage collection. | Heap pressure, allocation pattern, or an unsuitable JVM change. | Compare memory and pause behavior with the custom argument removed or with a carefully adjusted heap. |
| Memory remains stable but ticks are slow. | CPU-bound game or mod logic rather than insufficient heap. | Use the CPU view to identify the subsystem before adding RAM. |
The 50-millisecond tick budget
A Minecraft server tick has a 50 millisecond budget. Sustained work above that budget produces delayed updates and falling TPS. A single short spike during world generation is less concerning than repeated overruns during ordinary play, so compare profiles over the same duration and workload.
Use spark’s CPU, heap, instance-memory, garbage-collection, and server-behavior views together. A CPU hotspot with normal memory points toward a mod or workload that needs configuration or replacement. A memory graph that climbs continuously, followed by long collections, calls for heap and allocation investigation. A chunk-loading hotspot during travel suggests distance, generation, storage, or CPU pressure rather than a blanket JVM change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Optimization mods: where Lithium fits
Lithium is a general-purpose optimization mod covering systems such as physics, mob AI, block ticking, and data tracking. Its project documentation says it can run server-side without requiring clients to install it, and it supports compatible Fabric and NeoForge installations. The project claims that some users can see more than a 50% improvement in tick times; treat that as the project’s claim, not a guaranteed result for every modpack.
Check compatibility before installing
- Match the Lithium build to the exact Minecraft version and loader.
- Read the modpack author’s instructions and the loader’s compatibility information.
- Check whether another optimization changes the same subsystem.
- Back up the world and configuration before adding or removing a performance mod.
- Profile before and after installation using the same player actions and duration.
An optimization mod can expose an incompatibility, alter behavior that another mod expects, or simply be irrelevant to the actual bottleneck. Keep it only when the measured result is positive and gameplay remains correct.
A repeatable tuning order
- Document the environment. Write down Minecraft, loader, modpack, Java, player count, hardware, storage, and current
server.propertiesvalues. - Establish a baseline. Use spark during normal travel, chunk generation, automation, mob activity, and the busiest expected period. Record tick time or TPS, memory, and garbage collection.
- Align distances. Keep
simulation-distanceequal to or belowview-distance. Lower both if the profile identifies chunk or ticking pressure. - Correct heap sizing. Remove excessive allocation and leave memory for the operating system and other services.
- Test JVM changes individually. Compare one change before and after under the same workload; revert changes that do not improve the measured result.
- Investigate the named subsystem. Inspect the mod, machine network, entity area, or world-generation path identified by spark. Update, configure, replace, or remove it only after confirming the evidence.
- Validate gameplay. Check farms, redstone, machines, exploration, and multiplayer behavior after every meaningful change.
- Re-test after upgrades. A new mod, loader, Minecraft version, Java version, or world can change the bottleneck, so repeat the baseline instead of assuming old settings still apply.
How do I reduce lag on a Forge/Fabric server?
Start by deciding whether the lag is a tick problem, a chunk-loading problem, a memory-pause problem, or a client/network symptom. The fix differs for each.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →If TPS falls near farms or bases
Profile the area with spark, lower simulation distance for a controlled comparison, and inspect the hottest entity, block-ticking, or automation subsystem. Reduce unnecessary entities or machine activity only after confirming which system consumes the tick budget. A lower distance can reduce active work, but it should not be used to conceal a misconfigured machine network permanently.
If exploration causes freezes
Profile while travelling through new terrain. Lower view and simulation distance together, test the same route, and check whether chunk generation or storage becomes the dominant activity. If CPU remains saturated after the distance change, faster cores or a host with stronger per-core performance may help more than additional heap.
If the server pauses during garbage collection
Compare heap usage and collection behavior in spark. Remove untested JVM arguments, ensure the process is not competing with other applications for memory, and adjust allocation only in a controlled before-and-after test. Keep the smallest stable heap that handles the measured peak workload.
If players report lag but the server profile is healthy
Check whether the complaint is limited to one player, one route, or one client. View distance affects the chunks sent to clients, while simulation distance affects server activity; neither alone explains every network or client-rendering problem. Compare server tick timing with the player’s connection and client performance before changing server-wide values.
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 →Managed hosting considerations
Managed modded Minecraft hosting can be useful when you cannot maintain Java, backups, monitoring, and loader updates yourself. Evaluate it by the resources and controls it actually provides: dedicated or shared CPU capacity, guaranteed memory, storage performance, geographic location, automated backups, restore procedures, console access, supported Forge and Fabric versions, and limits on changing server.properties or JVM arguments.
Ask how support handles a profiler report and whether you can reproduce a workload before and after a resource change. A plan advertising more RAM is not automatically faster if its CPU cores are slower or heavily shared. The same measurement procedure applies on hosted and self-hosted servers.
Quick Recap
Maintenance checklist
- Keep a dated copy of
server.properties, JVM arguments, loader version, and mod list. - Back up the world before changing optimization mods or removing a mod.
- Profile after major modpack, loader, Minecraft, or Java updates.
- Repeat the same workload when comparing settings; otherwise the comparison is not meaningful.
- Document gameplay checks for farms, redstone, machines, mobs, and exploration.
- Prefer one measured change over several simultaneous tweaks.
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.
