Tags
Creators
Details
1.0.1
Compatibility
Changes
Changelog
[1.0.1] - 2026-03-12
Bug Fixes
-
Fixed an issue where the attenuation mode was not functioning properly. Addressed a problem where a
ConcurrentModificationExceptionwas being silently caught internally due to non-thread-safe access to theClientLevelplayer list from the background audio thread, causing the gain to remain stuck at 1.0 (maximum volume). Changed the logic to cache player coordinates per frame from the main thread, allowing the audio thread to safely reference this cache. -
Improved the update timing of the attenuation gain (Fixed an issue where audio would briefly play at full volume when stepping out of the orange boundary). Previously, the audio thread updated the gain approximately every 260ms, which caused the audio to be heard at full volume for a split second immediately after stepping out of bounds. Changed the gain update to occur on the render thread (approx. 60fps), significantly improving the response time.
-
Fixed an issue where the attenuation mode did not work for audio played by other players. Thanks to the aforementioned improvement in gain update timing, attenuation is now correctly applied even when playing audio media recorded by players other than yourself.
-
Fixed a bug where audio would not play via redstone input. Resolved an issue where the packet sending process for
startPlayback()was omitted during the multiplayer compatibility refactoring. Restored the logic to send a playback packet to all clients on the rising edge of a redstone signal. -
Fixed an issue where audio data on recording media would become corrupted. Fixed a problem where the creative mode item slot synchronization packet would overwrite the actual server-side data with client-side temporary data (placeholders). Added validation to skip playback if invalid data is detected.
-
Fixed an issue where audio on other clients would not stop when the block was destroyed. Updated the logic to send a
ClientStopAudioPayloadto all players when the playback device is destroyed.
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:4rsUhTWv:qMgdHBFJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4rsUhTWv:qMgdHBFJ"
}

