Direct answer
ticks-per.hopper-check controls the interval between attempts to pull items into a hopper; it is not the number of items transferred.
How to check it
- Use a test input hopper with a stable supply and measure how quickly it pulls objects from above. Inspect the exact
spigot.ymlversion to locate the key. - Record the original configuration or test conditions, capture a profile or a repeatable observation, and identify the affected world or player group.
- Make the measurement under the same player count and workload you will later use to verify the change.
What to change
A larger interval can reduce repeated checks but slows pickup in some farms. Keep hopper-amount and hopper-transfer constant during this experiment so the effect is attributable to the check interval.
Verify common auto-sorters and pickup timing; a lower profiler cost is not useful if collectors miss or back up items.
Software and version notes
Check the active version and generated configuration before copying paths or values. Different forks and mod loaders may implement this behavior differently.
This article is written for Paper / compatible servers. Configuration keys and defaults can move between versions. The source material checked for this page includes PaperMC spigot.yml reference. If your server is Folia, Leaf, Purpur, Fabric, Forge, NeoForge, or another fork/loader, do not assume a Paper-only setting exists or behaves identically.
Verify the result
Repeat the same test with the same software build, player count and world activity. Compare the targeted symptom and any spark measurements, then check that intended game mechanics still work. If the change does not produce a reproducible improvement, revert to the recorded baseline.