追踪每位玩家的活跃(非挂机)游戏时长,受 LuckPerms 权限控制,旨在为服务器中最活跃的玩家提供奖励计划。一个模组,兼容 Paper、Spigot、
Purpur 和 Folia。
AFK 感知追踪 — 移动、方块/物品栏交互、聊天、指令和战斗均被视为活跃行为;纯视角移动不算在内,因此挂机宏无法刷取奖励。挂机时间与活跃时间分别记录,而非直接丢弃。
- LuckPerms 控制的指令 — 每个子指令都是标准的 Bukkit 权限节点,通过 LuckPerms 以常规方式管理。奖励操作也可通过 LuckPerms API 直接添加组别或提升追踪等级。
- 配置驱动的奖励 — 基于游戏时长和登录连续天数里程碑,以及每日/每周/每月的排行榜结算,执行控制台命令(或专用的
vault:give / luckperms:addgroup /
luckperms:promote 动作)— 不硬依赖任何特定的经济插件。
- 名人堂 — 过往的排行榜周期会被存档,而不仅仅是被覆盖,可通过箱子 GUI 浏览。
- 登录连续天数 — 连续天数单独追踪并奖励,与原始游戏时长分开计算。
- 视觉细节 — 基于 MiniMessage 的
/playtime 统计卡片,带有指向下一个奖励的进度条,分页的排行榜/名人堂 GUI,实时动作栏和可选记分板,挂机标签页列表标签,PlaceholderAPI 扩展,Discord Webhook 公告。
- WorldGuard 区域规则(可选) — 将已知的挂机刷取区域标记为“从不活跃”,或将合法的挂机休息区标记为免于检测。
- 临时事件倍率 —
/playtime event 2 1h 用于设置限时 2 倍活跃时间窗口。
- 默认使用 SQLite,可选 MySQL — 开箱即用无需配置;如需在共享的 BungeeCord/Velocity 网络中使用,可指向 MySQL/MariaDB。
- CSV 导出 — 供管理员审计奖励计划。
可选组件:LuckPerms、PlaceholderAPI、Vault(+ 一个经济插件)、WorldGuard
在 config.yml 中设置 stealth-mode: true 可同时禁用所有面向玩家的通知:
进入/退出挂机的广播、挂机前警告、实时动作栏、侧边栏记分板、
标签页列表中的 [AFK] 标签,以及所有奖励/排行榜公告(游戏内和 Discord)。奖励指令(如 vault:give、luckperms:addgroup 等)仍会正常运行 — 仅抑制公告,以便你可以静默发放奖励。
当 stealth-mode 为 false 时,各个独立开关(afk.broadcast-status-changes、visuals.actionbar.enabled、每个里程碑的 announce、每个 leaderboard-rewards.<period>.announce 等)仍正常工作,如果你想要更精细的控制而非一键切换,可使用这些选项。
隐身模式不会影响权限设置。playtime.use 和 playtime.top 默认对所有玩家设为 true,因此除非你通过权限插件撤销这些节点(例如
/lp group default permission set playtime.use false),否则玩家仍可运行 /playtime 查看自己的统计数据/排行榜。
Tracks each player's active (non-AFK) playtime, gated behind LuckPerms permissions, to power
a rewards program for the most active players on your server. One jar, runs on Paper, Spigot,
Purpur, and Folia
AFK-aware tracking — movement, block/inventory interaction, chat, commands, and
combat all count as activity; pure camera-look movement doesn't, so anti-AFK macros don't
farm rewards. AFK time is tracked separately from active time, not just dropped.
- LuckPerms-gated commands — every subcommand is a standard Bukkit permission node, managed
by LuckPerms the normal way. Reward actions can also add groups / promote tracks directly via
the LuckPerms API.
- Config-driven rewards — playtime and login-streak milestones, plus daily/weekly/monthly
leaderboard payouts, run console commands (or first-class
vault:give / luckperms:addgroup /
luckperms:promote actions) — no hard dependency on any specific economy plugin.
- Hall of Fame — past leaderboard periods are archived, not just overwritten, browsable in a
chest GUI.
- Login streaks — consecutive-day play tracked and rewarded separately from raw playtime.
- Visual details — MiniMessage-driven
/playtime stat card with a progress-to-next-reward
bar, paginated leaderboard/Hall of Fame GUIs, live action bar and optional scoreboard, AFK
tab-list tag, PlaceholderAPI expansion, Discord webhook announcements.
- WorldGuard region rules (optional) — flag known AFK-farm regions as "never active", or
flag a legitimate AFK lounge as exempt from detection.
- Temporary event multipliers —
/playtime event 2 1h for a timed 2x active-time window.
- SQLite by default, MySQL optional — zero-config out of the box; point at MySQL/MariaDB for
a shared BungeeCord/Velocity network.
- CSV export for admins auditing the rewards program.
Optional: LuckPerms, PlaceholderAPI, Vault (+ an economy plugin), WorldGuard
Set stealth-mode: true in config.yml to suppress every player-facing notification at once:
AFK enter/exit broadcasts, the pre-AFK warning, the live action bar, the sidebar scoreboard, the
tab-list [AFK] tag, and all reward/leaderboard announcements (in-game and Discord). Reward
commands (vault:give, luckperms:addgroup, etc.) still run — only the announcements are
suppressed, so you can keep paying out rewards silently.
The individual toggles (afk.broadcast-status-changes, visuals.actionbar.enabled, each
milestone's announce, each leaderboard-rewards.<period>.announce, etc.) still work normally
when stealth-mode is false, if you want more surgical control instead of the all-at-once
switch.
Stealth mode does not touch permissions. playtime.use and playtime.top default to true
for everyone, so players can still run /playtime and see their own stats/the leaderboard unless
you revoke those nodes via your permissions plugin (e.g.
/lp group default permission set playtime.use false).
评论 0
登录后参与评分
还没有评论,来抢沙发吧