Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 months ago
All versions
1.1.2+fabric-1.20.1
Release
RemapIDs 1.1.2 (Fabric 1.20.1)3 months ago 10
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Changes
Fixed
- Remaps targeting mod registry entries no longer silently discarded — Remap loading now uses two-phase initialization: JSON is parsed during mod construction, then wildcards are expanded and targets are validated at registry freeze time when all mod entries are available. Previously, validation ran before mod registries were populated, causing any remap targeting a non-vanilla ID (e.g.,
create:andesite_alloy) to be incorrectly filtered out. This also fixes wildcard patterns now correctly matching mod IDs.
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:LS9KUmOO:njtawjXW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LS9KUmOO:njtawjXW"
}

