Tags
Creators
Details
1.7.1+mc1.21.6-26.2-forge
Compatibility
Changes
No behaviour change. Metadata release: the Minecraft version list on every file is now generated from the repository's coverage table, and every version listed is booted as a real server by CI or carries a written reason why it is not (issue #84). Two claims that could not work were removed: Forge 1.14-1.14.3 and 1.16 (no Forge build, or FML refusing the jar's javafml range) and Forge 1.21.2 (no Forge build). The mc1.14.x jar now ships as two files' worth of listing - +mc1.14.x for Fabric and Quilt, +mc1.14.x-fabric for the four 1.14 releases Quilt Loader has no build for.
https://github.com/ashwalk33r/minecraft-fabric-commandsspy/pull/85
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:ZeMREG8v:WDzuuyNJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZeMREG8v:WDzuuyNJ"
}

