Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 11 months ago
Updated 4 hours ago
All versions
0.4.0-beta.1+mc26.2.neoforge
Beta
Phonon 0.4.0-beta.1 for NeoForge 26.24 hours ago 4
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
0.4.0-beta.1
For Minecraft 26.2, up from 0.3.1.
Changes
- Phonon runs on Fabric as well as NeoForge, with the same blocks, items, commands and settings. It needs Fabric API.
Settings are in
config/phonon-server.jsonandconfig/phonon-client.json, and Mod Menu shows a button for the client settings. - A Fabric client whose Phonon can't talk to the server's is told to install the server's version when it joins, as NeoForge already does.
Fabric and NeoForge players can't join each other's servers, since the loaders differ. On NeoForge nothing changes for players.
Test evidence
- Targets: Minecraft 26.2 with NeoForge 26.2.0.93, and with Fabric Loader 0.20.1 and Fabric API 0.161.0+26.2. Java 25, tested on macOS on Apple Silicon.
- 63 automated tests pass.
- The 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 on a dedicated server stayed in sync. Fabric: -20 ms at late join and -2 ms after a seek. NeoForge: -30 ms and -20 ms.
- Production dedicated servers for both loaders, set up by NeoForge's installer and Fabric's server launcher, start with the release jar, run
/phonon reloadand stop cleanly.
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:GVp8yCwc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eQMs1sDd:GVp8yCwc"
}

