Two libraries nobody installs on purpose reached 26.3 on 20 September, and between them they unblock a long list of biome mods that have been stuck on 26.2 since Wilderness Bound shipped.
TerraBlender and GlitchCore are dependencies. If you have been refreshing Biomes O’ Plenty’s page waiting for a 26.3 build, this is the thing that had to happen first.
What these two actually do
TerraBlender is the layer that lets multiple mods add biomes to the same world without overwriting each other. Vanilla’s biome source is not designed for several mods claiming regions of the same noise map, and TerraBlender is the arbitration that makes it work.
Without it, two biome mods installed together produce either a crash or a world where one of them silently does nothing. With it, both get allocated regions and both generate.
GlitchCore is the smaller piece – a shared code library for Glitchfiend’s own mods, which includes Biomes O’ Plenty. Its 26.3.0.0.1 release on the same day re-adds an API for registering strippable blocks, which is the kind of detail that matters to exactly one person until a mod fails to load without it.
Why the whole category was waiting
Dependency chains in the biome space run deep. A biome mod depends on TerraBlender, which depends on the game’s worldgen internals, which change every drop. Nothing downstream can move until the library does.
That is why the biome and worldgen category is consistently the last thing to reach a new version, long after the performance stack has settled. The performance mods hook rendering and ticking, which change less. Worldgen mods hook the part of the game Mojang is actively rewriting.
It is also why a modpack built around terrain is a much bigger version-migration job than one built around gear – the reasoning is in the version migration notes.
Where Biomes O’ Plenty actually stands
Still on 26.2. Its most recent build, 26.2.0.0.28, went out on 7 September, before Wilderness Bound.
So the accurate statement is that BOP is now unblocked rather than updated. The libraries it needs exist for 26.3; the mod itself has not shipped a 26.3 build yet. Anyone planning a world around it should wait for the actual release rather than treating the library update as the green light.
Historically the gap between the libraries landing and Glitchfiend’s own mods following has been short, because the same people maintain both. Our Biomes O’ Plenty review covers what you are waiting for.
The beta tag
Both 26.3 builds are marked beta rather than release. TerraBlender is at 26.3.0.0.0 and GlitchCore at 26.3.0.0.1, with a same-day hotfix on the second.
Version numbers ending in .0.0 on a library that sits underneath worldgen are worth treating carefully. This is the first build against a new version’s internals, it has had one day of exposure, and the failure mode for a worldgen library is a world that generates wrong rather than a crash you notice immediately.
Both are on Fabric, NeoForge, Forge and Quilt, with the Fabric downloads running an order of magnitude ahead of the others on day one.
What this means if you are waiting
- Do not start a 26.3 world you intend to add biome mods to later. Biomes generate at chunk creation, and retrofitting means travelling to fresh terrain.
- Check the actual mod’s version list, not the library’s. A library on 26.3 does not mean the mod is.
- If you run several biome mods, all of them need to be on 26.3 before you move. The slowest one sets the date.
- Stay on 26.2 until then. That is the boring answer and it is the right one for a world you care about.
For anyone who wants terrain changes now rather than in a few weeks, the vanilla-blocks options moved earlier – WWOO rewrote itself for 26.3 two days after the drop, and it has no library dependency chain of this kind.
Short version
TerraBlender and GlitchCore are on 26.3 as of 20 September, in beta. Biomes O’ Plenty is not, yet, but it now can be. If your 26.3 plans were blocked on a biome mod, the block has moved one step further down the chain rather than disappeared.
How to check a dependency chain yourself
This situation repeats after every drop, and the check takes about a minute per mod.
- Open the mod’s Modrinth page and look at the version list filtered to the game version you want. If nothing appears, it is not ported.
- Open its dependency list. Every required dependency needs its own build for that version.
- Check each dependency the same way. Libraries frequently depend on other libraries.
- The slowest item in that tree is your actual release date.
Doing this before you plan an update is the difference between a migration that takes an evening and one that stalls halfway with a server nobody can join.
Which biome mods this affects
TerraBlender is a dependency for a large share of the biome category, not just Glitchfiend’s own work. Anything that adds biomes to the overworld alongside other mods almost certainly sits on top of it, because the alternative is writing your own arbitration and breaking compatibility with everything else.
The mods that are not affected are the ones that rewrite vanilla biomes rather than adding new ones, and the datapack-based options that work through vanilla worldgen data rather than through code. That is why a handful of terrain mods were on 26.3 within days while the biome-adding ones were not – they are solving a different problem with a shorter dependency chain.
Images: Explorify project gallery.