Tags
Creators
Details
0.7.0-beta.1+old-forge.1.17.1
Compatibility
Required content
Changes
Changes since 0.7.0-alpha.4
A fairly bug-fix focused release this time around. This release should fully supersede 0.6.9.2 for those still using it.
- Updated branding!
- Update to Minecraft 26.2 and 26.3
- Fix Forge compatibility
- Intrusion detection on startPlaying for improved mod compatibility
- Inject config screen into accessibility onboarding in 26.1+
- Partially support FrozenLib, Legacy4J, Vanilla Backport
- Tag series within the version string; largely cosmetic but helpful.
Full Changelog: https://github.com/Modflower/music-moods/compare/v0.7.0-alpha.4...v0.7.0-beta.1
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:z23qey0b:JMJfXiaD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z23qey0b:JMJfXiaD"
}

