Tags
Creators
Details
4.2
Compatibility
Changes
In previous versions, the service was quite unstable, but in the current version, it works very well, and we’ve also removed unnecessary login steps. Additionally, there were security issues when applying the instance, but these have been resolved in the current version.
Summary
1.The security issue has been resolved 2.We have removed unnecessary logins. 3.Service Safety 4.Changes to the Instance Deployment System 5.How to Change the Deployment Method for Deployed Instances
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:E5cmhDev:VQ5xeNUX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E5cmhDev:VQ5xeNUX"
}

