Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 2 weeks ago
All versions
1.0.0+1.20.1
Release
Sounds 1.0.02 years ago 3,663
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
This is a huge update! Thank you to all my Ko-Fi Supporters for helping me test out and recommend features.
New Additions
- Added support for 1.21!
- Added over 56 new block sounds - bringing Sounds' featureset inline with QualitySounds. These sounds are sourced from Zapsplat, a premium foley library.
- Added an incompatibility screen to tell players that Sounds and QualitySounds do the same thing, and that they will conflict.
- A cleaned up configuration screen, the ko-fi and discord grid widgets have been turned into buttons which lie next to the "Done" button.
- Ko-Fi supporters are given a "Thank You" in the config screen in the form of a little splash text.
- Cleaned up various implementations, hopefully reducing non-reproducible bugs in the future.
- Added new
TagPairclasses which can be used by mods to implement their own custom block sound configurations.
Fixes
- Fixed issue with enderpearls not having unique sounds when the toggle is enabled.
- Fixed compatibility issue with Inventorio, the "Item Drop" sound effect no longer is spammed when opening the inventory when inventorio is enabled.
- Fixed issue where the background of the config screen isn't rendered, which allows you to see the previous screen rendered underneath the config screen.
- Fixed crashes when a configured sound's sound event ID is not valid, you will now recieve a toast warning you that the sound is broken and that you should fix it!
- Fixed various mixin targets to be cleaner and require less modification across versions (specifically Leashes and cakes)
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:ZouiUX7t:zzFKvQk1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZouiUX7t:zzFKvQk1"
}

