Links
Tags
Creators
Details
1.0
Compatibility
Required content
Changes
The following biomes have been swapped in worldgen:
Temperate
- plains > swamp
- forest > sparse jungle
- birch jungle > jungle
- old growth birch jungle > bamboo jungle
- river, beach > mangrove swamp
- swamp > cherry grove
Note: Dark Forest and Old Growth Spruce Forest swap places in worldgen (O.G. Pine removed)
Hot
- jungle (sparse, bamboo) > twilight swamp
- wooded badlands > fire swamp (twilight)
- badlands > wooded badlands
- eroded badlands > badlands
- mangrove swamp > spooky forest (twilight)
Cold
- taiga > dense mushroom forest (twilight)
- snowy taiga > firefly forest (twilight)
- snowy plains > dark forest (twilight)
- ice spikes > dark forest center (twilight)
- frozen river > river
- frozen beach, stony shores > beach
Mountains
- frozen peaks > stony peaks
- jagged peaks, stony peaks > basalt deltas
Note: Basalt Deltas spawn Nether Fortresses underground to get Blaze Rods / Netherwart. They do not spawn Bastions, however.
Hilly
- meadow > oak savannah (twilight)
- grove > lush caves
- snowy slopes > dripstone caves
- cherry grove > mushroom fields
- windswept gravelly hills > clearing (twilight)
- windswept hills > old growth birch forest
- windswept forest > thornlands (twilight)
Ocean
- Frozen Oceans > Cold Oceans
- Cold Oceans > Lukewarm Oceans
- Oceans > Warm Ocean
- Lukewarm Oceans > Warm Ocean
- Warm Ocean > Oceans, Dripstone Caves
- Mushroom Fields > Twilight Glacier (twilight)
Note: Twilight Glacier is surrounded by thin band of Frozen Ocean, followed by larger band of Deep Dark. Deep Frozen Ocean removed.
Unchanged
- Savanna Biomes
- Flower Forest, Sunflower Plains
Requires the Twilight Forest mod
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:5TfRlB35:Q6sG9uXm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5TfRlB35:Q6sG9uXm"
}


