Download File

This release improves cleanup quality on both vanilla and biome-overhaul-modded worlds, fixes two long-standing edge cases that mainly affected modded worldgen, and adds an in-game command to make bug reports easier. ### Fixed - **Trimming oversized biome regions sometimes left tiny stranded islands behind.** When a biome region is larger than its configured `max` size, the cleaner trims it down by folding the excess quarts into neighbouring biomes. Occasionally a handful of those quarts were left stranded as a small island adjacent to the trimmed region rather than merging cleanly in — usually because no adjacent neighbour had room to grow without itself going over its own `max`, or because the neighbour the planner picked wasn't a clean fit and ended up stranded itself. The planner now reserves room in absorbing neighbours up front, folds unviable leftovers back into the original region when there's headroom, and breaks ties toward neighbours that stay neatly sized. **Vanilla and modded worlds both benefit** — vanilla seeds see noticeably fewer stray-island patches, and the effect is even larger on biome-overhaul worldgen mods where many regions exceed their `max` and need trimming. - **Inland beaches and shores were sometimes preserved when they barely touched a river or ocean.** The "must touch ocean or river to count as coastal" rule (`requiredBoundaryGroups` in the config) accepted *any* contact as enough — even a single quart of river adjacency was sufficient. With biome-overhauling worldgen mods that introduce extra biomes near coastlines, this could keep large beaches as "coastal" despite being almost entirely inland (e.g. a beach with one quart of river touch and 80+ quarts of forest neighbours). The rule now requires meaningful contact: at least 4 qualifying boundary contacts, *or* at least 10% of the region's total boundary in the rule's biome list. Either condition passes, so genuinely small coastal regions still work — but token contact no longer rescues a stranded inland beach. Vanilla worlds without worldgen mods are unaffected; their coastlines comfortably exceed both thresholds. - **Oversized shores on heavily-modded worldgen were silently skipped instead of being trimmed.** When you configure a biome with a `[min, max]` range (e.g. `"minecraft:stony_shore": [32, 64]`), regions larger than `max` should be trimmed down. The cleaner had an internal exploration ceiling of 4096 quarts, sized for vanilla worldgen where shores are intrinsically small. Biome-overhaul mods (clifftree's granite shores, extended stony coastlines, and similar) routinely produce shore regions in the 10000–20000-quart range; those blew past the ceiling, the planner aborted with "budget exceeded", and the region was left exactly as the world generated it. To make matters more confusing, `/biomecleaner inspect` had said the region "would be trimmed" because inspect uses a much larger 65536-quart scan and didn't know the cleanup pipeline would give up earlier. The cleanup ceiling now matches inspect's at 65536 quarts by default, which covers every modded shore we've measured. Vanilla output is byte-identical to 1.1.3 because no vanilla region ever approached the old ceiling either. If a modded biome can produce regions even larger than 65536 quarts, the new top-level `oversizedPlannerBudgetCap` field in `advanced.json` lets you raise it further; `/biomecleaner inspect` now correctly reports `OVERSIZED but EXCEEDS PLANNER BUDGET` with the exact threshold when a region won't fit, instead of falsely promising a trim. ### Added - **`/biomecleaner inspect` command for bug reports.** Stand inside a region you think the cleaner handled wrong and run the command — the mod prints a structured report to chat and `latest.log` covering the world seed, Minecraft version, mod loader and mod count (the full sorted mod list goes only to the log), your position, the biome the algorithm sees versus the biome stored in your chunk palette, the configured size threshold and required-boundary rule, the result of a fresh region scan (region size, classification, qualifying-vs-total boundary contacts with the floor/ratio pass-fail breakdown, top boundary biomes), and a plain-language verdict. The log block is tagged `[BIOMECLEANER-INSPECT]` for easy copy-paste into bug reports. The scan walks up to a 1024×1024-block region so the reported size is the true region size, not the cleanup pipeline's short-circuited proof-of-stable size.