Tags
Creators
Details
0.5.0
Compatibility
Changes
Catalog manages the Modrinth plugins on your server. Here's what it does:
- recognises the plugins you already have and finds them on Modrinth, with nothing to configure
- tells you when updates come out, and installs them for you if you turn that on
- waits a couple of hours before an automatic update, so if a fix is released in that time frame you won't get the bad version
- searches Modrinth and installs plugins without leaving the game
- lets you pick release, beta or alpha per plugin, and switch to any published build
- moves plugins you remove into a trash folder instead of deleting them
Nothing is ever swapped while the server is running. Updates go to the server and apply on the next restart.
Thanks for reading, see you next version!
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:i5brxoU7:PvFwfKjQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i5brxoU7:PvFwfKjQ"
}

