boosCooldowns
每条命令独立的冷却时间、预热、限制、价格与禁用规则——共享数据库确保整个服务器网络保持同步。
专为 Paper 1.20+ 构建(已在 1.21.8 和 26.1.2 上测试)。需要 Java 21。即插即用安装,开箱即用的 SQLite,支持多服务器的 MySQL/MariaDB。
✨ 功能特性
核心控制
- 每命令冷却时间 – 支持正则表达式或通配符,按命令组划分,可自定义提示消息
- 预热机制 – 玩家在命令充能期间必须保持静止
- 使用次数限制 – 在指定时间窗口内允许 N 次使用,并支持定时重置
- 消耗价格 – 支持金钱(Vault)、经验等级、物品、PlayerPoints
- 全服冷却时间 – 一名玩家使用
/event 后,所有玩家共享该冷却窗口
- 渐进式冷却时间 – 每次连续使用都会增加乘数,在静默期后重置
- 禁用命令 – 将命令标记为
disabled: true 而无需注销它;提供绕过权限
玩家体验 (UX)
- 预热特效 – Boss 进度条指示器、音效、粒子效果
- 动作栏 (Action bar) – 显示预热倒计时和冷却提示
- 确认对话框 – 点击
[Yes] [No] 按钮处理有消耗的指令,支持按玩家切换开关
- 取消预热时退款 – 可选:当预热被中止时退还已扣除的钱/物品/XP
- 本地化支持 – 放入
messages_<locale>.yml,消息将跟随客户端语言
- 每命令独立消息 – 可为每个命令单独覆盖冷却/预热/禁用的文本
管理工具
/bcd status [player] – 查看所有活跃的冷却时间、剩余使用次数、预热状态
/bcd rule get/set/tempset – 实时检查或修改命令规则(临时覆盖会自动恢复)
/bcd grant cooldown/uses – 手动为玩家预设状态
/bcd clear cooldowns/uses/warmups/all <player> – 精细化清理数据
/bcd reset now/schedule/list – 全局使用计数器重置,支持立即执行或定时计划
/bcd validate – 配置校验器(检测未知键、无效时长、材料/声音拼写错误)
/bcd audit – 决策日志(可选启用)
/bcd diff – 比较共享同一数据库的各节点间的配置哈希值
- 旧版别名 – 所有 4.0 之前的命令名称仍可用(如
clearcooldowns, set, info 等)
- 自动生成帮助 (
/bcd help) – 根据权限过滤,按类别分组显示
- 智能 Tab 补全 – 自动建议选项、玩家名称及已配置的命令
高级功能
- 世界限制 – 规则仅适用于特定世界
- WorldGuard 区域 – 规则仅适用于特定区域内(可选)
- 组继承 –
vip 组继承 default 组的所有规则,仅覆盖所需部分
- 基于事件的重置 – 当玩家击杀实体或获得成就时清除冷却时间;可选发送聊天消息、音效提示及全服广播
- 命名空间感知 – 输入如
/plugin:command 的命令会被重写为其基本形式,以便冷却时间和限制依然生效(无需保留旧的硬性语法阻止器)
- 命令别名 –
/ja hello → /me hello,支持参数替换($1, $*, $player, $world)
- 告示牌快捷方式 – 放置
[boosCooldowns] 告示牌即可以玩家或控制台身份运行命令
- 多服务器漂移检测 – 每个节点对其
config.yml 进行哈希计算,插件会在检测到差异时发出警告,并通过 /bcd diff 进行检查
持久化存储
- SQLite(默认,零配置)或 MySQL / MariaDB(适用于服务器网络)
- JDBC 驱动通过 plugin.yml 中的
libraries: 字段自动下载,无需手动安装
- HikariCP 连接池,热路径读取采用缓存穿透策略
- 基于版本号的迁移脚本(
V1…V4),在启动时自动应用
- 旧版
users.yml 会在首次运行时自动迁移;原文件重命名以确保安全
开发者接口
- 公共 API –
BoosCooldownAPI.getInstance(),包含 isOnCooldown, setCooldown, getRemainingUses 等方法
- 自定义 Bukkit 事件 –
CooldownEvent, WarmupEvent, CommandEvent(全部可取消)
- PlaceholderAPI 扩展 –
%boos_remaining_<cmd>%, %boos_uses_<cmd>%, %boos_on_cooldown_<cmd>%
- bStats 指标统计 – 13 个自定义图表,涵盖存储后端(含驱动版本)、功能开关、检测到的集成、多节点设置、语言分布及配置规模
? 依赖要求
|
版本 |
| Java |
21+ |
| Paper / Spigot / Bukkit |
1.20+ (API) |
| 存储 |
内置 SQLite,或 MySQL 5.7+ / MariaDB 10+ |
可选集成(软依赖)
所有集成均在运行时检测——缺少某项集成仅会禁用对应功能,绝不会导致启动失败。
| 插件 |
解锁功能 |
| Vault + 任何兼容 Vault 的经济插件 (EssentialsX Economy, CMIEconomy, …) |
金钱价格 (price: 100.0) |
| PlayerPoints |
点数价格 (playerpoints: 10) |
| PlaceholderAPI |
%boos_*% 占位符;插件消息中第三方占位符的扩展 |
| WorldGuard |
每命令的区域限制 (regions:) |
| LuckPerms (或任何权限插件) |
基于组的规则目标设定,通过 booscooldowns.<group-name> |
? 安装步骤
- 从 Hangar 页面下载
boosCooldowns.jar。
- 将其放入
plugins/ 文件夹。
- 启动服务器一次 – 默认的
config.yml 将在 plugins/boosCooldowns/ 中生成。
- 编辑
config.yml,然后在游戏内或控制台运行 /bcd reload。
从 4.0 之前版本升级?users.yml 将在首次启动时自动迁移,并重命名为 users.yml.migrated-<timestamp>。
⚙️ 配置要点
数据库
database:
type: sqlite # sqlite (默认) 或 mysql / mariadb
# host: localhost
# port: 3306
# database: boosCooldowns
# username: user
# password: secret
pool-size: 4
cache-ttl-seconds: 30
对于跨多个服务器(BungeeCord/Velocity 网络)的共享冷却时间,请让所有服务器指向同一个 MySQL/MariaDB 实例,并为每个服务器分配唯一的 options.options.node_id。
一条命令规则 —— 所有可用选项
commands:
groups:
default:
/kit:
cooldown: "1 hour"
warmup: 5 # 秒
limit: 3
limit_reset_delay: "6 hours" # 固定窗口
price: 100.0 # Vault 货币
xpcost: 5
playerpoints: 10
itemcost:
item: DIAMOND
count: 1
name: "Kit Token"
server_cooldown: "30 minutes"
# 渐进式冷却 – 每次乘以 ×2,闲置后重置连击数
cooldown_multiplier: 2.0
cooldown_reset_after: "6 hours"
# 限制条件
worlds: [survival, nether]
regions: [spawn, arena] # 需要 WorldGuard
# 效果
warmup_sound: BLOCK_BEACON_AMBIENT
complete_sound: ENTITY_EXPERIENCE_ORB_PICKUP
warmup_particle: ENCHANT
# 权限 + 消息
disabled: false
disabled_message: "&cKit is offline."
cooldown_message: "&7Kit cooling down: &e&seconds&&7."
warmup_message: "&7Preparing kit... &e&seconds&&7."
permission: "myplugin.kit" # 可选的额外门槛
denied_message: "&cNot allowed."
shared_cooldown: [/kit_daily]
shared_limit: [/kit_daily]
vip:
_inherits: default # 继承上述所有 /kit 规则
/kit:
cooldown: "10 minutes" # ……但此项冷却时间更短
别名
commands:
aliases:
/ja: /me # 精确匹配
/tell *: /msg $1 $* # 带参数替换的通配符
占位符:$1, $2, …, $*, $player, $world。
基于事件的冷却重置
event_triggers:
- when: KILL
entity: ENDER_DRAGON
reset_cooldown: /boss_reward
message: "&6You slew the dragon! &e/boss_reward&6 is ready."
sound: ENTITY_PLAYER_LEVELUP
broadcast: true # 默认值:false
- when: ADVANCEMENT
advancement: story/mine_diamond
reset_cooldown: /miner_reward
message: "&a/miner_reward has been reset."
消息占位符:&command&、&player&、&entity&(仅限 KILL)、
&advancement&(仅限 ADVANCEMENT)。
处理 /plugin:command 语法
Minecraft 允许任何人通过输入 /minecraft:tp 而不是 /tp 来绕过冷却时间。你有两种方式阻止这种情况:
- 硬拦截 (
syntax_blocker_enabled: true,默认值) – 拒绝任何带有命名空间前缀的命令,并显示 invalid_command_syntax 消息。虽然严格,但当管理员输入 /paper:version 时可能会造成困扰。
- 透明重写 (
syntax_blocker_enabled: false +
apply_rules_to_prefixed_syntax: true) – 插件在运行规则查找之前,会静默地将 /plugin:cmd 重写为 /cmd。玩家保留快捷方式,管理员保留冷却时间。推荐此选项。
全局选项
options:
options:
disabled_for_ops: true # 插件对 OP 无效
warmups_enabled: true
cooldowns_enabled: true
limits_enabled: true
prices_enabled: true
cancel_warmup_on_move: false
cancel_warmup_on_damage: false
cancel_warmup_on_sneak: false
cancel_warmup_on_sprint: false
cancel_warmup_on_gamemode_change: false
block_interact_during_warmup: false
clear_cooldowns_on_death: false
clear_uses_on_death: false
start_cooldowns_on_death: false
command_logging: false
command_signs: false
syntax_blocker_enabled: true # 直接拒绝 /pluginname:command
# 当拦截器关闭时,将 /plugin:cmd 重写为 /cmd,以便规则仍然适用
apply_rules_to_prefixed_syntax: true
command_confirmation: true # 询问是/否以确认收费命令
refund_on_warmup_cancel: false
audit_enabled: false # 将每个决定持久化到数据库
audit_retention_days: 30
default_locale: en
node_id: "" # "" = 自动主机名:端口
config_sync_interval_seconds: 60
action_bar:
warmup: false
cooldown_on_attempt: false
update_interval_ticks: 10
boss_bar:
warmup: false
color: BLUE # BLUE, GREEN, PINK, PURPLE, RED, WHITE, YELLOW
style: PROGRESS # PROGRESS, NOTCHED_6/10/12/20
? 命令
根命令:/booscooldowns (别名 /bcd)。Tab 补全功能已全面启用。
玩家命令
| 命令 |
默认值 |
用途 |
/bcd status [player] |
true |
查看你的冷却时间、限制和活跃的热身状态。[player] 需要 booscooldowns.status.others 权限 |
/bcd check <command> |
true |
该命令对我是否处于冷却中? |
/bcd confirmations |
true |
切换确认对话框的开启/关闭状态 |
管理
| 命令 |
默认权限 |
用途 |
/bcd reload |
op |
重新加载 config.yml |
/bcd clear cooldowns <player> [command] |
op |
清除活跃的冷却时间 |
/bcd clear uses <player> [command] |
op |
重置使用次数计数器 |
/bcd clear warmups <player> |
op |
取消活跃的预热时间 |
/bcd clear all <player> |
op |
清除冷却时间 + 使用次数 + 预热时间 |
/bcd rule set <option> <command> <value> [group] |
op |
持久化规则覆盖 |
/bcd rule tempset <option> <command> <value> <duration> |
op |
临时覆盖(自动恢复) |
/bcd rule get <command> [group] |
op |
打印生效的规则(继承后) |
/bcd grant cooldown <player> <command> <duration> |
op |
手动设置冷却时间 |
/bcd grant uses <player> <command> <count> |
op |
覆盖剩余使用次数 |
/bcd reset now <command> |
op |
立即清除全局使用计数器 |
/bcd reset schedule <command> <time> |
op |
计划全局重置(格式:+2h、yyyy-MM-dd HH:mm:ss) |
/bcd reset list |
op |
列出待处理的全局重置计划 |
诊断
| 命令 |
默认权限 |
用途 |
/bcd validate |
op |
检查 config.yml 中的拼写错误、无效时长、未知材质/音效 |
/bcd audit [command] [limit] |
op |
读取 command_audit 日志 |
/bcd diff |
op |
比较本节点配置哈希值与对等节点 |
/bcd help [section] |
true |
自动生成帮助;<section> 可深入查看特定组别 |
遗留别名(仍为向后兼容而保留)
| 旧版命令 |
新版命令 |
/bcd clearcooldowns, clearuses, clearwarmups |
/bcd clear cooldowns / uses / warmups |
/bcd set, tempset |
/bcd rule set / tempset |
/bcd scheduleglobalreset, listresets, startglobalreset |
/bcd reset schedule / list / now |
/bcd info, limits, checkcooldown |
/bcd status [player] / /bcd check |
? 权限
玩家级(默认 true)
| 权限节点 |
效果 |
booscooldowns.status |
对自己使用 /bcd status |
booscooldowns.check.cooldown |
使用 /bcd check |
booscooldowns.list.limits |
旧版 – 现由 booscooldowns.status 涵盖 |
绕过权限
| 权限 |
效果 |
booscooldowns.exception |
完全绕过插件 |
booscooldowns.norestriction |
绕过预热/冷却时间/价格/限制(别名仍然生效) |
booscooldowns.nocooldown[./command] |
绕过冷却时间,可选择按命令指定 |
booscooldowns.nowarmup[./command] |
绕过预热阶段 |
booscooldowns.nolimit[./command] |
绕过使用次数限制 |
booscooldowns.noprice[./command] |
绕过 Vault 金钱消耗 |
booscooldowns.noxpcost[./command] |
绕过经验值消耗 |
booscooldowns.noitemcost[./command] |
绕过物品消耗 |
booscooldowns.noplayerpoints[./command] |
绕过 PlayerPoints 消耗 |
booscooldowns.nodisable[./command] |
使用标记为 disabled: true 的命令 |
booscooldowns.noactionbar |
隐藏操作栏通知 |
booscooldowns.nobossbar |
隐藏Boss条预热指示器 |
booscooldowns.nocancel.{move,damage,sneak,sprint,gamemodechange} |
在该事件发生时不取消预热 |
booscooldowns.dontblock.interact |
在预热期间可以与方块/容器进行交互 |
管理员权限(默认 op)
| 权限 |
授予 |
booscooldowns.reload |
/bcd reload |
booscooldowns.status.others |
/bcd status <other player> |
booscooldowns.clearcooldowns |
/bcd clear cooldowns,旧版别名 |
booscooldowns.clearuses |
/bcd clear uses |
booscooldowns.clearwarmups |
/bcd clear warmups |
booscooldowns.clear.all |
/bcd clear all |
booscooldowns.set |
/bcd rule set、tempset,旧版 set/tempset |
booscooldowns.rule.get |
/bcd rule get |
booscooldowns.grant |
/bcd grant cooldown、grant uses |
booscooldowns.scheduleglobalreset |
/bcd reset now、schedule、list |
booscooldowns.validate |
/bcd validate |
booscooldowns.audit |
/bcd audit |
booscooldowns.diff |
/bcd diff |
booscooldowns.signs.{player,server}.{use,place} |
使用/放置 [boosCooldowns] 告示牌 |
群组目标设定
booscooldowns.<group-name> 将玩家置于非默认的指令组中。请配合你的权限插件(如 LuckPerms、PermissionsEx 等)使用:
/lp user Alice permission set booscooldowns.vip true
? PlaceholderAPI
安装 PlaceholderAPI 后,boos 扩展会自动注册。
| 占位符 |
值 |
%boos_remaining_<cmd>% |
格式化后的剩余冷却时间(例如 "2h 15m") |
%boos_remaining_seconds_<cmd>% |
原始整数秒数 |
%boos_on_cooldown_<cmd>% |
true / false |
%boos_server_cooldown_<cmd>% |
全服冷却剩余时间 |
%boos_uses_<cmd>% |
"剩余/上限"(若无上限则为 ∞) |
%boos_uses_remaining_<cmd>% |
原始整数剩余使用次数 |
在命令名称中使用下划线代替空格——例如 %boos_remaining_daily_claim% 对应 /daily claim。前导斜杠是可选的。
你还可以在插件消息中嵌入外部占位符:
cooldown_message: "等待 &e%remaining%&r(余额:&a%vault_eco_balance%&r)"
? 多服务器设置
所有玩家状态(冷却时间、限制、用户偏好、审计日志、定时重置)均通过数据库自动共享。将每个服务器指向同一个 MySQL/MariaDB,即可实现:
- 冷却时间会跟随玩家在整个网络中保持同步
- 全服冷却时间会在所有服务器上阻止每位玩家执行相关操作
- 定时重置会在最先触发该任务的节点上一致执行
命令规则(即 config.yml 中的 commands: 部分)仍为每服务器独立配置——建议通过 git、rsync、符号链接或部署流水线来保持各服务器之间的同步。
该插件内置了漂移检测功能:每个节点在启用和 /bcd reload 时会对 config.yml 进行哈希计算,并将结果写入 config_version;定期任务会在检测到对等节点配置不一致时发出警告。使用 /bcd diff 可一目了然地查看差异所在。
? 面向开发者
API
BoosCooldownAPI api = BoosCooldownAPI.getInstance();
CommandData data = api.buildCommandData(player, "/kit");
if (data != null && !api.isOnCooldown(player, data)) {
api.setCooldown(player, data); // CompletableFuture<Void>
}
在类加载时引用 BoosCooldownAPI 的消费者应在其 plugin.yml 中声明 loadbefore: [boosCooldowns]。
事件
CooldownEvent – 玩家触发了冷却时间(可取消)
WarmupEvent – 准备阶段开始或完成(可取消)
CommandEvent – 插件即将处理命令(可取消,可设置拒绝消息)
? 支持与社区
需要帮助?发现了 Bug?想要建议新功能?
- Discord: – 获取帮助并与其它管理员交流的最快方式
- GitHub: – 源代码、问题追踪器、拉取请求
提交 Bug 报告时,请包含以下内容:
- Paper 版本信息(执行
/version)
- 完整的
latest.log(或与带时间戳的相关部分)
- 你的
config.yml
/bcd validate 的输出结果
/bcd diff 的输出结果(仅限多服务器环境)
? 指标统计
本插件使用 bStats
收集匿名使用数据。除了默认的服务器指标
(玩家数量、Java 版本、在线模式等)之外,该插件还提供以下自定义图表,以便社区了解该插件的实际使用情况:
- 存储后端(SQLite / MySQL),并可下钻至驱动版本
- 多节点设置 – 多少管理员跨服务器共享数据库
- 语言分布(
default_locale)
- 功能开关 – 确认提示、告示牌、动作栏、Boss 栏、审计日志、取消退款
- 检测到的集成 – Vault、PlayerPoints、PlaceholderAPI、WorldGuard、LuckPerms
- 管理员实际启用的插件功能(冷却时间、准备阶段、限制、价格等)
- 已连接的准备阶段取消来源(移动、受到伤害、潜行、疾跑、游戏模式更改)
- 配置规模分桶 – 命令组数量、配置的命令数量、事件触发器数量
你可以在 plugins/bStats/config.yml 中全局选择退出。
? 许可与致谢
依据 MIT 许可证 授权 –
版权所有 © 2011–2026 LordBoos(游戏内名称 boosik)及贡献者。
最初由 LordBoos(游戏内名称 boosik)开发。
boosCooldowns
Per-command cooldowns, warmups, limits, prices and disable rules – with a
shared database so your whole network stays in sync.
Built for Paper 1.20+ (tested on 1.21.8 and 26.1.2). Java 21. Drop-in install,
SQLite out of the box, MySQL/MariaDB for multi-server.
✨ Features
Core control
- Per-command cooldowns – regular expressions or wildcards, per command group, with custom messages
- Warmups – player has to stand still while the command charges up
- Usage limits – N uses per time window, with scheduled resets
- Prices – money (Vault), XP levels, items, PlayerPoints
- Server-wide cooldowns – one player uses
/event, everyone shares the cooldown window
- Progressive cooldowns – multiplier that grows with each consecutive use, resets after a quiet period
- Disable commands – flag a command
disabled: true without unregistering it; bypass permission available
Player UX
- Warmup effects – boss bar progress indicator, sounds, particles
- Action bar for warmup countdown and cooldown notices
- Confirmation dialogs – clickable
[Yes] [No] for commands that cost something, per-player toggle
- Refund on warmup cancel – opt-in return of charged money/items/XP when a warmup is aborted
- Localization – drop
messages_<locale>.yml and messages follow client language
- Per-command messages – override cooldown/warmup/disabled text per command
Admin tooling
/bcd status [player] – every active cooldown, remaining uses, warmup state
/bcd rule get/set/tempset – inspect or mutate command rules live (temp overrides auto-restore)
/bcd grant cooldown/uses – manually seed state on a player
/bcd clear cooldowns/uses/warmups/all <player> – cleanup with granularity
/bcd reset now/schedule/list – global usage-counter resets, immediate or scheduled
/bcd validate – config linter (unknown keys, bad durations, typos in materials/sounds)
/bcd audit – decision log (opt-in)
/bcd diff – compare config hash across nodes sharing the same DB
- Legacy aliases – every pre-4.0 command name still works (
clearcooldowns, set, info, …)
- Autogenerated
/bcd help – permission-filtered, grouped by category
- Smart tab completion – suggests options, player names, configured commands
Advanced
- Per-world restrictions – rule only applies in specific worlds
- WorldGuard regions – rule only applies inside specific regions (optional)
- Group inheritance –
vip group inherits every rule from default, overrides just what it needs
- Event-based resets – wipe a cooldown when the player kills an entity or earns an advancement; optional chat message, sound cue and server-wide broadcast
- Namespace-aware – commands typed as
/plugin:command are rewritten to their bare form so cooldowns and limits still apply (no need to keep the old hard syntax blocker on)
- Command aliases –
/ja hello → /me hello with argument substitution ($1, $*, $player, $world)
- Sign shortcuts –
[boosCooldowns] signs that run commands as player or console
- Multi-server drift detection – each node hashes its
config.yml, plugin warns on divergence, /bcd diff inspects
Persistence
- SQLite (default, zero-config) or MySQL / MariaDB (for networks)
- JDBC drivers auto-downloaded via
libraries: in plugin.yml – no manual install
- HikariCP connection pool, cache-through for hot-path reads
- Schema-versioned migrations (
V1…V4), applied on startup
- Legacy
users.yml is auto-migrated on first run; old file renamed for safety
Developer
- Public API –
BoosCooldownAPI.getInstance() with isOnCooldown, setCooldown, getRemainingUses, …
- Custom Bukkit events –
CooldownEvent, WarmupEvent, CommandEvent (all cancellable)
- PlaceholderAPI expansion –
%boos_remaining_<cmd>%, %boos_uses_<cmd>%, %boos_on_cooldown_<cmd>%
- bStats metrics – 13 custom charts covering storage backend (with driver version), feature toggles, detected integrations, multi-node setups, locale distribution and config scale
? Requirements
|
Version |
| Java |
21+ |
| Paper / Spigot / Bukkit |
1.20+ (API) |
| Storage |
SQLite bundled, or MySQL 5.7+ / MariaDB 10+ |
Optional integrations (soft-depend)
Every integration is detected at runtime – missing one just disables that feature, never breaks startup.
| Plugin |
Unlocks |
| Vault + any Vault-compatible economy (EssentialsX Economy, CMIEconomy, …) |
Money prices (price: 100.0) |
| PlayerPoints |
Point prices (playerpoints: 10) |
| PlaceholderAPI |
%boos_*% placeholders; expansion of third-party placeholders inside plugin messages |
| WorldGuard |
regions: per-command restriction |
| LuckPerms (or any permissions plugin) |
Group-based rule targeting via booscooldowns.<group-name> |
? Installation
- Download
boosCooldowns.jar from the Hangar page.
- Drop it into
plugins/.
- Start the server once – default
config.yml is generated in plugins/boosCooldowns/.
- Edit
config.yml and run /bcd reload in-game or from console.
Upgrading from a pre-4.0 version? users.yml is migrated automatically on first start and renamed to users.yml.migrated-<timestamp>.
⚙️ Configuration essentials
Database
database:
type: sqlite # sqlite (default) or mysql / mariadb
# host: localhost
# port: 3306
# database: boosCooldowns
# username: user
# password: secret
pool-size: 4
cache-ttl-seconds: 30
For shared cooldowns across multiple servers (BungeeCord/Velocity
network), point every server at the same MySQL/MariaDB instance and give
each one a unique options.options.node_id.
A command rule – everything available
commands:
groups:
default:
/kit:
cooldown: "1 hour"
warmup: 5 # seconds
limit: 3
limit_reset_delay: "6 hours" # fixed window
price: 100.0 # Vault money
xpcost: 5
playerpoints: 10
itemcost:
item: DIAMOND
count: 1
name: "Kit Token"
server_cooldown: "30 minutes"
# Progressive cooldown – ×2 each time, streak resets after idle
cooldown_multiplier: 2.0
cooldown_reset_after: "6 hours"
# Restrictions
worlds: [survival, nether]
regions: [spawn, arena] # requires WorldGuard
# Effects
warmup_sound: BLOCK_BEACON_AMBIENT
complete_sound: ENTITY_EXPERIENCE_ORB_PICKUP
warmup_particle: ENCHANT
# Access + messages
disabled: false
disabled_message: "&cKit is offline."
cooldown_message: "&7Kit cooling down: &e&seconds&&7."
warmup_message: "&7Preparing kit... &e&seconds&&7."
permission: "myplugin.kit" # optional extra gate
denied_message: "&cNot allowed."
shared_cooldown: [/kit_daily]
shared_limit: [/kit_daily]
vip:
_inherits: default # all /kit rules above
/kit:
cooldown: "10 minutes" # …except this one gets shorter
Aliases
commands:
aliases:
/ja: /me # exact match
/tell *: /msg $1 $* # wildcard with argument substitution
Placeholders: $1, $2, …, $*, $player, $world.
Event-based cooldown resets
event_triggers:
- when: KILL
entity: ENDER_DRAGON
reset_cooldown: /boss_reward
message: "&6You slew the dragon! &e/boss_reward&6 is ready."
sound: ENTITY_PLAYER_LEVELUP
broadcast: true # default: false
- when: ADVANCEMENT
advancement: story/mine_diamond
reset_cooldown: /miner_reward
message: "&a/miner_reward has been reset."
Message placeholders: &command&, &player&, &entity& (KILL only),
&advancement& (ADVANCEMENT only).
Handling /plugin:command syntax
Minecraft lets anyone bypass a cooldown by typing /minecraft:tp instead
of /tp. You have two ways to stop that:
- Hard blocker (
syntax_blocker_enabled: true, the default) – rejects
any namespace-prefixed command with an invalid_command_syntax message.
Strict but annoying when ops type /paper:version.
- Transparent rewrite (
syntax_blocker_enabled: false +
apply_rules_to_prefixed_syntax: true) – the plugin silently rewrites
/plugin:cmd to /cmd before running its rule lookup. Players keep the
shortcut, admins keep the cooldown. Recommended.
Global options
options:
options:
disabled_for_ops: true # plugin has no effect on ops
warmups_enabled: true
cooldowns_enabled: true
limits_enabled: true
prices_enabled: true
cancel_warmup_on_move: false
cancel_warmup_on_damage: false
cancel_warmup_on_sneak: false
cancel_warmup_on_sprint: false
cancel_warmup_on_gamemode_change: false
block_interact_during_warmup: false
clear_cooldowns_on_death: false
clear_uses_on_death: false
start_cooldowns_on_death: false
command_logging: false
command_signs: false
syntax_blocker_enabled: true # reject /pluginname:command outright
# when the blocker is off, rewrite /plugin:cmd → /cmd so rules still apply
apply_rules_to_prefixed_syntax: true
command_confirmation: true # ask Yes/No for priced commands
refund_on_warmup_cancel: false
audit_enabled: false # persist every decision to DB
audit_retention_days: 30
default_locale: en
node_id: "" # "" = auto hostname:port
config_sync_interval_seconds: 60
action_bar:
warmup: false
cooldown_on_attempt: false
update_interval_ticks: 10
boss_bar:
warmup: false
color: BLUE # BLUE, GREEN, PINK, PURPLE, RED, WHITE, YELLOW
style: PROGRESS # PROGRESS, NOTCHED_6/10/12/20
? Commands
Root command: /booscooldowns (alias /bcd). Tab completion is wired up throughout.
Player commands
| Command |
Default |
Purpose |
/bcd status [player] |
true |
Your cooldowns, limits, active warmup. [player] requires booscooldowns.status.others |
/bcd check <command> |
true |
Is this command on cooldown for me? |
/bcd confirmations |
true |
Toggle the confirmation dialog on/off |
Administration
| Command |
Default |
Purpose |
/bcd reload |
op |
Reload config.yml |
/bcd clear cooldowns <player> [command] |
op |
Clear active cooldowns |
/bcd clear uses <player> [command] |
op |
Reset usage counters |
/bcd clear warmups <player> |
op |
Cancel active warmups |
/bcd clear all <player> |
op |
Wipe cooldowns + uses + warmups |
/bcd rule set <option> <command> <value> [group] |
op |
Persist a rule override |
/bcd rule tempset <option> <command> <value> <duration> |
op |
Temporary override (auto-restores) |
/bcd rule get <command> [group] |
op |
Print effective rules (after inheritance) |
/bcd grant cooldown <player> <command> <duration> |
op |
Seed a cooldown manually |
/bcd grant uses <player> <command> <count> |
op |
Overwrite remaining uses |
/bcd reset now <command> |
op |
Wipe the global usage counter immediately |
/bcd reset schedule <command> <time> |
op |
Schedule a global reset (+2h, yyyy-MM-dd HH:mm:ss) |
/bcd reset list |
op |
List pending scheduled resets |
Diagnostics
| Command |
Default |
Purpose |
/bcd validate |
op |
Lint config.yml for typos, bad durations, unknown materials/sounds |
/bcd audit [command] [limit] |
op |
Read the command_audit log |
/bcd diff |
op |
Compare this node's config hash with peers |
/bcd help [section] |
true |
Autogenerated help; <section> drills into a group |
Legacy aliases (still work for backwards compatibility)
| Legacy |
New |
/bcd clearcooldowns, clearuses, clearwarmups |
/bcd clear cooldowns / uses / warmups |
/bcd set, tempset |
/bcd rule set / tempset |
/bcd scheduleglobalreset, listresets, startglobalreset |
/bcd reset schedule / list / now |
/bcd info, limits, checkcooldown |
/bcd status [player] / /bcd check |
? Permissions
Player-level (default true)
| Permission |
Effect |
booscooldowns.status |
Use /bcd status on yourself |
booscooldowns.check.cooldown |
Use /bcd check |
booscooldowns.list.limits |
Legacy – now covered by booscooldowns.status |
Bypass permissions
| Permission |
Effect |
booscooldowns.exception |
Bypass the plugin entirely |
booscooldowns.norestriction |
Bypass warmups/cooldowns/prices/limits (aliases still apply) |
booscooldowns.nocooldown[./command] |
Bypass cooldowns, optionally per command |
booscooldowns.nowarmup[./command] |
Bypass warmups |
booscooldowns.nolimit[./command] |
Bypass limits |
booscooldowns.noprice[./command] |
Bypass Vault money cost |
booscooldowns.noxpcost[./command] |
Bypass XP cost |
booscooldowns.noitemcost[./command] |
Bypass item cost |
booscooldowns.noplayerpoints[./command] |
Bypass PlayerPoints cost |
booscooldowns.nodisable[./command] |
Use commands flagged disabled: true |
booscooldowns.noactionbar |
Suppress action-bar notifications |
booscooldowns.nobossbar |
Suppress boss-bar warmup indicator |
booscooldowns.nocancel.{move,damage,sneak,sprint,gamemodechange} |
Don't cancel warmup on that event |
booscooldowns.dontblock.interact |
Interact with blocks/containers during warmup |
Admin permissions (default op)
| Permission |
Grants |
booscooldowns.reload |
/bcd reload |
booscooldowns.status.others |
/bcd status <other player> |
booscooldowns.clearcooldowns |
/bcd clear cooldowns, legacy aliases |
booscooldowns.clearuses |
/bcd clear uses |
booscooldowns.clearwarmups |
/bcd clear warmups |
booscooldowns.clear.all |
/bcd clear all |
booscooldowns.set |
/bcd rule set, tempset, legacy set/tempset |
booscooldowns.rule.get |
/bcd rule get |
booscooldowns.grant |
/bcd grant cooldown, grant uses |
booscooldowns.scheduleglobalreset |
/bcd reset now, schedule, list |
booscooldowns.validate |
/bcd validate |
booscooldowns.audit |
/bcd audit |
booscooldowns.diff |
/bcd diff |
booscooldowns.signs.{player,server}.{use,place} |
Use / place [boosCooldowns] signs |
Group targeting
booscooldowns.<group-name> places the player in a non-default command
group. Use with your permissions plugin (LuckPerms, PermissionsEx, etc.):
/lp user Alice permission set booscooldowns.vip true
? PlaceholderAPI
Install PlaceholderAPI and the boos expansion registers automatically.
| Placeholder |
Value |
%boos_remaining_<cmd>% |
Formatted remaining cooldown ("2h 15m") |
%boos_remaining_seconds_<cmd>% |
Raw integer seconds |
%boos_on_cooldown_<cmd>% |
true / false |
%boos_server_cooldown_<cmd>% |
Server-wide cooldown remaining |
%boos_uses_<cmd>% |
"remaining/limit" (or ∞ if no limit) |
%boos_uses_remaining_<cmd>% |
Raw integer remaining uses |
Use underscores instead of spaces in command names – %boos_remaining_daily_claim% for /daily claim. Leading slash is optional.
You can also embed foreign placeholders inside plugin messages:
cooldown_message: "Wait &e%remaining%&r (balance: &a%vault_eco_balance%&r)"
? Multi-server setup
All player state (cooldowns, limits, user preferences, audit log, scheduled resets) is shared automatically through the database. Point every server at the same MySQL/MariaDB and:
- Cooldowns follow the player across the network
- Server-wide cooldowns block every player everywhere
- Scheduled resets fire consistently on the node that happens to trigger first
Command rules (the commands: section of config.yml) still live per-server – keep them in sync via git, rsync, symlink or deploy pipeline.
The plugin ships drift detection: each node hashes its config.yml on enable and on /bcd reload, writes it to config_version, and a periodic task warns you when peers disagree. /bcd diff shows the mismatch at a glance.
? For developers
API
BoosCooldownAPI api = BoosCooldownAPI.getInstance();
CommandData data = api.buildCommandData(player, "/kit");
if (data != null && !api.isOnCooldown(player, data)) {
api.setCooldown(player, data); // CompletableFuture<Void>
}
Consumers referencing BoosCooldownAPI at class-load time should declare loadbefore: [boosCooldowns] in their plugin.yml.
Events
CooldownEvent – player hit an active cooldown (cancellable)
WarmupEvent – warmup is starting or completing (cancellable)
CommandEvent – plugin is about to process a command (cancellable, set deny message)
? Support & community
Need help? Found a bug? Want to suggest a feature?
- Discord: – quickest way to get help and chat with other admins
- GitHub: – source code, issue tracker, pull requests
For bug reports, please include:
- Paper version (
/version)
- Full
latest.log (or the relevant section with timestamps)
- Your
config.yml
/bcd validate output
/bcd diff output (multi-server only)
? Metrics
This plugin uses bStats
to collect anonymous usage data. In addition to the default server metrics
(player count, Java version, online mode, …) the plugin contributes these
custom charts so the community can see how the plugin is actually used:
- Storage backend (SQLite / MySQL) with drill-down to the driver version
- Multi-node setups – how many admins share a DB across servers
- Locale distribution (
default_locale)
- Feature toggles – confirmations, signs, action bar, boss bar, audit, refund-on-cancel
- Detected integrations – Vault, PlayerPoints, PlaceholderAPI, WorldGuard, LuckPerms
- Which plugin features admins actually enable (cooldowns, warmups, limits, prices, …)
- Which warmup-cancel sources are wired up (move, damage, sneak, sprint, gamemode change)
- Config scale buckets – how many command groups, how many configured commands, how many event triggers
You can opt out globally in plugins/bStats/config.yml.
? License & credits
Licensed under the MIT License –
copyright © 2011–2026 LordBoos (in-game boosik) and contributors.
Originally by LordBoos (in-game boosik).
评论 0
登录后参与评分
还没有评论,来抢沙发吧