1.1.0
Compatibility
Changes
General bug fixing, added tests and added java runtime configs It is now possible to set wanted major java versions and vendors for the mod, alongside with java downloader using foojay disco if no compatible runtime is found. Curseforge release won't ship the downloader and instead will ask the user to manually install the wanted java version. Mods can ship a java provider and java requirements similar to the command line provider.
Fixed race crash/use after free with hiding early window.
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:zCFNaupz:lewrXGXD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zCFNaupz:lewrXGXD"
}

