Tags
Creators
Details
1.3.75-SNAPSHOT+316
Compatibility
Changes
Commit acd0679
Fix version-specific packs being skipped for <1.20.3 clients (#120)
For clients older than 1.20.3, getPacksForVersion broke out of the loop after the first matching pack. Since packs are stored in a HashMap and iterated in non-deterministic order, the "all" fallback could be chosen before the version-specific override was ever considered, so the hasVersionOverride preference filter never ran.
Collect all valid packs, apply the version-override preference filter first, then reduce to a single pack for old clients. Use LinkedHashSet for deterministic selection. Same fix applied to Velocity's searchForValidPacks.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
by SamB440 on 2026-06-15
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:v182E90X:TU6WU9HR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v182E90X:TU6WU9HR"
}

