Links
Tags
Creators
Details
Licensed MIT
Published last month
Updated 2 months ago
All versions
1.01
Release
ItemCooldowns 1.012 months ago 608
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
BungeeCord
Folia
Paper
Purpur
Spigot
Waterfall
Changes
v1.01
- PvPManager integration (SpigotMC #25420, including the ChanceSD fork v4): attacks blocked by PvPManager (newbie protection, respawn protection, PvP mode disabled) do not apply cooldowns and do not trigger the gamemode switch. Configurable via
pvpmanager.enabled - New
use-modeoption for spear and trident:block— the lunge/throw is fully blocked during the cooldowndamage(default) — the lunge/throw works, all damage is blocked during the cooldownno-damage— the lunge/throw always works as movement but deals no damage; attacks still have the cooldown
- Trident cooldown now starts on actual throw (
ProjectileLaunchEvent) instead of on right-click charge — charging is no longer cancelled - Removed off-hand attack checks (vanilla melee always uses the main hand — a fist with a trident in the off hand no longer triggers cooldowns)
- Cooldowns are cleared when a player leaves the server
- New config keys are added automatically to existing installations (
ensureConfigDefaults) creative-to-survival-on-player-hitoption (oldgamemode.switch-creative-to-survivalstill supported)folia-supported: true, thread-safe cooldown tracking- Mace smash protection (multi-target hit in one swing) now uses a time window instead of world ticks
- Fixed: cooldown triggered by opening chests/doors with a gated item in hand
- Fixed: phantom end-crystal cooldowns
- Fixed: anchor clicks no longer cancel block placement on the anchor
- Fixed: message spam during cooldown (throttled to once per 3 seconds)
- Creative→survival switch respects
itemcooldowns.bypass
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:EITW6QSF:WqInogMl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EITW6QSF:WqInogMl"
}

