Fast Noise: A Mod to Optimize World Generation
The Fast Noise mod introduces a set of performance optimizations aimed at speeding up noise generation and world creation processes in Minecraft.
How It Works
During world generation, the game performs numerous computations. This mod optimizes some of the key stages:
- Implementation of more efficient methods for resizing paletted data containers (palettedContainer).
- Application of improved algorithms for updating block states.
It is important to note that the calculation of the heightmap is not currently optimized. An attempt to accelerate block counting was abandoned due to incompatibility with the Lithium mod and technical hurdles.
Difference from Other Solutions
Fast Noise is not just a clone of existing optimizers like Noisium. While Noisium primarily works with direct access to data containers, Fast Noise implements additional, deeper performance improvements for a more comprehensive approach to accelerating generation.
Compatibility with the Original Game
All changes are made to completely preserve gameplay and behavior identical to the standard version of Minecraft. This ensures that the mod will not break your saves or expected game mechanics.
How Much Faster Does It Get
The focus is primarily on micro-optimizations. Progress is noticeable in execution speed, but it is not a massive acceleration. To objectively assess the difference, benchmarks are conducted. The code snippet below shows comparative tests of biome and noise generation in different worlds (Overworld, Nether, End) using Fast Noise version 1.0.6 and without it.
It is important to remember that performance benchmarks can vary. Differences in hardware can sometimes lead to random fluctuations in world generation speed of up to ±50%. Testing settings also have their limitations, so results may contain minor inaccuracies.
Compatibility with Other Mods
The Fast Noise mod is designed to avoid conflicts. It will function correctly with most other mods, as long as they do not directly modify the game's internal populateNoise function via mixins. In all other cases, no issues are expected.
