Direct answer
A hopper repeatedly checking a full destination can waste attempts; this is different from a hopper holding items or an item entity lying on the ground.
How to check it
- Identify where the sorting line reaches a full chest. Temporarily route overflow to a separate buffer and compare the same item throughput and MSPT.
- 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
Paper exposes hopper.cooldown-when-full in its world configuration. Check the exact generated file and whether it is already enabled; redesign overflow handling before changing unrelated hopper-transfer intervals.
Verify item filters and full-container behavior. Disabling hopper InventoryMoveItemEvent is not a safe shortcut for servers with protection plugins.
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 profiling guide. 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.