All versions
0.11.0-beta+mc1.20.1
Beta
Muddy World 0.11.0-beta+mc1.20.13 months ago 17
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Muddy World 0.11.0-beta for Minecraft 1.20.1
Added
- Added Minecraft 1.20.1 support.
- Added a dedicated Fabric 1.20.1 build of Muddy World.
Changed
- Ported Muddy World to Minecraft 1.20.1.
- Updated Fabric, Yarn, Loom, and Java compatibility for Minecraft 1.20.1.
- Adapted client rendering code for Minecraft 1.20.1.
- Adapted terrain conversion and finalizer logic for Minecraft 1.20.1.
- Preserved the same gameplay behavior as the newer Muddy World versions.
Fixed
- Fixed Viscous Mud fog color in the 1.20.1 port.
- Fixed Viscous Mud overlay and inside-view rendering in the 1.20.1 port.
- Fixed Viscous Mud hand and held item rendering issues in the 1.20.1 port.
- Fixed incorrect inventory item tinting from the 1.20.1 port.
- Fixed muddy blocks not being mined efficiently with a shovel.
- Fixed muddy terrain variants not dropping Mud when mined without Silk Touch.
- Fixed Viscous Mud shovel mining speed while keeping its no-drop behavior.
- Fixed terrain conversion triggering falling block physics during generation/finalizer conversion.
Included Features
- Muddy terrain generation in wet biomes.
- Water-contact mud conversion.
- Wet-biome climate conversion.
- Natural mud drying.
- Lava and Nether drying behavior.
- Viscous Mud and Viscous Mud Bucket.
- Decorative persistent mud from Water Bottle interaction.
- Biome tag and datapack compatibility.
- Optional Rooted Trees compatibility.
Notes
- This is a port of Muddy World 0.11.0-beta to Minecraft 1.20.1.
- Fabric API is required.
- Rooted Trees compatibility is optional.
- If Rooted Trees is not installed, Muddy World works normally.
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:B3roGO40:ZGjSGFdo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B3roGO40:ZGjSGFdo"
}

