All versions
0.1.0+26.2
Release
Old Continents 0.1.0+26.22 weeks ago 165
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
[0.1.0] - 2026-07-21
First release. For Minecraft 26.2 with Fabric (requires Fabric API).
Added
- "Continents" world type with a Continentalness slider (0–100) (steps of 5)
behind the Customize button on the world creation screen:
- 0 = modern generation, identical to vanilla.
- 100 = classic 1.6.4-style continents: ragged-coast archipelagos in a dominant ocean (~84% water).
- Anything in between = hybrid worlds.
- Terrain built from 100% vanilla density functions (no custom chunk generator): worlds store a clean reference, stay stable across mod updates, and are safe to open even without the mod installed.
/continents map <continentalness> [radius](OP): renders a 1024×1024 PNG biome map of your seed at any slider value in ~1 second, without generating chunks (radius 1,000–30,000, default 10,000). Files are saved tocontinents-maps/with a clickable link in chat./continents map settings <id> [radius](OP): variant that renders any registerednoise_settings(useful for datapacks and experiments).- Dedicated server support:
level-type=continents\:continentsgenerates at continentalness 100. - Languages: English, Spanish, and Spanish (Argentina).
Balance notes
- The curve at continentalness 100 is calibrated against real 1.6.4 generation: fragmented landmasses (features ~2.9× vanilla scale), rugged coastlines, and an ocean-biased offset.
- Mushroom islands exist but are rare and small (deep-tail compression of the noise: only the most extreme cores cross the mushroom fields threshold).
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:7AFdOQG9:eaKHup0R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7AFdOQG9:eaKHup0R"
}

