Links
Tags
Creators
Details
Licensed CC-BY-NC-4.0
Published 2 months ago
Updated 3 days ago
All versions
2.1.0+26.1-fabric
Release
One Dimension 2.1.0 — Fabric 26.13 days ago 2
Uploaded by
Compatibility
Minecraft: Java Edition
26.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Changes
OneDimension 2.1.0
A compatibility release — the most-reported mod conflicts, fixed.
- Amplified Nether (and other tall-Nether packs) now fit. The dimension floor moved down to y −320, so a Nether up to 256 blocks tall generates in full instead of being cut through the middle by the obsidian floor. Tested with Amplified Nether and Incendium. Existing worlds upgrade automatically the first time they load.
- End gateways work. Stepping into a gateway after the dragon fight now takes you to the outer End islands.
- Xaero's World Map & Minimap: each band maps as its own layer — the End no longer draws over your Overworld map, and standing in the End maps the End, instead of the Overworld showing through the gaps between the islands.
- Distant Horizons: the End's islands no longer hang over the Overworld in the distance, and no longer leave dark island-shaped patches on the ground beneath them. (Distant terrain Distant Horizons has already saved keeps its old lighting until it regenerates.)
- Iris / Oculus shaders now use their Nether and End environments inside those bands, rather than rendering the whole world as Overworld.
- Fixed a crash on world load with Biolith installed — this affects Biolith-based biome mods.
- Fixed unnatural free-floating End stone slabs at chunk borders out in the End's void (newly generated chunks only).
Requires CodxLib 1.3.6 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:kXBpPb2P:co8R7YRp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kXBpPb2P:co8R7YRp"
}


