Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published 2 years ago
All versions
3.1.5
Release
CliffTree 3.1.5 - Mounts of Mayhem4 months ago 11.6K
Compatibility
Minecraft: Java Edition
1.21.11
Platforms
Fabric
NeoForge
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
CliffTree 3.1.5 for 1.21.11
Changes & Additions
- Reduced fog density in most cave biomes
- Added Chinese localization (by Lailah Quill)
- The mod version now depends on Lithostitched 1.6
- The datapack version does not require it, but minor improvements will be present if it is installed
Bug Fixes
- Fixed underwater music not playing in ocean biomes
- Fixed magma blocks being way too common in oceans when it reaches deepslate level
- Fixed snow golems not melting in certain warm biomes
Lithostitched-dependant features
Minor improvements are applied when Lithostitched is installed:
- Improved the appearance of custom bandlands-type biomes
- Now uses a custom surface rule instead of feature-based replacement
- Will no longer bleed colors across different types of bandlands biomes
- For example, the colored bands of Shrublands will no longer bleed to nearby Badlands biomes
- Improved the appearance of steep cliffsides
- Is now applied across all directions, instead of just north and east
- The steepness of stony cliffsides now vary across different biome types
- World preset selection is now enabled for both datapack and mod versions
- CliffTree's surface rules are now saved as a separate file, and referenced in the noise settings
- This should simplify and futureproof adding CliffTree compatibility to terrain generation mods
Report CliffTree issues here
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:59ypHk8x:JZIwqnbs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:59ypHk8x:JZIwqnbs"
}

