Links
Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 14 hours ago
All versions
1.2.13+1.21.8
Release
1.2.13+1.21.814 hours ago 0
Compatibility
Minecraft: Java Edition
1.21.6–1.21.8
Platforms
Fabric
Quilt
Supported environments
Server-side
Singleplayer
Changes
Changed
- Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.
Fixed
- Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
- pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
- AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
- Forge and NeoForge jars reported their version as
0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried anImplementation-Versionattribute, so the mod list and every log line showed0.0NONE. All 24 loader jars now carry the real version.
Added
- Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
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:IX0J3vJn:WLjOqYlo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IX0J3vJn:WLjOqYlo"
}

