Direct answer
Leaf has historically exposed performance.throttle-hopper-when-full, which delays repeated checks against full inventories. The public config reference is from 1.21.1; check the current generated file first.
How to check it
- Test a sorter whose output container remains full and compare it with the same sorter after overflow routing. Inspect the actual Leaf key and skip-tick units before changing it.
- 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
Throttling can save unnecessary inventory checks but must not hide uncollected items. Prefer fixing overflow or buffer design before adding a fork-only throttle option.
Verify that inventory event listeners, hopper clocks and collection latency behave acceptably on your selected Leaf build.
Software and version notes
Before using any example, confirm that your exact server build exposes this option and that a per-world override does not take precedence. Leaf examples from publicly available 1.21.1 documents are historical; do not assume the same keys or defaults apply to later builds.
This article is written for Leaf. Configuration keys and defaults can move between versions. The source material checked for this page includes Leaf global configuration. 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.