1.0.1
Compatibility
Changes
Music Machine - 1.20.1 Forge Backport Release
The long-awaited backport to Forge 1.20.1 is finally here! This release brings all the core features of the 1.21.11 NeoForge version down to 1.20.1, with a handful of brand-new UI improvements to make customizing your soundtrack even easier.
✨ New Features & UI Overhaul
- Biome Sub-Categories: The massive "Overworld" track list is now beautifully organized! Songs are grouped by the specific biomes they play in (e.g., Forests & Jungles, Desert & Badlands, Deep Dark), making it much clearer where each track naturally occurs.
- Toggle All Button: A highly requested feature! Added a shiny new "Toggle All" button to the bottom of the config screen so you can instantly enable or disable every track in your current tab with a single click.
- Decluttered Tabs: To keep the category bar clean, the Swamp and Underwater tabs have been folded directly into the Overworld tab as their own sub-categories.
🐛 Bug Fixes & Under-the-Hood Improvements
- 1.20.1 Sound Mapping: Re-mapped all internal track logic to properly hook into Minecraft 1.20.1's legacy
sounds.jsonpaths, ensuring all C418 and newer tracks trigger perfectly. - Fixed "Legacy Profile" Silence: Fixed an issue where selecting the Legacy profile would occasionally cause the game to stop playing music entirely.
- Fixed Long Pauses: Fixed an underlying engine issue that caused the game to wait an unusually long time to play the next song after changing configuration settings.
- UI Readability: Added a darkened background overlay to the config screen so text is always readable, no matter what your Title Screen panorama looks like!
- Codebase Organization: Refactored the repository structure so both the 1.21.11 and 1.20.1 versions can be maintained side-by-side.
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:xAtzKOkC:WcSj9nja"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xAtzKOkC:WcSj9nja"
}

