1.2.4
Compatibility
Changes
If you're wondering why it takes half a year to longer to get updates on Modrinth than CurseForge, blame the Modrinth team.
Fixed glitch where shift clicking a partial stack onto another partial stack of the same type in a seedbag and immediately closing the window resulted in the transferred stack being deleted (the seed bag forgetting the change).
For the record - it already had the correct behavior when right-clicking a stack in a bag and then immediately closing the GUI (with the stack still on your cursor). Not sure what that conversation was about.
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:DfhoerHn:unQZ0nzC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DfhoerHn:unQZ0nzC"
}

