Links
Tags
Creators
Details
1.1.0
Compatibility
Changes
VersionEye 1.1.0
Plugins that aren't published on Modrinth (most notably ProtocolLib) no longer show up as "not found". VersionEye now falls back to Hangar when a plugin can't be matched on Modrinth.
Added
- Hangar fallback: plugins missing from Modrinth are looked up on Hangar by name (Release channel only, so dev builds are still never reported as updates)
check-hangarconfig option to toggle the fallback (on by default)hangar:<slug>override syntax to pin a plugin to a specific Hangar project, e.g.ProtocolLib: hangar:ProtocolLib- Update notifications now show which source a match came from (
[Modrinth]/[Hangar]) with a clickable link to the project page
Changed
- Both API clients now share a single HTTP connection pool, User-Agent, and rate-limit retry logic
Requires Paper, Purpur, or Folia 26.1+ and Java 25.
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:eWy6nCaZ:gadu2Oj7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eWy6nCaZ:gadu2Oj7"
}

