Cooldowns

Cooldowns make certain command (sections) unavailable for a certain amount of time after running it.

So if /example had a 10s cooldown and you ran it, you wouldn't be able to run it again for 10s.

Cooldown logic

• Every command section can have it's own cooldown.
  These don't depend on their parents' cooldowns.
  This just means, that if /example is on cooldown for you, you could still run /example arg1.

• They work with players, the console and command blocks.

• Also, cooldowns will not persists between restarts; are not saved.

Adding a cooldown

You can specify the cooldown duration using the duration format.
Put the cooldown in quotes as YAML may interpret 1d as a double (number) because of the d suffix.

Example:

playtime-reward:
  #...
  executes: #...
  cooldown: '1d' # Will survive restarts
  cooldown-message: 'Playtime reward will be available in <cooldown>' # default: 'Command is on cooldown for <cooldown>'
  literal:help:
    executes: #...
    #no cooldown for '/daily-reward help'