Tags
Creators
Details
1.0.6
Compatibility
Changes
I've been meaning to get around to this for a while. I kinda had to relearn how Fabric handles client and server code. Found out the hard way that they finally separated the main and client directories/classes finally. Anyway, here are the changes:
- Updated to support 1.21 and above.
- Fixed the version string substitution in fabric.mod.json
- Moved all code from main to client.
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:1ZCQhSfC:4s6Y9CiV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1ZCQhSfC:4s6Y9CiV"
}

