Links
Tags
Creators
Details
0.4.0-beta.3+mc1.21.3.fabric
Compatibility
Required content
Changes
0.4.0-beta.3
For every Minecraft release from 1.21.1 to 26.3, up from 0.4.0-beta.1.
Changes
- Phonon runs on Minecraft 1.21.1 through 26.3, on both NeoForge and Fabric. One file covers each loader and group of Minecraft releases; for example, the file for 1.21.3 also runs on 1.21.2.
- On Fabric, Phonon names the oldest Fabric API it runs with, so an older one is reported when the game starts instead of crashing.
On Fabric for Minecraft 1.21.10 and older, a server's library and station lists must fit in one 1 MiB packet, as Fabric API there can't split larger ones; that is several thousand tracks. On Fabric for 1.21.1, the speaker's light strip doesn't glow in the dark.
Test evidence
- Targets: 23 builds, one per loader and group of Minecraft releases, each against that group's newest NeoForge or Fabric API. Java 21 for 1.21.x and Java 25 for 26.x, tested on macOS on Apple Silicon.
- Every build compiles and passes the 63 automated tests.
- Every build passes the short boot test in the real client: a speaker plays in singleplayer, the boombox tooltip shows, and every name has a translation.
- On every release from 1.21.1 to 26.3, a production dedicated server for each loader starts with the release jar,
runs
/phonon reloadand stops cleanly. Releases that share a jar, such as 1.21.2, are booted with the oldest loader version that jar allows. - On 26.3 the full scripted checklist passes on both loaders in the real client and on a dedicated server: playback controls, several speakers, stations and the boombox, 1 MB cache eviction, resource reload, reconnecting and a server restart. Two clients stayed in sync after a seek: NeoForge +20 ms, Fabric +3 ms.
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:BraZ9HIE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eQMs1sDd:BraZ9HIE"
}

