Tags
Creators
Details
0.3.0+26.1.2
Compatibility
Required content
Changes
0.3.0
Party Speakers can now play together. Start music on one, open its settings and choose Link speakers → Select source. At the next speaker, choose Link speakers → Link. A group supports up to eight speakers, up to 64 blocks apart, with the same owner and access policy.
- Play/Pause, Next and station changes work across the group. Each speaker keeps its own volume, listening range and redstone setting.
- Moving between linked speakers no longer starts another copy of the song or adds their volume together. The sound position blends smoothly.
- Built-in playlists on placed speakers keep going when the player walks away, disconnects or switches to a car. The server keeps the queue and song clock; it does not decode music.
- Unlinking pauses the detached speaker and leaves the others playing. Breaking one does not stop the rest; replacing it does not silently restore its link.
- Speaker links survive saving the world. Playback remains session-only, with no force-loaded chunks.
- Minecraft background music fades out while the radio is audible and returns when it is quiet. Game sounds and jukeboxes are unaffected.
- Open speaker controls stay current when another player changes playback. Pending edits are preserved; conflicting changes need an explicit confirmation.
- Fixed the speaker RGB animation so its ring uses the correct texture frame.
The same five stations and 55 tracks from 0.2.0 are included unchanged, including Rowen Rook's five dRock tracks. No new music or another lossy conversion.
Install the matching version on clients and server for shared playback and speaker linking. Keep Custom music and remove any old standalone Stations JAR. Custom/unknown station packs still need their playback client's queue; server playlist continuation applies to the built-in stations, not arbitrary audio.
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:jeo3EZFJ:7ew3HZ2Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jeo3EZFJ:7ew3HZ2Y"
}

