0.2.1-beta.2
Compatibility
Required content
Changes
Server upgrades no longer mark a mod incompatible when a mod is republished with the same version number for the target Minecraft version (for example 0.6.6 for 26.2 vs 0.6.6 for 26.3).
/msu stage self keeps the live updater jar until wrapper apply. Staging a newer filename used to delete every MSU jar in mods/ first, so apply quarantined the plan (Staged plan expected to replace a file, but it is missing) and start.sh could not find an updater jar. Obsolete-jar cleanup also refuses to wipe mods/ when the keep file is not on disk.
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:3QdVlEZ7:IkNbR9ve"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3QdVlEZ7:IkNbR9ve"
}

