Direct answer
hopper-amount is the number of items moved per successful transfer, limited by the stack size. It is not a tick interval.
How to check it
- Inspect
world-settings.default.ticks-per.hopper-amountin the currentspigot.yml; run a short sorter test that counts delivered items over a fixed time window. - 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
Raising amount moves larger batches and can change item-sorting, economy automation and redstone timing. Compare it separately from hopper-check and hopper-transfer, which control when attempts occur.
Use one known item sorter and one full-container case to confirm no item loss or misrouting.
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.