Command Cooldowns

What are Command Cooldowns?

Command Cooldowns control how often a command can be used.

Some commands can be used without a cooldown, while others have a cooldown configured by default.

For example, commands such as /daily, /weekly, and /monthly use default cooldowns unless changed by the admin.

Cooldown settings and cooldown policies can be managed in the dashboard under Cooldowns.

Cooldown types

Kodo supports two different cooldown types:

Command cooldown

The command cooldown controls how long a user must wait before using the command again.

This is the standard cooldown used by commands such as /daily, /weekly, /monthly, /drop, and others.

Reward cooldown

Some commands also use a reward cooldown.

This controls how often a user can receive rewards from the command.

This is separate from the command cooldown.

For supported reward commands, the reward cooldown is configured in that command’s Currency Settings.

Default cooldowns

Some commands have a default cooldown already configured.

Examples include:

• /daily → 24 hours
• /weekly → 7 days
• /monthly → 1 month

Admins can change these cooldowns if needed.

Cooldown policies

Cooldown Policies let admins change a command’s cooldown for specific roles, users, or the entire server.

This can be used to:

• Reduce cooldowns for special roles
• Give faster cooldowns to boosters or staff
• Apply custom cooldown rules for a specific command
• Create server-wide cooldown changes

A policy can either:

• Set a fixed cooldown
• Apply a cooldown multiplier

Policy scope

Each cooldown policy has a scope that decides where it applies.

Available scope types include:

• All Commands
• Specific Command
• Command Category

This makes it possible to apply one cooldown rule to all commands, only one command, or a full command category.

Policy targets

Each cooldown policy also has a target that decides who receives the cooldown change.

Available target types include:

• Discord Role
• Specific User
• Entire Server

This allows cooldowns to be customized for selected users, roles, or everyone in the server.

Cooldown policy options

A cooldown policy can be configured in different ways.

Override Cooldown

Override Cooldown sets a fixed cooldown in milliseconds.

This completely replaces the command’s original cooldown.

If an override cooldown is set, the multiplier is ignored.

Cooldown Multiplier

Cooldown Multiplier scales the original cooldown.

Examples:

• 0.5 = 50% faster
• 1.5 = 50% slower

This is useful when you want to reduce or increase a cooldown without replacing it completely.

Stacking Multiplier

The Stacking Multiplier is an optional advanced setting used when a policy stacks with other policies.

This allows a different multiplier to be used when multiple policies combine.

Minimum and Maximum Cooldown

Admins can also set optional cooldown limits:

• Minimum Cooldown
• Maximum Cooldown

These limits are applied after the final cooldown has been calculated.

Policy stacking

Cooldown policies can optionally stack with other policies.

This is useful when a user matches more than one policy, such as:

• a staff role
• a booster role
• a special user policy

When stacking is enabled, multiple multiplier policies can combine.

The dashboard also shows a Stacking Preview so admins can see how different combinations affect the final cooldown.

Priority

Each policy has a Priority value.

Lower numbers have higher priority and are evaluated first.

Priority is used to control which policy applies before others.

This is especially important when policies overlap.

Enable Policy

Policies can be enabled or disabled without deleting them.

This makes it easy to temporarily turn cooldown rules on or off.

Notes

Each policy can also include optional notes.

This is useful for describing the purpose of the policy, such as:

• VIP reduction
• staff cooldown bonus
• seasonal event override

Important notes