Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 2 years ago
All versions
0.3.1
Release
Dynamic Surroundings: Fabric Edition 1.20.1-0.3.12 years ago 4,260
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client-side
Changes
Requirements
- JAVA 17+ (I am using Adoptium https://adoptium.net/)
- Fabric Loader >=0.14.22
- Fabric API >=0.91.0+1.20.1
- 100% client side; no server side deployment needed
What's New
- Added a button to Minecraft's Sound Configuration Options screen for accessing the Individual Sound Configuration menu of the mod. It can be found in the lower left corner of the screen.
- Added option to enable playing of other situational music (as in biome background music) rather than creative music when the player is in creative mode. It is off by default and needs to be enabled. Makes testing resource/mod packs easier.
- Added a client side command /dsmm to force a reset of Minecraft's music manager. This will clear any music being played and set the timers so that a new selection will be made within a few seconds.
- Added option to disable client side command registration. Useful when trying to run under Quilt, or if a pack developer just wants to disable as a default.
Changes
- Reworked the display of the individual sound configuration UI. The goal is to slim things down so the information fits on smaller displays. WIP - the icons suck.
- Preload tag cache when connecting to a world. Before, the mod would load entries into the cache in a lazy fashion, and as a result, the player would experience a lag-stutters when faulted in.
- Delay processing resource packs/external configurations until later in the startup process.
Fixes
- Startup crash when ModernUI is installed with its "ding at startup" enabled.
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:H7fshfpD:d3ft8eE3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H7fshfpD:d3ft8eE3"
}

