2.0
Compatibility
Changes
NEW FEATURE: LINKED COOLDOWNS
When an anchor material is used and there is a linked cooldown attatched to it, all "secondary" materials attatched to the anchor material are put on cooldown for the specified amount of time
-
4 New commands
-
AddLinkedCooldown [AnchorMaterial] [SecondaryMaterial] [Seconds]
-
RemoveLinkedCooldown [AnchorMaterial] [SecondaryMaterial]
-
ClearLinkedCooldowns
-
ClearCooldowns
-
Bug Fixes
-
Fixed bug where a cooldown would restart when one was already applied by interacting with the item whilst it was on cooldown
-
Fixed bug where players could bypass cooldowns by holding the itemstack outside of their inventories for the tick that the cooldown applied for
Changes
-
/ListCooldowns
- New formatting, shows non linked cooldowns first (if any) then linked cooldowns
-
Global
-
Added support for decimals in adding cooldowns
-
Added new methods of setting cooldowns, should be more universal with cooldowns being set properly
-
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:nlU87rb0:nfUk1hWh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nlU87rb0:nfUk1hWh"
}

