Direct answer
Spigot ignore-spectators is an entity activation-range setting; whether spectators wake nearby entities is separate from spectator visibility or permissions.
How to check it
- With a spectator account and a survival player, compare a test mob farm while only the spectator is near it. Check your fork’s generated
spigot.ymland activation range. - 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
Ignoring spectators can reduce entity activity caused by staff cameras or spectator hubs, but changes behavior in minigame spectating and monitored farms. Test admin observation workflows carefully.
Do not use this option to infer that spectator accounts stop loading chunks or consuming network traffic.
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.