Tags
Creators
Details
2.6-Beta
Compatibility
Changes
This Beta release is a complete Rewrite of the Plugin.
It does not add any new features, but improves maintainability and therefore allows for easier addition of new features.
The Configuration file has minimal changes, which are migrated fully automatically.
To be precise, the command options where you configure the command which is executed now only allows a string list.
Also, it got renamed.
Your old config file is not deleted but saved in ./migrations
Please report any bugs you encounter on GitHub.
Issues might happen on config migration or general functionality of the Plugin.
I tested as good as possible, but I'm not able to reproduce every production configuration.
Thanks for Testing!
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:zDdNh6jC:61i53ijU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zDdNh6jC:61i53ijU"
}

