All versions
0.10.0
Beta
MuddyWaters 0.10.0 - Rerelease2 days ago 22
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Changes
⚠️ Critical fix — worlds no longer break when client and server versions differ
- Previously the mod added hidden data to vanilla blocks, which shifted Minecraft's internal block ID table. If a client and server ran different versions of the mod — or only one side had it installed — chunks were decoded against the wrong table and the world rendered as completely different blocks, with heavy lag.
- The mod now leaves vanilla block data untouched, so it is safe to run with mismatched versions, and safe against a vanilla client or a vanilla server.
- Upgrade note: player-placed protection is reset by this update. Blocks you placed before 0.10.0 are no longer exempt from conversion. Blocks placed from now on are tracked as normal.
- Player-placed/mod-converted tracking now works for any block, including ones added by datapacks or other mods.
Converted blocks now dry out
- Blocks the mod converted revert once they are no longer wet: mud, podzol, mycelium, rooted dirt and packed mud dry to coarse dirt, and coarse dirt dries back to plain dirt.
- Only ever applies to blocks this mod converted — naturally generated mud, podzol, mycelium and coarse dirt are never touched.
- New config: dryOutEnabled (default on), dryOutTicks (default 6000 ticks / 5 min)
Updated shoreline blocks
- Plains → coarse dirt
- Forest (incl. dark, birch, flower) → rooted dirt
- Taiga (incl. old growth) → gravel (was cobblestone)
- Savanna → packed mud (was coarse dirt)
- Snowy and frozen biomes → packed ice (was gravel)
- Lush caves → moss block
- Beach → sand
- Swamp/mangrove (mud), badlands (red sand), desert (sand), jungle (podzol), mushroom fields (mycelium) and windswept (gravel) are unchanged
- Every snowy variant is packed ice, including snowy taiga and snowy beach
Config file
- The shoreline block table in muddywaters.json updates to the new defaults automatically on first launch. If you have edited it yourself — even one entry — your version is kept as-is.
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:GtCbr1US:iFbx4YQQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GtCbr1US:iFbx4YQQ"
}



