To run Biomes O’ Plenty on a dedicated Minecraft Java server, install the server’s matching Forge, Fabric, or NeoForge loader, place the matching Biomes O’ Plenty JAR and dependencies in mods, use the correct world-generation setting for your Minecraft version, and create a new world. The server and every client must use the same Minecraft version, loader, mod build, and dependency versions.
Godlike.Host offers modded Minecraft server hosting with one-click modpacks, a built-in mod installer and up to three free backups a day.
What Biomes O’ Plenty adds
Biomes O’ Plenty is a client-and-server mod for Minecraft Java Edition. It adds more than 50 unique biomes, along with associated plants, trees, blocks, and other world-generation content. Because those features are generated as terrain is created, installing the mod on a server is not just a matter of copying a file to the host: the server must load the mod during world generation, and players must have a compatible client installation.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The most important decision is the exact combination of Minecraft version and mod loader. A Biomes O’ Plenty file built for Forge cannot be used on a Fabric or NeoForge server, even if the Minecraft version number is identical. The same rule applies to dependencies.
Check the version and loader before downloading anything
Start with the Minecraft version your server will actually run. Then choose one loader family: Forge, Fabric, or NeoForge. Download the Biomes O’ Plenty artifact built for that exact pair. The project’s current files include separate Forge, Fabric, and NeoForge builds; the CurseForge files listing also shows 26.3 files for all three loader families with October 2026 release dates.
#1 Best Overall
Do not use a “close enough” file. A 1.20.1 build, for example, is not automatically compatible with 1.20.4, and a Forge build is not interchangeable with a NeoForge build. The loader, Minecraft version, Biomes O’ Plenty release, and every dependency must line up.
| Choice | What must match | When it is appropriate |
|---|---|---|
| Forge | Minecraft version, Forge server distribution, Forge Biomes O’ Plenty build, and Forge-compatible dependencies | Use when your modpack or existing server is built around Forge. |
| Fabric | Minecraft version, Fabric server distribution, Fabric Biomes O’ Plenty build, Fabric API, and other matching dependencies | Use when the rest of your server’s mods are Fabric-based. |
| NeoForge | Minecraft version, NeoForge server distribution, NeoForge Biomes O’ Plenty build, and NeoForge-compatible dependencies | Use when your chosen Minecraft version and mod collection target NeoForge. |
If you are joining an existing server, ask its administrator for the exact Minecraft version, loader name and version, Biomes O’ Plenty file version, and dependency versions. Installing a different loader or release on your computer will normally result in a mod-list mismatch when you connect.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsInstall the required dependencies
The dependency set changes with the Minecraft version and loader. Check the dependency information for the specific Biomes O’ Plenty file you downloaded rather than copying dependencies from a different release.
| Minecraft range or loader | Required dependency information | Configuration note |
|---|---|---|
| 1.18 and newer | TerraBlender is required. | Use the TerraBlender build for the same Minecraft version and loader family. |
| 1.20.4 and newer | GlitchCore is required in addition to the applicable dependencies. | Use a GlitchCore release that explicitly supports the server’s Minecraft version and loader. |
| Fabric installations | Fabric API is required. | Fabric API must match the Minecraft version used by the server. |
Some versions can require more than one item in the table. For example, a recent Fabric server may need TerraBlender, GlitchCore, and Fabric API. A missing or incompatible dependency is one of the most common reasons a modded server stops during startup.
Prepare a clean server directory
Use a separate directory for the modded server, or make a complete backup before changing an existing installation. A backup should include the world directory, server.properties, the mods directory, and any loader configuration files. Never test a new world-generation mod by overwriting the only copy of a long-running survival world.
You also need a Java installation supported by the Minecraft version and loader you selected. The exact Java requirement is determined by that Minecraft release and loader; follow the loader installer’s requirement instead of assuming that the Java runtime used for another server is suitable.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallInstall the matching server loader
- Download the server distribution. Obtain the Forge, Fabric, or NeoForge server installer for the exact Minecraft version you selected.
- Run the installer in the server directory. Select the server installation option when the installer offers multiple choices. Fabric’s installer uses its server-launch configuration; Forge and NeoForge create their own loader files and launch entries.
- Accept the EULA. Start the loader once. The first launch normally creates the server structure and stops until you accept Minecraft’s EULA. Open the generated
eula.txt, change the EULA line to the required acceptance value, save it, and start the loader again. - Confirm the directory layout. A successful first launch should leave a
modsdirectory or create one when the loader starts. It should also createserver.propertiesand the loader’s launch scripts or JAR files. - Stop cleanly. Use the server console’s
stopcommand before copying mods or editing configuration. Do not modify a world while the server process is still writing to it.
Always start the loader’s generated server script or loader JAR after installation. Starting a vanilla server JAR instead bypasses Forge, Fabric, or NeoForge, so Biomes O’ Plenty will not load.
Add Biomes O’ Plenty and its dependencies
- Download the Biomes O’ Plenty JAR built for your exact Minecraft version and loader family.
- Download TerraBlender for Minecraft 1.18 and newer.
- Add GlitchCore for Minecraft 1.20.4 and newer.
- If the server uses Fabric, add Fabric API as well.
- Copy every JAR into the server’s
modsdirectory. Do not place them in the client’s mods folder only, and do not leave duplicate releases of the same dependency in the directory. - Check each filename and release page before starting the server. A dependency for a different Minecraft version or loader can be just as incompatible as omitting the dependency entirely.
Keep the downloaded files together in a temporary folder until you have confirmed the server starts. This makes it easier to identify which file was added if a startup error appears.
Configure world generation for your Minecraft version
The required level-type value depends on the age of the Minecraft version. The project description explicitly states: “To use the mod on a server for 1.18 and above, no changes to server.properties are required.” Leave the normal level type in place for those versions.
| Minecraft version | server.properties action |
Exact value |
|---|---|---|
| 1.18 and newer | Do not change level-type for Biomes O’ Plenty. |
No Biomes O’ Plenty-specific value is required. |
| 1.15 through 1.17 | Edit server.properties and set the world type. |
level-type=biomesoplenty |
| 1.12.2 and older | Edit server.properties and use the legacy world-type name. |
level-type=BIOMESOP |
To edit the file, stop the server, open server.properties in a plain-text editor, change only the applicable setting, save it, and restart the loader server. Do not put spaces around the equals sign. If the file already contains another custom level type, replace it only when your Biomes O’ Plenty version falls in one of the legacy ranges above.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
Create a new world after installing the mod
Generate the world only after the loader, Biomes O’ Plenty, dependencies, and version-specific configuration are in place. Existing chunks do not get retroactively converted into Biomes O’ Plenty terrain. Players may continue to see ordinary terrain in chunks that were generated before the mod was enabled, even when the installation itself is correct.
- Stop the server and back up the current world if one exists.
- For a new installation, remove or rename the unused world directory rather than deleting a valuable world without a backup.
- Set the desired
level-nameinserver.properties, if needed. - Start the loader server and allow it to create the world.
- Join after startup completes and travel beyond the spawn area to inspect newly generated terrain.
For legacy installations, the official instructions describe either creating a new world or using NBT editing in certain cases. NBT editing is not a substitute for a backup: changing world metadata incorrectly can make a save unusable.
Match every client to the server
Biomes O’ Plenty is not a client-only enhancement. Every player connecting to the dedicated server should install the same Minecraft version, the same loader family and version, the same Biomes O’ Plenty build, and the same required dependencies. A player who installs the mod locally cannot make an unmodded vanilla server generate the mod’s biomes.
- Distribute a precise mod list to players rather than telling them to download “the latest” file.
- Keep Forge, Fabric, or NeoForge consistent between server and clients.
- For Fabric, include the matching Fabric API on clients as well as on the server.
- When updating, change the server and client files as a coordinated set.
If only one player receives a connection error, compare that player’s mod directory with a known-good client. If everyone is rejected, inspect the server’s loader and mod versions first.
Verify that the installation is working
A successful startup is necessary but not sufficient: the mod must also participate in world generation. Use this verification sequence:
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
- Read the server console during startup. It should load the selected mod loader without a missing-dependency or wrong-version error.
- Confirm that the Biomes O’ Plenty JAR and dependencies remain in
modsafter the first launch. - Join with a matching client and check that the connection is accepted without a mod-list mismatch.
- Explore newly generated chunks rather than relying on an area created before installation.
- Look for the mod’s distinctive plants, trees, blocks, or biome layouts. Seeing only familiar vanilla terrain in an old region does not prove the installation failed.
For a controlled test, create a temporary world with a distinct level-name. This avoids confusing an old save’s pre-generated chunks with the output of the new installation.
Hosted-server deployment
The same compatibility rules apply on a managed host. The host must run the correct Forge, Fabric, or NeoForge distribution, and the mod and dependencies must be installed on the server rather than only on a player’s computer.
Exaroton’s documented workflow is to switch the server software to Forge, install Biomes O’ Plenty, add TerraBlender for 1.18 and newer, and choose biomesoplenty in its world-type field for Minecraft 1.13.2 and newer. The host’s control-panel label can differ from the raw server.properties setting, so use its documented field for the version you selected. Stop the server before changing the software, uploading JARs, or replacing a world.
Troubleshoot the common failure modes
The server crashes during startup
- Verify that the Minecraft version in the server directory matches the Biomes O’ Plenty JAR.
- Verify that the loader is the same family named by the mod file: Forge, Fabric, or NeoForge.
- Check for TerraBlender on 1.18 and newer.
- Check for GlitchCore on 1.20.4 and newer.
- Check for Fabric API on Fabric servers.
- Remove duplicate or older copies of Biomes O’ Plenty and its dependencies.
Read the first “caused by” or missing-mod line in the server log rather than trying random files. A dependency error near the beginning of the crash report usually identifies the incompatible or absent component.
The server starts, but no new biomes appear
- Confirm that the world was created after Biomes O’ Plenty was installed.
- Travel into chunks that had never been generated before the installation.
- For Minecraft 1.15 through 1.17, check that
level-type=biomesoplentyis present. - For Minecraft 1.12.2 and older, check that the value is exactly
level-type=BIOMESOP. - For 1.18 and newer, remove an unnecessary legacy level-type value and let the project’s modern world-generation behavior apply.
Do not expect already explored terrain to change. Testing in a fresh world is the fastest way to separate a generation problem from an old-chunk problem.
Players cannot join
- Compare the client and server Minecraft versions.
- Compare the loader family and loader versions.
- Compare the Biomes O’ Plenty build.
- Compare TerraBlender, GlitchCore, and Fabric API versions where applicable.
- Remove client-only additions that alter the required mod list if the server does not support them.
A client can display a different error for the same underlying mismatch, so use the server console and the client’s connection message together.
The wrong server process is being launched
If the console looks like a vanilla server and never lists the mod loader, inspect the hosting panel, startup script, or command line. Replace the vanilla entry point with the Forge, Fabric, or NeoForge launch script created during loader installation. Stop the process before changing the startup command.
Updating or changing the setup safely
Treat a loader change, Minecraft-version change, or major Biomes O’ Plenty change as a migration rather than a routine file replacement. Make a full backup first, document the old versions, and test the new combination in a copied world or temporary world before allowing players to return.
- Keep the same loader family unless you are intentionally rebuilding the server; Forge, Fabric, and NeoForge files are not interchangeable.
- Update dependencies at the same time as the mod when the new release requires them.
- Do not open a world in a newer setup and then assume it can safely return to the older setup.
- Expect newly generated chunks to reflect the active installation, while old chunks retain their existing terrain.
For a long-running server, schedule the change when no one is online, preserve the original backup separately, and record the exact file versions that worked.
Quick Recap
Quick installation checklist
- Java Edition server selected.
- Exact Minecraft version selected.
- One loader family selected: Forge, Fabric, or NeoForge.
- Matching server loader installed and launched once.
- Biomes O’ Plenty JAR copied to
mods. - TerraBlender added for 1.18 and newer.
- GlitchCore added for 1.20.4 and newer.
- Fabric API added when using Fabric.
- Legacy
level-typeset only where required:biomesoplentyfor 1.15–1.17 orBIOMESOPfor 1.12.2 and older. - New world created after installation.
- Every client matched to the server’s version, loader, mod, and dependencies.
- Backup retained before any world or version change.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
