🕐 Cooldowns

Stop players from mashing the same command over and over. Takes 30 seconds to set up.

New in v4.0 — Config lives at config/CommandMaker/cooldowns.json

The 30-Second Version

{
  "cooldowns": {
    "home": {
      "type": "player",
      "seconds": 30,
      "message": "&cChill out — wait {remaining}s before /home again!"
    }
  }
}

That's it. Now when someone uses /home, they can't use it again for 30 seconds. If they try, they get your message.

Player vs Global

Type	What happens	Good for
`player`	Each player gets their own timer. Only the person who ran the command has to wait.	Teleports, kits, daily rewards
`global`	One person uses it, everyone waits. Server-wide lockout.	Boss summons, server events, world resets

Custom Messages

Put {remaining} wherever you want the countdown number. Colors work with & codes:

"message": "&cNope! &f{remaining}s &cleft on the clock"

Skip the message entirely and we'll use a sensible default.

Checking Cooldowns in Other Aliases

Use ${cooldown_home_remaining} inside any alias to see how long is left. Returns 0 if the cooldown's done. Pairs perfectly with conditions:

if:cooldown(home) say Still waiting... else home

Commands

Command	Does
`/cmd cooldown set <alias> player\|global <seconds> [message]`	Add a cooldown
`/cmd cooldown clear <alias>`	Remove it
`/cmd cooldown list`	See what's configured

💡 Pro tip: Cooldowns reset when the server restarts (they're in-memory). But the config sticks around in cooldowns.json so they come right back next launch.