The safest way to reduce Minecraft server lag with spigot.yml is to measure the bottleneck first, then change only the settings that address it. Lowering every value from a preset can damage farms, item recovery, redstone timing, mob AI, and player visibility without fixing the actual cause.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
Use Spigot Timings to identify whether the pressure comes from chunk loading, entity AI, dropped items, hoppers, explosions, or long tile/entity tasks. Change one related group, restart, reproduce the same workload, and keep a rollback copy. The values below are starting points and documented examples—not guaranteed TPS improvements.
As an Amazon Associate I earn from qualifying purchases.
What spigot.yml can—and cannot—fix
spigot.yml controls several server-side workloads, but its settings do different jobs. view-distance determines how many chunks are loaded around each player. entity-activation-range determines how far away entities continue normal AI and logic ticking. entity-tracking-range determines how far entities are sent to clients. Item merging and despawning control the number and lifetime of dropped-item entities. Hopper, TNT, collision, and tick-budget settings target narrower workloads.
That distinction matters. A lower tracking range can reduce what clients receive, but Spigot’s configuration reference says it does not improve server performance in the same way as reducing loaded chunks or entity ticking. Conversely, lowering activation ranges may improve server work while changing mob farms or distant AI. No official documentation establishes a universal percentage gain for any value, so judge a change by measured tick time under your own workload.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Always match the syntax and available keys to the exact Spigot or Paper version. Paper’s current reference includes categories and controls—such as raiders, water mobs, villagers, flying monsters, and wake-up behavior—that are absent from many older Spigot examples.
Profile before editing
Spigot’s reducing-lag guidance explicitly recommends finding the cause first instead of copying an aggressive configuration. A useful baseline records the server software and version, online-player range, worlds, plugins, and whether farms, villagers, hoppers, redstone, or TNT are central to play.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors- Back up the file and world data. Copy
spigot.ymlto a dated location before every experiment. Keep the previous working file available for an immediate rollback. - Record a repeatable workload. Note player count, dimensions in use, approximate loaded areas, and the activity that produces lag. A crowded spawn, a villager hall, a mob grinder, and a TNT machine stress different settings.
- Capture Timings. Use Spigot Timings during the problem period and inspect which tasks consume tick time. In versions exposing the traditional commands, operators commonly start collection with
/timings onand create a report after reproducing the issue; command names and report handling vary by software version. - Classify the hotspot. Decide whether the evidence points to chunks, entity AI, item entities, hopper transfers, explosions, collisions, or tile/entity tasks exceeding their budgets.
- Change one group at a time. Restart, reproduce the same workload, and compare tick-time behavior. Do not change view distance, activation ranges, hopper cadence, and despawn rates simultaneously; you will not know which trade-off caused a result.
- Test gameplay after each restart. Check mob and villager behavior, farms, item pickup and recovery, redstone timing, hopper throughput, visibility, and TNT contraptions before keeping the change.
Core distance settings
view-distance: reduce loaded chunks when players are the cause
Spigot documents a default of 10 chunks and describes view-distance as the number of chunks loaded around each player. The cited reference constrains values to 1–15. Lowering it can reduce chunk loading and memory/work pressure when many players are spread across the world.
This is a chunk-loading control, not a general cure for plugin code, entity AI, hoppers, or item piles. Players will see a shorter world horizon, and redstone or farms just outside the loaded area may stop operating until someone moves closer. Test the lowest distance that still supports your server’s exploration and farm design rather than selecting a low value by habit.
entity-activation-range: reduce distant AI ticking carefully
In the documented Spigot defaults, animals and monsters use 32 blocks, while miscellaneous entities use 16 blocks. Entities outside their activation range tick at a reduced rate instead of running normal behavior every tick. Lower values can produce a substantial reduction in entity work, but they can also alter AI, farms, pathfinding, and the behavior of distant mobs.
Spigot’s lag guide shows this aggressive experimental example:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
entity-activation-range:
animals: 8
monsters: 10
misc: 2Those numbers are not recommended defaults. Use them only after Timings identifies entity ticking as the problem, and test every farm that depends on mobs remaining active away from a player. A mob may move, attack, breed, or process slower when outside the normal range. Paper’s current reference exposes more granular categories, including raiders, water mobs, villagers, and flying monsters, together with wake-up controls; do not paste a category from a newer Paper reference into an older Spigot build that does not support it.
entity-tracking-range: a visibility and bandwidth control
Spigot’s documented defaults are 48 blocks for players, animals, and monsters; 32 blocks for miscellaneous entities; and 64 blocks for other entities. Tracking range controls what is sent to a client and therefore affects visibility and network traffic. The Spigot reference states that lowering it does not improve server performance; it primarily addresses client-side bandwidth or visibility concerns.
Paper’s current reference lists version-specific tracking ranges, so verify the active software before editing. A shorter range can make mobs or projectiles appear late or disappear at a distance even while the server continues processing them.
Control dropped-item and experience-entity load
merge-radius: combine nearby entities sooner
The documented defaults are an item radius of 2.5 blocks and an experience radius of 3.0 blocks. Increasing these radii lets nearby item or experience entities merge sooner, reducing the entity count in farms and collection areas. The trade-off is altered pickup and collection behavior: items that previously remained separate can combine into a larger stack.
Free tools Windows power users keep installed
One-click scans. No signup required.
Spigot’s lag guide gives item 4 and experience 6 as an example for a measured item-entity problem. Treat that as a test value, not a universal setting, and verify hoppers, water streams, item filters, and XP collection afterward.
item-despawn-rate: remove abandoned drops faster
Spigot documents a default of 6,000 ticks. Lowering it removes dropped items sooner and can reduce the number of item entities a busy world must process. The cost is permanent loss: when keep-inventory is disabled, a player may be unable to recover drops after a death or temporary disconnect.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
The reducing-lag guide gives 1,200 ticks—about one minute—as an example for worlds with many loaded entities. Use a shorter period only where item recovery is not a core expectation, such as a controlled technical world, and communicate the rule to players before deployment. Test death drops, delayed minecart or water collection, and any farm whose output waits for a player.
Mob spawning and activation workloads
mob-spawn-range: change the radius only when spawning is the issue
Spigot documents a default of 4 chunks. It is the radius around players in which mobs can spawn. Lowering it reduces the number of chunks offering valid spawn locations, which can prevent some spawns rather than merely reducing server work. Increasing it spreads mobs over a larger area and can make them appear rarer at a particular farm.
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 →Adjust this setting only when Timings and gameplay observations show a spawn-distribution or spawn-workload problem. Recheck hostile-mob farms, passive-animal availability, and the server’s intended mob-cap behavior after every change.
nerf-spawner-mobs: target spawner AI, not all mobs
The documented nerf-spawner-mobs option disables most AI for mobs originating from spawners. It can reduce pathfinding and behavior work in dense grinder rooms, but it changes how those farms function. Because it does not target naturally spawned mobs, it is appropriate only when spawner output is the diagnosed source of load. Test collection rates, mob movement, and player safety around the spawner before enabling it.
max-entity-collisions: limit packed-pen collision work
Spigot documents a default of 8 for max-entity-collisions. The limit caps collision processing for entities packed into a small space, such as animal pens or mob chambers. A lower cap can help when collision calculations dominate, but it may change cramming, pushing, breeding, minecart, and item-interaction behavior. Use it for a measured collision hotspot rather than as a blanket lag fix.
Hoppers, redstone, and transfer cadence
For hopper-heavy servers, Spigot’s lag guide suggests testing hopper-transfer: 24, hopper-check: 24, and hopper-amount: 3. The exact effect depends on the version’s tick configuration. The reference defines hopper-amount as the maximum number of items moved during one hopper tick cycle.
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 #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
These values change timing and throughput, not just CPU use. Transfers happen less frequently or move fewer items, so storage systems can back up, item filters can behave differently, and redstone clocks may no longer match expected timings. Apply the group only after identifying hopper work in Timings, then run a full test of sorting systems, furnaces, farms, minecart loaders, and overflow protection. If throughput becomes unacceptable, restore the previous copy rather than compensating by adding more hoppers.
TNT and explosion bursts
max-tnt-per-tick limits how many TNT entities may explode in one tick. Spigot’s reducing-lag guide suggests 10 when player TNT creates burst lag. This is a workload-specific cap: it can smooth a large detonation, but it also changes cannons, quarry machines, and timed contraptions. Test the largest legitimate explosion your server permits and explain the cap to players who build technical machines.
Tick budgets: max-tick-time
Spigot documents separate tile and entity budgets under max-tick-time, with defaults of 50 ms each. When a task exceeds its budget, the server can skip to the next task. Lower values may prevent one category from monopolizing a tick, but the skipped work can appear as gameplay stutter. The reference specifically warns that a lower entity value can make entities appear to lag.
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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe lag guide shows an aggressive example of tile: 8 and entity: 16 milliseconds. These are experimental values, not safe universal defaults. A low budget may hide a stall by deferring work while making redstone, block entities, or mob movement less smooth. Change it only after identifying long tile or entity tasks, and compare both average tick time and visible stutter under the same load.
Chunk processing and growth settings
chunks-per-tick
Spigot documents a default of 650 for chunks-per-tick. Lowering it can save resources by processing fewer chunk operations in a tick, but crop and related growth work may take longer. Use it when chunk-processing pressure is measured, and observe world generation, scheduled block updates, and farm output over a representative play session.
growth modifiers
Growth modifiers default to 100. Spigot explicitly states that changing these values does not improve performance by itself. They are gameplay controls for crop, cactus, cane, mushroom, and other growth behavior, not a lag remedy. Leave them unchanged unless your objective is to alter growth rates and you have accepted the resulting farm-economy changes.
Version-aware configuration
Older Spigot examples often show only animals, monsters, and miscellaneous entities in activation ranges. Current Paper documentation can expose additional categories, wake-up settings, and different tracking defaults. A key that is valid on one build may be ignored, renamed, or rejected on another.
- Record the exact server software, build, and Minecraft version beside every backup.
- Compare the shipped configuration comments for that build with the relevant Spigot or Paper reference.
- Do not assume a value described in a 2016 reference is the current default on a 2026 server.
- After an upgrade, regenerate or review configuration files so new keys and defaults are visible before tuning.
Practical profiles for common bottlenecks
The following profiles organize documented values by symptom. They are starting experiments, not promises of a particular TPS result.
| Diagnosed workload | Settings to test | Expected trade-off |
|---|---|---|
| Many players loading distant terrain | Lower view-distance from the default of 10 in small steps |
Shorter visible and loaded horizon; distant farms may pause |
| Dense entity AI or pathfinding | Reduce relevant entity-activation-range categories; test the 8/10/2 example only as an aggressive experiment |
Slower distant AI and possible farm or villager behavior changes |
| Large item or XP piles | Increase merge-radius; consider a shorter item-despawn-rate |
Different collection behavior and possible unrecoverable drops |
| Hopper-heavy automation | Test hopper transfer/check at 24 and amount at 3 | Lower transfer cadence or throughput; systems can back up |
| TNT burst lag | Test max-tnt-per-tick: 10 |
Large detonations and cannons behave differently |
| Long tile or entity tasks | Investigate max-tick-time; 8/16 is an aggressive guide example |
Deferred work and visible stutter if budgets are too low |
Troubleshooting after a change
TPS improves but farms stop working
Inspect activation range, spawn range, spawner AI, and tick budgets first. Restore the last working file, then increase only the category needed by the farm. A farm that requires a player to stand close may be incompatible with a globally reduced activation range.
Players report missing items
Check item despawn and merge behavior, then reproduce a death drop and a delayed collection cycle. A shorter despawn period is not appropriate where recovery is promised. Restore the original period if items disappear before players can reach them.
Redstone or storage systems back up
Review hopper cadence and amount. Compare a measured transfer cycle with the pre-change behavior, including filters, furnace inputs, minecart loaders, and overflow chests. Throughput problems require reversing or relaxing hopper changes, not lowering unrelated entity settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Mobs appear late or vanish at a distance
Separate tracking from activation. Tracking changes what the client receives; activation changes how entities tick. Check both the configured range and the software version’s category names before changing values again.
Lag remains after all distance values are lowered
Return to Timings. Persistent lag may come from a plugin, a single world, chunk generation, tile entities, or a workload not addressed by spigot.yml. More aggressive global reductions can make the game less reliable without removing that underlying hotspot.
Quick Recap
A rollback and validation checklist
- Keep the original and experimental YAML files with dates and server versions.
- Validate indentation and key names after every edit; YAML formatting errors can prevent startup or silently leave a default active.
- Restart rather than assuming a live reload applied every setting.
- Repeat the same player count and workload used for the baseline.
- Compare measured tick time, not just a brief feeling of smoothness.
- Have players test farms, villager trades, mob visibility, item recovery, hopper throughput, redstone timing, and TNT limits.
- Roll back immediately when a change causes data loss, broken progression, or unacceptable behavior.
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.
