Links
Tags
Creators
Details
0.3.1+mc26.1.2
Compatibility
Changes
0.3.1
For Minecraft 26.1.2, up from 0.3.0-alpha.3. It adds everything in the 0.3.0 and 0.3.0-beta sections below: stations, playlists, the boombox, finding tracks by title and the new speaker screen.
Changes
- On a station, the speaker screen shows who runs it beside Now Playing, and the audio meter stays clear.
- Playback buttons say when they act for everyone, such as "Pause · for everyone". Locked ones still say why.
- Pressing Enter on an existing station's name tunes to that station instead of creating a second one with the same name.
- Long playback no longer grows native memory.
- Phonon's logo shows in the game's mod list.
Test evidence
- Target: Minecraft 26.1.2, NeoForge 26.1.2.80, Java 25, tested on macOS on Apple Silicon.
- 63 automated tests pass, and the scripted checklist passes in the real client and on a dedicated server: playback controls, several speakers, 1 MB cache eviction, resource reload, reconnecting and a server restart.
- Audio captured from the running client matched the source recording at 0.994 correlation. A test tone panned fully left and right, and a stone wall and water cut 3 kHz by 25 dB and 10 dB against 300 Hz.
- 46 minutes of continuous play on a dedicated server, with three speakers and a station, passed 260 checks with Java and native memory flat. A separate full run passed its chunk unload and server restart checks.
- Two clients on a dedicated server stayed in sync: -17 ms at late join and -11 ms after a seek.
- In the real client: starting a station, pressing Enter on its name in different capitals tuned a second speaker instead of creating a duplicate, the boombox screen opened, and
/phonon add <title>added a YouTube result. - The release jar booted into a world in a clean NeoForge install.
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:4zz5Lljs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eQMs1sDd:4zz5Lljs"
}

