All versions
1.1.0
Release
Music Regions 1.1.03 months ago 28
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Music Regions 1.1.0
Major Improvements
Improved Region Synchronization
- Completely revamped region syncing between server and client.
- Regions now properly load when joining worlds with existing painted chunks.
- Fixed issues where newly created regions would not appear in the region manager list.
- Improved handling of large regions with thousands of painted chunks.
Improved Large Region Support
- Optimized chunk data transfer for large painted areas.
- Large radius painting (500+ chunk radius tested) now works reliably.
- Reduced packet-related issues when loading regions with many chunks.
Bug Fixes
Region Manager Fixes
- Fixed regions not appearing in the region list after creation.
- Fixed region data not refreshing properly after creating, deleting, or editing regions.
- Fixed client-side cache issues causing outdated region information.
Music Playback Fixes
- Fixed music regions only playing the first song in a region's playlist.
- Regions with multiple songs now properly select songs randomly.
- Improved song transitions between different regions.
Performance Fixes
- Removed unnecessary debug logging.
- Improved chunk removal performance when erasing painted areas.
- Fixed lag spikes caused by removing chunks from very large regions.
Technical Changes
Networking Improvements
- Reworked region synchronization packets.
- Improved handling of region data between server and client.
- Added better support for syncing large amounts of chunk data.
Stability Improvements
- Improved world loading compatibility with existing Music Regions data.
- Fixed crashes caused by malformed region synchronization data.
Notes
- Existing worlds and painted regions are fully compatible with this update.
- No manual migration is required.
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:anrzOK5H:37APWIuF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:anrzOK5H:37APWIuF"
}

