Biome Cleaner

Cleans up the messy, scattered biome patches that Minecraft's terrain generation creates. Small biome regions are merged into their larger neighbors, giving your world cleaner boundaries and a more natural feel -- without changing terrain shape, structures, or gameplay.

The mod works server-side only (no client installation needed) and runs entirely on its own background threads, so your server's tick rate is unaffected.

Before & After

With the default settings, those tiny 1-chunk patches of plains in the middle of a forest, or awkward slivers of beach where they don't belong, get absorbed into the surrounding biome. The result is smoother, more coherent biome regions while keeping the overall world layout intact.

Features

• Configurable threshold -- Set how small a biome region must be before it gets merged (default: 512 quarts)
• Biome protection -- Mark specific biomes (like rare ones) to never be replaced
• Replacement control -- Prevent certain biomes (like oceans) from spreading into other areas
• Biome groups -- Define groups for bulk configuration (e.g., all ocean variants)
• Per-group thresholds -- Use different size thresholds for different biome types
• Background preprocessing -- Chunks are cleaned ahead of the player, so there's no lag when new terrain loads
• Server-side only -- No client installation required

Adding to an Existing World

The mod works best on new worlds, but you can add it to an existing world with one caveat: biome seams can appear at the border of your already-explored area.

This happens because the mod only affects chunks as they're generated for the first time. If a small biome patch straddles the boundary between chunks you've already explored and chunks you haven't, the old side keeps its original biomes while the new side gets cleaned up -- creating a visible mismatch where the two halves meet.

These seams only occur right at the edge of your previously explored territory and only where a small biome patch happens to cross that boundary. The rest of your new terrain will be fully cleaned as expected. Once you move past the border area, everything is seamless.

Starting a new world? No issues at all -- every chunk is cleaned as it generates.

Configuration

Main Config

Located at config/biomecleaner/common.json:

What is a quart? Minecraft stores biomes at 1/4 block resolution (one biome value per 4x4x4 block cube). A "quart" is one of these 4x4 biome cells. The default threshold of 512 quarts corresponds to roughly a 90x90 block area -- small patches below this size get cleaned up.

Advanced Config

Located at config/biomecleaner/advanced.json:

{
  "groups": {
    "rare": ["minecraft:mushroom_fields", "minecraft:stony_peaks"],
    "oceans": [
      "minecraft:ocean", "minecraft:warm_ocean", "minecraft:lukewarm_ocean",
      "minecraft:cold_ocean", "minecraft:frozen_ocean", "minecraft:deep_ocean",
      "minecraft:deep_lukewarm_ocean", "minecraft:deep_cold_ocean", "minecraft:deep_frozen_ocean"
    ],
    "rivers": ["minecraft:river", "minecraft:frozen_river"],
    "beaches": ["minecraft:beach", "minecraft:snowy_beach", "minecraft:stony_shore"]
  },
  "sizeThresholdOverrides": {
    "beaches": 32,
    "rivers": 48
  }
}

Recommended JVM Arguments

The mod's worker threads are designed to run at a lower priority than the main server thread, so they automatically yield CPU time when the server needs it. By default, Java ignores thread priority settings. Adding these two JVM flags to your server startup script enables them:

-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=1

This is optional but recommended -- it ensures the mod's background work never competes with tick processing, even under heavy load.

Performance

TL;DR: You won't notice it. The mod adds about 2.4% CPU overhead at the default settings and runs entirely on its own background threads -- your server tick rate stays the same.

These numbers are from the default sizeThreshold = 512. Lower thresholds cost less, higher thresholds cost a bit more -- but all stay under 3% CPU.

The mod predicts where the player is heading and pre-cleans chunks in the background well before they're needed. In benchmarks, 79% of chunks were ready more than 5 seconds before the player arrived.

Threshold Comparison

Higher thresholds clean more aggressively (merging larger patches) at a small additional cost:

All thresholds run on dedicated background threads with no impact on vanilla server performance.