Repository navigation
Persistence and player commands
Cooldowns now survive restarts, several ways to skip or wrongly trigger a cooldown are fixed, and players can check their own cooldowns.
New
- Persistent cooldowns: stored in each player's data, so they survive restarts and
/scd reload. No database or extra files. /scd check: players see their own active cooldowns (sharedcooldowns.check, on by default)./scd check <player>and/scd reset <player>: admins can view or clear an online player's cooldowns (sharedcooldowns.admin).- Configurable messages: all
/scdtext is editable undermessages:inconfig.yml. - New settings:
pending-timeout(default 120 s) andteleport-causes(defaultCOMMAND,PLUGIN).
Fixed
- A second queued teleport, such as a
/tpaaccepted after/home, could get past the cooldown. It is now blocked. - A
/tpaaccepted more than 30 seconds later did not start the cooldown. - Ender pearls and other unrelated teleports could start a conditional cooldown.
- A cooldown was used up even when another plugin cancelled the command or the player lacked permission.
- Registered command aliases could skip the cooldown.
- Cooldowns could end up to one second early, and
time.compactbroke on labels with spaces.
Upgrading
- Requires Paper 26.3+ and Java 25+.
- Replace the old jar. Your
config.ymlkeeps working; new settings use their defaults until you add them. - CMI is no longer a dependency. It still works, because teleports are now detected through Paper's own event.
- If another plugin cancels a command, no cooldown starts. This includes CMI custom aliases that run several commands: list the commands they run instead.