2.0.1
Compatibility
Changes
Tectonic Layers 2.1.0 Beta - Native Stack Update
This is the biggest Tectonic Layers update so far.
The Nether and the End are no longer just “copied” into the Overworld. They now generate as native stacked layers, keeping their real terrain shape, biomes, decorations, structures, mobs, fog, portals, and End fight behavior inside one connected vertical world.
Highlights
- Native Nether and End terrain generation inside the stacked Overworld.
- Configurable stack order: swap Nether and End positions while keeping the Overworld as the playable anchor.
- Optional layer removal: create worlds without the Nether layer or without the End layer.
- Better support for modded Nether/End content, including BetterNether structures and decorations.
- Vanilla and modded structures now generate in their correct stacked layer.
/locatenow points to the stacked version of structures instead of empty native coordinates.- End dragon fight, End crystals, obsidian pillars, End city content, and shulkers work inside the stacked End layer.
- Improved Nether/End mob spawning in their real layers.
- Better portal routing between stacked layers, with safer arrival positions.
- New pre-world stack configuration screen.
- Overworld height override from the UI.
- Boundary mode options for layer transitions: Auto, Islands / void, and Caves / blend.
- Faster chunk generation and loading through cached native generation contexts.
- Fixed several crashes around dragon pathing and chunk loading.
- Fixed many cases of Nether/End content bleeding into the Overworld.
Compatibility
Required:
- Minecraft 1.21.1
- NeoForge
- Tectonic
- Lithostitched
Optional but supported:
- Amplified Nether
- BetterNether / BCLib
- Other Nether or End worldgen mods may work, but are still experimental.
Amplified Nether is no longer required. If it is installed, Tectonic Layers will respect its Nether height and generate the stacked Nether accordingly.
Important beta note
This update changes world generation heavily. For the best experience, create a new world.
Existing worlds may contain old chunks from previous beta layouts, especially around Nether/End layers, structures, and portals. Back up your worlds before updating.
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:y1WLFJBb:dOcBdcBW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y1WLFJBb:dOcBdcBW"
}

