Tags
Creators
Details
5.1.0+1.21.11-forge
Compatibility
Required content
Changes
OneBlock 5.1.0
This file is for Forge 1.21.11.
Blocks, items and mobs can now belong to a biome. 5.0.0 let a biome bring its own pool; this lets a single entry say which biomes it appears in. Everything else is unchanged, and a config that doesn't use it behaves exactly as before.
- Any drop-table entry may list the biomes it spawns in. While none of them is the active biome the entry contributes nothing, and its share goes to the rest of the list — so give every wood the same weight, tag one per biome, and the combined chance of getting a log stays constant while which log you get follows the biome. Vote taiga, get spruce; vote plains, get oak.
- Entries with no biomes listed still spawn everywhere, and the tags are ignored entirely when biomes are off or nothing would be left to roll — a tag can never make a list unspawnable.
- Set them in
config/oneblock.jsonor visually at codx.io/tools/one-block, which now shows live per-biome chances. The in-game dictionaries show an entry's biomes on its tooltip.
Fixes
/oneblock export(and Export For Website) no longer adds blocks that can't be mined in survival — bedrock, barriers, command blocks and the like were being listed at the same weight as everything else, and a table containing one would eventually put it on someone's OneBlock and strand them. They're skipped on export, and they can never roll even if an older export already put them in your file.- The biome shown above your OneBlock now uses the biome's name instead of its raw id.
CodxLib is required — install the build matching your Minecraft version and loader. On Fabric it must be 1.3.4 or newer.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:necbGNtT:UsoNOGlz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:necbGNtT:UsoNOGlz"
}

