Tags
Creators
Details
8.0.0
Compatibility
Changes
Version 8.0.0:
Updated to 26.1
See the migration guide available on the Ladysnake website.
Starting with alpha-5, world data from previous minecraft versions should be migrated appropriately (thanks Patbox !).
Changes
- Two modules have been renamed in order to match Mojmap names :
cardinal-components-levelhas been renamed tocardinal-components-leveldatacardinal-components-worldhas been renamed tocardinal-components-level- All interfaces inside these modules have been renamed accordingly
- Nullability annotations now use Jspecify, like the base game
Removed
- Components attached to a
LevelDataobject (using thecardinal-components-leveldatamodule) can no longer use dynamic registries in serialization (vanilla limitation) ComponentContainer.Builder#build(String)(had been deprecated for removal for a couple years now)
Fixes
- Fixed game crashing when CCA's config file was invalid
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:RRJmyPMW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K01OU20C:RRJmyPMW"
}

