Tags
Creators
Details
Licensed GPL-2.0-only
Published 9 months ago
Updated 6 months ago
All versions
1.19+mc26.1.x
Release
Cave Overhaul 1.19+mc26.1.x6 months ago 77
Compatibility
Minecraft: Java Edition
26.1.1–26.1.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
warning: new chunks WILL have different cave gen and it WILL make your world look kinda weird
Commit 3c84e69
- Fixed an issue where noise caves could end abruptly in tall vertical walls instead of tapering off naturally.
- Slightly more noise caves generate in areas that previously had none.
Commit 7eb304c
- Fixed an issue where caves from the old-world carver could terminate in flat stone walls aligned to chunk boundaries.
- Cave shape and density in old-world carver regions will shift slightly as a side effect — tunnels now cluster a bit more tightly within their home area.
Commit 6d50344
- Fixed an issue where all cave layers shared a single structural noise pattern, causing layers (especially the duplicated ones below y=-64) to look the same as each other.
- Each cave layer now generates with its own independent structural shape for more variety between depths.
Commit 385c50a
- Unified how caves and underground rivers apply their large-scale terrain warping, so they pull from a single consistent pattern instead of independent ones.
- As a result, noise caves WILL generate differently from previous versions, especially at greater depths. Existing worlds will show a visible seam between old and newly-generated chunks.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| caveoverhaul-1.19+mc26.1.x-sources.jar | Sources jar | 107.37 KiB |
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:cek6kGVS:aMKQ3xnw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cek6kGVS:aMKQ3xnw"
}

