Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated 11 months ago
All versions
1.2.0
Release
Sculk Muffler 1.2.011 months ago 7,655
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Added
- Support for muffling global sound events (Wither spawning, etc.) by converting them to non-global events as though the global sound events game rule is disabled.
- The Advanced Sculk Muffler block, which has several new settings including:
- Containment Mode, which allows sounds to play as long as the listener is within the muffler's area of effect, otherwise the sound is silenced.
- Range Offsets, allowing you to reposition the area covered relative to the muffler to make placing one easier.
- Sound Allowlist / Denylists, so you can dial in exactly which sounds you want to be blocked.
Fixed
- Updating the volume of
AbstractTickableSoundInstancesounds will remember the sound's original volume so it can be restored when the muffling state changes without the instance's volume being changed. - Clamp the volume of a sound between 0% and 100% when applying muffling to ensure expected behavior. This should fix jukebox songs.
Changed
- Mufflers that have been renamed with an anvil now remember their custom name and display it where appropriate.
- The volume of
AbstractSoundInstancesounds of the RECORDS category is updated every tick so that muffling changes can apply correctly to jukebox songs. - Improve the line rendering when drawing the working area of a muffler.
- The sonic boom attack of Wardens will now be mitigated when either the Warden or the target are standing within range of a muffler, when previously the Warden needed to be within range of a muffler.
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:WwhlGDEO:pBOUMY5q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WwhlGDEO:pBOUMY5q"
}

