Direct answer

ticks-per.hopper-transfer is the delay between hopper item movements in the Spigot configuration. It changes transfer cadence, not how many items are moved per attempt.

How to check it

  1. Watch a timed hopper chain and record items transferred per minute. Change only hopper-transfer on staging, leaving hopper-check and hopper-amount unchanged.
  2. Record the original configuration or test conditions, capture a profile or a repeatable observation, and identify the affected world or player group.
  3. Make the measurement under the same player count and workload you will later use to verify the change.

What to change

A longer interval may reduce hopper activity but reduces throughput and changes sorter timings. Verify the target version has this key and that the server actually loads the edited configuration.

Gameplay and compatibility warning

Test overflow, chest minecarts and time-sensitive item filters before any production change.

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.

References