Tags
Creators
Details
6.2.1
Compatibility
Changes
Version 6.2.1:
Fixes
- Fixed issue in the
cardinal-components-chunkmodule causing save failures when no mod actually used said module-
Unfortunately, any chunk in which the damage happened will be reset. If you have a backup of your world, you should try loading that. Otherwise, I guess this is a reminder that regular backups are critical, especially when adding new mods or updating across Minecraft versions. In any case, my apologies for the damage and the delay in fixing the bug.
~ PyrofabPS: if you never got spammed by red popups saying "failed to save chunk", you are most likely unaffected by the issue.
-
see full changelog here
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:K01OU20C:HDcFuFlE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K01OU20C:HDcFuFlE"
}

