Direct answer
Optimized powered rails targets rail power handling. This is a separate optimization from the older Leaf minecart-ticking option; a rail network can use one, both, or neither depending on the installed build.
This is a Leaf-specific configuration option, not a general Paper or Folia setting. Confirm the key is present in the configuration generated by your own build before changing it.
How to check it
- Find a powered-rail system with repeatable acceleration, detector-rail logic and redstone toggling.
- Measure redstone or rail updates specifically; a minecart entity profiler cost may have a different cause.
- Record whether your build exposes optimized-powered-rails and what value it currently generates.
What to change
- Find optimized-powered-rails under performance in the generated config. Its displayed default differs between published Leaf configuration references.
- Do not infer the current default from older blog posts or third-party optimization packs. Test the effect on a backup copy, one key at a time.
- Copy the current configuration and note the previous value before running a controlled test.
Software and version notes
Published configuration path: performance.optimized-powered-rails.
Unlike optimize-minecart, this option concerns powered-rail behavior; combining their descriptions would obscure two distinct compatibility risks.
The archived Leaf global YAML documents the 1.21.1 branch; newer official examples differ. Do not copy an older default or missing block into a current server without verifying that release.
Verify the result
Retest booster segments, short redstone pulses, detector rails and automated rail farms. Compare both mechanics and measured update costs, then revert if power propagation changes.
Keep the A/B test results, server build, config diff and rollback notes together so the result can be reproduced.