Running Biomes O' Plenty on Fabric
What the Fabric version of Biomes O' Plenty needs: Fabric Loader, Fabric API, TerraBlender for Fabric and GlitchCore, plus how to avoid mixing up loaders.
For years Biomes O' Plenty was mainly associated with Forge. That has changed: recent releases are published for Fabric alongside Forge and NeoForge. If your favourite performance or utility mods live on Fabric, you can now keep your whole setup on one loader.
Is there a Fabric version?
Yes, for recent Minecraft versions the project publishes separate Fabric builds. Release listings show matching Fabric, Forge and NeoForge files for the same mod version. Older version lines, such as 1.12.2, were Forge-only, so Fabric is not an option there. Before you build a pack, open the version list on the mod's release page and confirm that a Fabric file exists for your exact Minecraft version.
The Fabric checklist
A working Fabric setup needs every item below, all built for the same Minecraft version:
- Fabric Loader, installed through the Fabric installer.
- Fabric API. The mod's page states plainly that the Fabric version requires it.
- TerraBlender (Fabric). TerraBlender is published as separate projects per loader, so choose the Fabric one.
- GlitchCore, the Glitchfiend library that the mod requires for Minecraft 1.20.4 and newer.
- Biomes O' Plenty, the Fabric file.
The single most common Fabric problem is a Forge or NeoForge jar sitting in a Fabric mods folder. Fabric will either ignore it or stop with an error, and the fix is simply to replace it with the Fabric file.
Installing step by step
1. Install Fabric Loader
Run the Fabric installer, select your Minecraft version and install the client profile. Launch that profile once so it can finish setting up.
2. Add the libraries
Place Fabric API, TerraBlender for Fabric and GlitchCore in your mods folder. The default locations for each operating system are listed in our full installation guide.
3. Add the mod
Add the Fabric build of Biomes O' Plenty to the same folder, then start the Fabric profile. If you reach the title screen, create a new world or explore unvisited chunks to see the new biomes.
Mistakes that cause crashes
- Version drift. Fabric API updates often. A Fabric API file for a different Minecraft version is a frequent cause of a failed launch.
- Two copies of a library. Leftover older TerraBlender or GlitchCore jars can conflict with the new ones. Keep one of each.
- Wrong Java. Modern Minecraft versions need a modern Java runtime. The official launcher bundles the right one; custom launchers sometimes do not.
For the error messages that go with these mistakes, see fixing common Biomes O' Plenty crashes.
Using it with other Fabric mods
Most players pair Biomes O' Plenty with client-side performance mods and map mods. Because Biomes O' Plenty mostly adds world-generation content and blocks, it usually coexists with those. Still, add mods in small batches and launch between batches. When something breaks, you will know which addition caused it. Our performance guide covers settings that help once everything loads.