Links
Tags
Creators
Details
0.3.0+mc26.2
Compatibility
Changes
0.3.0
For Minecraft 26.2. This release promotes the 0.3 beta line, including stations, playlists, portable boomboxes, in-game track search, and speaker controls. Minecraft 1.21.1 remains on 0.3.0-beta.4; other targets retain their existing releases.
Fixes and performance
- Fix native memory growth during extended playback on Minecraft 26.2.
- Hovering a stopped boombox no longer crashes the client.
- Private speakers save their current playback position when their chunk unloads.
- Selecting a track beyond the first 2,000 library entries plays the selected track.
- Concurrent audio transfers share bandwidth, so one track no longer waits for another track's entire download.
- Capacity rejections retry with bounded backoff; failed transfers leave buffering and show the playback error state.
- Station edits coalesce disk saves, and playback changes synchronize only the station view that changed.
Clients and servers must both update because the audio transfer protocol changed.
Validation
- Tested on November 4, 2026: Minecraft 26.2, NeoForge 26.2.0.93, Java 25.0.3,
macOS on Apple Silicon; functional source commit
e41eb02. - All 62 automated tests passed, with a successful CI build.
- A 68-minute dedicated-server soak passed 384 live assertions, followed by a successful server restart with shared playback, paused position, and volume preserved.
- Checks covered concurrent streaming, retry limits, cache eviction, chunk unload, pause/resume/seek, resource reloads, reconnects, and the stopped-boombox tooltip.
- PCM buffers were repeatedly reclaimed during extended playback.
- Soaked artifact SHA-256:
656566e88680e3751ca91c859a844cd2ca5e743260e96525aec995d410215c97.
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:eQMs1sDd:9WzYOTok"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eQMs1sDd:9WzYOTok"
}

