Tags
Creators
Details
All versions
1.0.0+mc26.3.jar
Release
Toroidal World 1.0.0last week 78
Compatibility
Minecraft: Java Edition
26.3
Platforms
Fabric
NeoForge
Supported environments
Client and server
Changes
Updated to NeoForge 26.3.0.64-beta and Fabric API 0.162.0+26.3.
Added
- A Toroidal world can be skewed: crossing the world's edge along Z also moves you along X, so getting back where you started can take several laps.
- The lines marking the world's edge on the fullscreen JourneyMap and Xaero's World Map can be turned off in the mod's settings.
Changed
- The dedicated-server presets are now
exotic_worlds:torus_<size>for a toroidal world andexotic_worlds:cylinder_<size>for a cylinder.
Compatibility
- BetterNether biomes and surfaces carry on across the world's edge in a Toroidal Nether, and its biomes shrink with Compact biomes.
- BetterEnd islands from the Custom End Terrain Generator, its surfaces, tunnels and the colours of placed blocks carry on across the world's edge in a Toroidal End.
- Distant Horizons 3.3.4 draws the distant terrain across the world's edge.
- Distant terrain from another mod's Distant Horizons world generator carries the world's ground cover and snow across the world's edge.
Fixed
- With C2ME installed, a new world no longer hangs at "Preparing spawn area", and chunks of an existing world generate again.
- With Distant Horizons, every beacon shows a single beam in the distant terrain.
- With TerraBlender, the Region line on the debug screen (F3) names the region you are standing in, also after crossing the world's edge.
- With a world border smaller than the world, a nether portal leads to the portal already standing inside the border.
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:CdjG7l5z:d9YtZSDX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CdjG7l5z:d9YtZSDX"
}

