Tags
Creators
Details
1.1.0+26.3
Compatibility
Required content
Changes
Your music, shared your way
Autoradio 1.1.0 · Minecraft 26.3 · Release
There’s more to a good soundtrack than pressing Play. This update adds new ways to listen together, keep a favourite recording and manage the music without losing sight of the drive.
What’s new
- Shared listening groups with owner and DJ controls, plus a shortcut beside the F7 wheel.
- Custom-music cassettes: turn imported tracks into labelled, coloured cassettes with world-backed recordings.
- Pause and device-volume controls for shared Custom music and cassettes.
- Now Playing at the top centre, with improvements to online-radio startup, background playback and reconnection.
The five built-in stations and all 55 tracks are unchanged. Internet radio and AAC/AAC+ support were already included in 1.0.0.
Make yourself at home
Use F7 for the quick radio wheel, F12 for device and shared-listening controls, and F9 to import your own music. Internet audio and other players’ Custom music keep their separate listening choices.
Before you update
Use Automobility 1.3.0+26.3-fabric with this release. Install one full Autoradio JAR; the Stations pack and decoder libraries are included, with no external codec installation needed.
For shared listening and cassettes, update the server and clients together. Back up the complete world and config/automobility-autoradio, including Custom music. Keep your preferences and permissions. Mixed old/new installations are not advertised as supported; roll back using the complete matching backup.
For this file: Minecraft 26.3 · Fabric Loader >=0.19.3 · Fabric API >=0.161.0+26.3 · Java 25+. Use dependencies built for Minecraft 26.3.
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:312F9ooc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jeo3EZFJ:312F9ooc"
}

