Tags
Creators
Details
0.2.32.1
Compatibility
Changes
In the previous update, we introduced a new feature: the custom database driver loading. Unfortunately, due to an oversight on our part, this feature was broken, and we failed to catch this problem in time. So here is a hotfix version with actually working custom database driver loading ;)
For more about 0.2.32.x, see the previous changelog.
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:8sg1aj4I:penBORky"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8sg1aj4I:penBORky"
}

