CrazyCrates, Per-Player Cooldowns Guide
How to configure per-player cooldowns in CrazyCrates to limit crate openings by time, prevent spam, and balance your server economy.
Why Per-Player Cooldowns?
Without cooldowns, a player with fifty keys can open a crate fifty times in under a minute. That floods the economy with prizes, cheapens the excitement of winning, and can cause TPS lag if your crate animation is particle-heavy. Crazycrates per player cooldowns solve all three problems by forcing a wait period between openings, giving each crate event time to breathe.
Cooldowns are especially important on servers where keys are farmable through voting, quests, or the ChestShop player market. If players can earn unlimited keys and burn through them instantly, the value of your crate rewards drops fast. A well-tuned cooldown keeps supply controlled and prizes meaningful.
Setting Up Cooldowns in CrazyCrates
CrazyCrates does not have a single global cooldown toggle. Instead, you configure cooldowns per crate type using the crate's YAML file. Open the crate you want to limit, for example plugins/CrazyCrates/crates/VoteCrate.yml:
Crate:
CrateType: CSGO
OpeningCooldown: 300
The OpeningCooldown value is in seconds. Setting it to 300 means each player must wait five minutes between openings of this specific crate. The cooldown is tracked per player, per crate, so opening the VoteCrate does not affect the timer on your SupplyCrate.
Recommended Cooldown Values
| Crate Tier | Cooldown (seconds) | Reasoning |
|---|---|---|
| Daily/Common | 60 | Fast rewards, low value prizes |
| Vote Crate | 300 | Matches typical vote site cooldown gaps |
| Rank/Premium | 600 | Higher value, slower distribution |
| Event/Legendary | 1800 | Maximum suspense, rarest rewards |
Handling Cooldown Messages
When a player tries to open a crate before their cooldown expires, CrazyCrates sends a configurable denial message. Edit this in your messages.yml:
Messages:
Player:
Crate-Cooldown: "&cYou must wait {time} before opening this crate again."
The {time} placeholder fills in the remaining seconds. You can also use PlaceholderAPI expansions to show the cooldown on scoreboards or holograms so players always know when their next opening is available.
Combining Cooldowns with Key Limits
Crazycrates per player cooldowns pair well with maximum key caps. If you distribute keys through a voting plugin, you can limit the number of keys a player earns per day in your vote plugin config, and then add a cooldown on the crate itself as a second layer. This double gate prevents both key hoarding and rapid-fire openings.
For economy balance, review the Vault economy guide to understand how crate prizes feed into your money supply. Every diamond block or enchanted tool that exits a crate is new wealth entering your server. Cooldowns slow that influx to a manageable rate.
Cooldowns Per Permission Group
If you want VIP players to have shorter cooldowns, use permission-based overrides. CrazyCrates does not natively support per-group cooldowns, but you can create separate crate files for each tier:
# crates/VoteCrate-VIP.yml
Crate:
CrateType: CSGO
OpeningCooldown: 120
Permission: crate.vote.vip
Grant crate.vote.vip through LuckPerms to your VIP group. The VIP crate points to the same physical location but uses a shorter cooldown. This approach gives you full control over cooldown values per rank without needing external addons.
Monitoring Cooldown Impact
After enabling crazycrates per player cooldowns, watch your economy metrics for a week. If inflation slows noticeably, your cooldowns are working. If players complain they cannot use keys fast enough, shorten the timer slightly. The goal is a pace that feels rewarding without flooding the market.
Need full config access? Astroworld Hosting, Pterodactyl panel, NVMe SSDs.