Direct answer
Measure hopper-related tick cost and reduce unnecessary inventories, item movement, and always-active contraptions.
What it means
Large numbers of active hoppers and connected inventories can create repeated inventory/item-transfer checks, which may become measurable tick work in dense farms or storage systems.
If you are a player
- Check whether the symptom is low FPS on your own computer, high ping/rubber-banding, or the whole server slowing down; these are different problems.
- Note the exact time, world/area, and action that triggers the lag (exploring, a farm running, saving, many players online, and so on).
- Ask another player whether they see the same delay. Give the owner a reproducible location/action instead of only saying “the server is laggy.”
If you run the server
- Profile a normal busy period and confirm hopper or inventory-move work is actually prominent, especially in large sorters and always-loaded storage rooms.
- Temporarily pause the suspect sorter on a test copy and re-profile the same area; if MSPT improves, inspect continuous hopper checks, item streams and unnecessary inventories.
- Review the current Paper/Spigot hopper settings for your build, but do not blindly disable the inventory-move event: protection, economy and logistics plugins may depend on it.
- Prefer reducing active hopper paths, stopping input when storage is full, and spacing large machines over global changes that break gameplay.
- Test item transport, sorting, plugin integrations, and MSPT after each change under comparable load.
Important notes
- More allocated RAM does not make a slow main-thread workload faster. Change heap size only when memory/GC evidence supports it.
References
Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.
Related fixes and guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.