Direct answer
Leaf exposes a faster random generator option in its historical 1.21.1 leaf-global.yml reference; this is not proof that every newer branch has the same key or default.
How to check it
- Identify the exact Leaf build, inspect its generated configuration and compare world generation or gameplay tests on identical disposable seeds. This feature targets random-generation implementation rather than general network lag.
- 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
The historical config shows performance.faster-random-generator.enabled with a selectable generator such as Xoroshiro128PlusPlus. Never paste a 1.21.1 example into a newer build without verifying the option and runtime support.
Random algorithm changes can alter deterministic behavior. Back up the world and check any mechanics relying on repeatability before enabling it.
Software and version notes
Before using any example, confirm that your exact server build exposes this option and that a per-world override does not take precedence. Leaf examples from publicly available 1.21.1 documents are historical; do not assume the same keys or defaults apply to later builds.
This article is written for Leaf. Configuration keys and defaults can move between versions. The source material checked for this page includes Leaf global configuration. 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.