Tags
Creators
Details
2.2.0-for-1.19.2
Compatibility
Required content
Changes
Backported YACL 2.2.0 to 1.19.2
Due to breaking JAR compatibility in an earlier version of YACL, mods that support YACL for 1.19.3 can no longer support 1.19.2. This is a backport of YACL 2.2.0 to 1.19.2 to allow mods to support it.
My stance on backporting
Personally, I hate to backport my mods. When breaking changes are made in Minecraft between versions, the code of the mod has to be changed to support the new version, making the older version of MC incompatible. If you want to support multiple versions of Minecraft, you have to maintain multiple branches of the mod, which is a lot of work for just one person, and I don't have the time to do that.
This is a one-off backport, and I will not be backporting any future versions of YACL to 1.19.2. If you want to support and use new features of YACL in your mod, you will have to drop support for 1.19.2.
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:1eAoo2KR:bIVYcRpm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1eAoo2KR:bIVYcRpm"
}

