All versions
1.3.2
Release
Dynamic Surroundings Rebirth 1.3.23 days ago 204
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client-side
Client and server
Changes
What's new
Dynamic Surroundings Rebirth 1.3.2
Highlights
- Better Clouds compatibility: rain and thunder fog no longer flicker while you move.
- Biome mods are properly supported now — a biome from a mod that ships no Dynamic Surroundings data used to get no ambience at all, and now works out its traits from the biome's name and its climate.
- New sounds for tridents, maces and spears: their own swing and hotbar sounds. Tridents previously fell back to a generic one.
- 1.21.1 gained 16 missing footstep sounds: bamboo, copper, honey, slime, tuff, sculk, moss, bone and froglight blocks were silent underfoot.
- A waterfall pouring into water is heard again — it produced no sound and no splash at all.
- Muffling no longer lags behind and then jumps when you move quickly.
- Modpack authors can now retune landing, stopping and take-off sounds in the data files, instead of needing a code change.
Bug Fixes
- Fixed flame jet and bubble column particles dying at half their intended age, and waterfall and steam particles being ticked and drawn twice.
- Fixed one effect failing and silencing every effect registered after it, for that tick.
- Fixed standing still while water rises over your eyes never switching you underwater.
- Fixed the mod playing into an audio engine that had gone away, which could leave the sound system broken after an output-device change.
- Fixed the End's outer islands never receiving End ambience, and the temperate climate tag being empty on 1.20.1.
- Fixed the version check being able to hang if the update server does not answer.
Other
- Biome music is off by default, and is now available on 1.20.1.
- Polish completed (264 missing keys) and Chinese completed (the last 8).
- A crit-word debug trace for reporting oddities, off unless explicitly enabled.
- New bilingual Customisation Guide (
docs/CUSTOMISATION-GUIDE.md), replacing the older integration guide.
Optional dependencies
Unavailable version
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:N4oljjup:az3sJQIv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:N4oljjup:az3sJQIv"
}

