Direct answer
entity-broadcast-range-percentage in server.properties scales the distance at which the server sends entity information to clients; it is not the same as ticking or mob activation.
How to check it
- Observe client-side entity pop-in and outbound traffic near a crowded hub. Compare with a spark profile to see whether the main burden is tracking/packets rather than AI ticks.
- 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
Adjust the percentage conservatively if bandwidth or tracking is proven to be the issue, and review entity-tracking-range in spigot.yml separately. The effective visibility can depend on both limits.
Too aggressive a reduction causes players or projectiles to appear late; use PvP and spectator tests.
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.