Direct answer
Older Leaf configuration references include an experimental minecart-ticking optimization. It is not the same as optimized powered rails, and the documented key may be absent from a newer 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
- Identify whether transport systems use player minecarts, hopper minecarts, chest minecarts, or automated item lines.
- Measure the lag near running carts rather than assuming a rail-heavy build is slow.
- Check your installed config for optimize-minecart before treating an older YAML example as applicable.
What to change
- In the Leaf 1.21.1 reference, performance.optimize-minecart.enabled is paired with skip-tick-count. Do not paste that block into a version that does not generate it.
- If supported, test on a world copy with minecart clocks, curves, unloading chunks and item transfers. A higher skip count may reduce precision rather than simply improve performance.
- Copy the current configuration and note the previous value before running a controlled test.
Software and version notes
Published configuration path: performance.optimize-minecart.enabled (historical).
The Leaf 1.21.1 reference lists the optimize-minecart block, while a more recent published global sample may omit it. Presence and semantics must be checked against your running version.
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
Time a cart route, verify hopper-minecart inventory transfers, station stops and player ride behavior; compare with the original configuration and revert when mechanical behavior changes.
Keep the A/B test results, server build, config diff and rollback notes together so the result can be reproduced.