Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last month
All versions
2.0-beta1
Beta
v2.0 Beta 1 ~ 1.19.x3 years ago 1,555
Compatibility
Minecraft: Java Edition
1.19.x
Platforms
Fabric
Forge
Quilt
Supported environments
Server-side
Singleplayer
Changes
This is a BETA! I cannot guarantee that updating worlds to the beta or out of the beta is 100% safe. Make backups!
Terralith support and the Large Biomes datapack currently do not exist for this beta.
- Massively altered the way the biome layout works. While the explanation of what changed is technical, the bottom line is that other biome mods should have next to no issues with Tectonic! The issues with biomes being in the completely wrong terrain has been abolished, so mountain peak biome on flat terrain or river biomes plastered on top of mountain ranges when using Terrablender are gone.
- Revised the terrain shaping to be less flat. While the large expanses of flat terrain still exist, there should be more interesting terrain breaking that up. You'll now find new terrain shapes like multi-tiered plateaus, and windswept terrain (with more terrain shapes coming in future versions). Don't worry though; special terrain features from prior versions like underground rivers and desert dunes have carried over.
- Refreshed cave generation. Caves are rarer yet overall bigger. There's also now a deep variant of underground rivers with lava instead of water!
- Removed all Tectonic biomes and improvements to vanilla biomes. This is for multiple reasons, but it comes down to this: It makes the mod more compatible with mods that add biomes and change existing ones, and some of these removed biome improvements from Tectonic have been and/or will be carried over into my other mods like Not Just Biomes. Tectonic biomes remain in the files to keep old worlds from corrupting.
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:lWDHr9jE:gY8cl3L6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lWDHr9jE:gY8cl3L6"
}

