2.4.2
Compatibility
Changes
Added a configs for Server owners to choose whether or not they want custom records enabled, also so players aren't forced to download the executables if they just want vanilla functionality.
Setting custom records to true, will automatically update the executables during mod launch if needed, to keep everything working.
audio_cache folder will delete monthly, to clean out unused records. If players still have said record, that audio assosiated with it will be re-downloaded upon playback and the month timer will reset. (Can also be edited in config)
Many more minor fixes and changes :)
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:cz7pKjRu:JXfHxbaO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cz7pKjRu:JXfHxbaO"
}

