Direct answer
This option changes a redstone rail mechanic. Its value should be chosen for minecart track behavior, not used as a generic fix for server lag.
How to check it
- Find the powered-rail
activation-rangeoption in the generated Purpur world settings. - Build a small isolated test track containing more rail pieces than one source should normally activate.
- Record which segments light up and test minecart travel with the current setting.
What to change
- Back up the world and save the old Purpur setting.
- Change the range only if the server design needs different powered-rail behavior; avoid assuming a smaller range always improves performance.
- Restart if the configuration requires it and retest the same rail circuit.
Software and version notes
Compatibility and safety
Purpur documentation describes this as the number of powered rails activated by a redstone source. It is unrelated to Spigot entity-activation-range, which controls entity ticking. Check the per-world path in the config generated by your specific version.
Verify the result
Confirm the track powers exactly as intended with carts and redstone; check farms and transport systems for regressions.