All versions
1.0.1
Release
Custom Dimensions 1.0.1last week 72
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
v1.0.1 Changelog 🛠️
- Fixed portal height collapse 🌌: Target portals no longer flatten to 1 block tall. Each interior position now preserves its relative Y offset (
targetY + (p.getY() - sourceMinY)) instead of all sharing the same Y level. - Fixed portals spawning at bedrock 🪨:
findSafeYOffsetnow scans from world top to bottom at target coordinates, placing portals on the surface. Void dimensions now fall back to Y=64 instead of Y=-64. - Fixed void dimension terrain 🗺️: 26.x now uses
FlatLevelSourcewithFlatLevelGeneratorSettings(empty layers +THE_VOIDbiome) instead of a nonexistent API. - Fixed 26.2.x
NetherPortalBlockMixincrash 💥: Removed injection into atickmethod that doesn't exist in 26.x. - Fixed 26.2.x duplicate code 📋: Removed duplicate lines in
DimensionManager.createLevelStem. - Fixed 26.x compilation error 💻: Resolved the
Registry.getHolder→HolderGetter.getOrThrowcompilation break on 26.x.
⚠️ What Wasn't Fixed & Upcoming Work
- Portal Linking & Two-Way Travel 🔄: True two-way portal linking is currently not working perfectly in this release.
- What we are working on next ⚙️: We are actively rewriting the destination caching logic to ensure that when you step through a custom portal, you can reliably walk right back through the exact same portal to return to your original location. Expect this fix in the next update!
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:1qLvD9tE:Ev6IIprG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1qLvD9tE:Ev6IIprG"
}

