1.0.1
Compatibility
Changes
CRUCIAL PATCH
ADDITIONS
- Added new manual function known as set_bonuses:uninstall which you MUST run before removing the datapack (either to remove it entirely or to update to a newer version) to ensure that no one gets stuck with buffs that no longer exist.
IMPORTANT NOTICE
If you are updating the datapack from version 1.0 to any future version, please download this version first in order to be able to run the uninstall function, as version 1.0 will not have the same kinds of buffs for everything as even version 1.1. This version's entire existence is effectively damage control. I apologize for this oversight, this was my first datapack so it's only natural something would slip through the cracks.
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:ERDKt6fD:uBnSulNU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ERDKt6fD:uBnSulNU"
}

