Spigot.yml Optimization to Reduce Lag

Note: This article is specific to Minecraft Java Edition and assumes you are running a Spigot server.

If you are running a Spigot server, there are several options to optimize performance and ensure smooth gameplay. This guide outlines the Spigot.yml settings you can adjust to improve server performance.

Below is a list of recommended spigot.yml configurations, ordered from the settings with the highest impact on performance to those with lesser impact. For guidance on editing this file, refer to our tutorial on modifying Spigot configurations.

save-user-cache-on-stop-only

Enabling this option prevents user data from being constantly saved while players are online, improving server performance. However, note that if your server crashes, user data will not be saved. Regular backups and frequent server stops are recommended to protect player data.

Default: false Optimized: true

entity-activation-range

This set of settings adjusts how close mobs and other entities must be to activate their AI. Numbers indicate the distance in blocks entities can travel before being deactivated. Entities reactivate when a player gets close enough.

• animals: 16

• monsters: 24

• raiders: 48

• misc: 8

  
  

merge-radius

Increasing the merge radius will group items and experience more frequently, reducing the number of active entities generating processes (“ticking”). Be careful: setting it too high can cause items to teleport through blocks or into dangerous locations (like lava).

• item: 4.0

• exp: 6.0

  
  

nerf-spawner-mobs

For servers that rely on mob spawners, this option boosts server performance by making mobs spawned from spawners have no AI.

Default: false Optimized: true

max-tick-time

Due to the risks associated with enabling this feature, which skips ticking on some entities and blocks in a way that can affect gameplay, it’s best to set this to 1000, effectively disabling the function.

• tile: 1000

• entity: 1000

  
  

mob-spawn-range

Adjust the chunk distance from a player where mobs can spawn. This helps ensure fewer mobs are active in areas inaccessible to players. Keep this lower than the view-distance so mobs actually spawn for players.

Default: 8 Optimized: 6

arrow-despawn-rate

Arrows shot by players in survival mode will despawn faster (measured in ticks), reducing the number of active entities. 300 ticks roughly equals 15 seconds.

Default: 1200 Optimized: 300

item-despawn-rate

Dropped items on the ground will disappear after a set number of ticks. Do not set too low or players may lose valuable items. 4000 ticks roughly equals 3.3 minutes.

Default: 6000 Optimized: 4000

tick-inactive-villagers

Introduced in version 1.14, new villager mechanics can cause significant lag if not optimized. Setting this to false prevents villagers outside the activation range (see above) from being ticked.

Default: true Optimized: false

You can further boost your Spigot server’s performance by optimizing Bukkit and Paper. Learn how to fine-tune your Bukkit settings in our Bukkit.yml Optimization Guide. If you’re using PaperMC, check out our Paper.yml Optimization Guide to get the most out of Paper.

Conclusion

We hope this guide has been helpful! 🚀 Remember, don’t hesitate to ask questions on the HolyHosting Discord or contact our support team.

Follow us on Twitter @HolyHosting to stay up to date.

Stuffy @ HolyHosting