All versions
1.2
Release
SMPUtils+ 1.2last year 56
Compatibility
Minecraft: Java Edition
1.21–1.21.8
Platforms
Bukkit
Paper
Spigot
Changes
New Feature: CustomCooldowns
Commands
-
/AddCooldown [Material] [Seconds]
- Will tab complete with all vanilla minecraft materials for you to choose from
- Needs 2 inputs of a material and the number of seconds it should be put on cooldown for
-
/RemoveCooldown [Material]
- Will tab complete with all materials that have a custom cooldown
- Needs 1 input of the material to remove the cooldown for
-
/ListCooldowns
- Does not tab complete with anything
- Needs no other inputs
- Outputs a list of all materials with a cooldown and the cooldown attatched to it
-
/AddLinkedCooldown
- Similar to /AddCooldown, will tab complete with all vanilla minecraft materials for you to choose 2 from
- Requires 3 inputs, the Anchor Material, Secondary Material, and the number of seconds the secondary material should be put on cooldown for when the anchor material is used
-
/RemoveLinkedCooldown
- Similar to RemoveCooldown. will tab complete firstly with all the current anchor materials, then all of the secondary materials inside of the anchor material previously written in (i.e. /removeLinkedCooldown [List Of Anchor Materials (for the sake of this it will be wind_charge)] [List of Secondary Materials under Wind Charge])
- Requires 2 inputs of the Anchor and Secondary Materials
-
/ClearLinkedCooldowns
- Will tab complete with all Linked Cooldowns and "all"
- Requires one input of "all" or a material with a linked cooldown
- If "all" is inputted then the command will clear every Linked Cooldown currently active
- If a valid material is inputted, every active secondary cooldown linked to that anchor material will be cleared
-
/ClearCooldowns
- If inputted on its own will pop up with a warning message asking to confirm you want to go ahead, and if so to put in /ClearCooldowns confirm
- If inputted as "/ClearCooldowns confirm" the command will clear every cooldown currently active
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:Mb7K785l:Tq4TnUH2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Mb7K785l:Tq4TnUH2"
}

