spigot.yml Explained

spigot.yml is one of the main configuration files on Spigot and Paper servers. It includes performance-sensitive settings, but it is also easy to over-tune.

#Sections Worth Understanding

| Section | Why it matters | | --- | --- | | Entity activation range | Controls when entities tick actively | | Entity tracking range | Controls how far entities are sent to players | | Watchdog | Handles server non-response behavior | | Growth modifiers | Changes crop and block growth rates | | Commands | Controls logging, overrides, and command behavior |

Do not edit every value in a public optimization list. Focus on the section that matches your profile.

#Entity Activation Range

Activation range can reduce work by making far-away entities tick less actively. It is useful on entity-heavy servers, but it changes behavior.

Watch for side effects:

1. Farms behaving differently.
2. Mobs seeming inactive at distance.
3. Animals or villagers waking less often.
4. Combat arenas feeling strange.
5. Player expectations changing without warning.

Use entity lag explained before lowering values.

#Entity Tracking Range

Tracking range affects how far players receive updates about entities. Lower values can reduce network and entity update pressure, but players may notice entities appearing late or vanishing at shorter distances.

Good candidates for review are crowded hubs, minigames, and servers with many decorative entities. Survival exploration may need more conservative changes.

#Watchdog Settings

The watchdog helps detect when the server stops responding. Do not increase watchdog time just to hide crashes or freezes. If the watchdog triggers, read logs with the startup log classifier and look for the blocked operation.

#Safe Editing

1. Back up spigot.yml.
2. Change one section.
3. Restart cleanly.
4. Test gameplay that section affects.
5. Profile the same workload again.

For broader Spigot tuning, use the Spigot optimization guide.