nineMinecraft is a joke site.
nineMinecraft is in no way affiliated with Modrinth or 9minecraft. (And frankly, who wants to be affiliated with the latter?)

Biome Cleaner 1.1.8 for Fabric 26.1

Changelog

Two targeted fixes for modpacks that combine fast-worldgen performance mods with biome-overhaul packs. Default-config worlds without those mods are unchanged — same biomes, same seeds.

Fixed

  • Cleanup silently didn't run on modpacks using fast biome-generation mods. Reported on a 222-mod Fabric modpack running Wilder Wild, Bloom, and zfastnoise: Wilder Wild's dying_forest was generating as tiny single-quart islands and the cleaner was leaving them in place. On modpacks that include zfastnoise (or other performance mods that swap Minecraft's biome-creation step for a faster version), the cleaner was being skipped entirely — installed and loaded, but never actually cleaning anything. The symptom was that small biome patches stayed exactly where they were after world generation; running /biomecleaner inspect on one of them reported "Chunk seen by cleaner: NO" even on a freshly-generated chunk. The mod now hooks one step higher up in the chunk-generation pipeline, at the point all the fast-noise mods, C2ME's parallel worldgen, and vanilla all converge — so cleanup runs regardless of which mod is doing the biome-fill. If you were using config/zfastnoise.mixin.toml's [mixin.perf] biome = false line as a workaround, you can flip it back to true. No effect on default-config worlds or on modpacks without those perf mods — same biomes, same seeds.

  • Tiny inland biome strips could persist when running parallel worldgen mods like C2ME. Reported on the same modpack: a 4-quart strip of minecraft:beach was visible inland inside a bloom:golden_forest region, exactly the "stranded coastal patch" the size-range rules are meant to prevent. Root cause was a precision difference between two ways Minecraft samples biome data — the cleaner's view and the actual chunk palette occasionally disagree at a handful of boundary quarts when C2ME's density-function compiler is in use. The cleaner already protects against most consequences of this disagreement, but in one specific case the disagreeing quarts could end up in the "keep" portion of an oversized-region trim while the surrounding "real" quarts ended up in the trimmed-away portion — leaving a tiny visible island of the disagreement biome. The cleaner now catches this case in both the runtime path and the warming-ahead path, and replaces the affected quarts with whatever the surrounding noise field actually wanted there. Default-config worlds without C2ME (or any other density-function-compiler mod) are unchanged — the underlying disagreement only occurs under those specific mod combinations. Same biomes, same seeds, no config changes required.

Dependencies

Files

biomecleaner-mc26.1-1.1.8-fabric.jar(388.86 KiB) Primary Download

External resources


Project members

alexthundercook

Member

Pockett

Member


Technical information

License
MIT
Client side
unsupported
Server side
required
Project ID