Tags
Creators
Details
3.2.1+1.20.6
Compatibility
Required content
Changes
-
Fix servers not letting clients with Fabric API join
Vanilla clients as well as clients who have the mod installed locally could join, but clients with just Fabric API were rejected.
This is due to a registry mismatch, specifically because the mod was registering a data component for items.
Unfortunately, the "alternate server-side cost display" feature had to be temporarily removed for this.
Optional dependencies
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:WC4UgDcZ:vAm2WOgJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WC4UgDcZ:vAm2WOgJ"
}

