BetterPunish
BetterPunish 是一款面向 Paper 服务器的管理员工具包。它处理处罚、举报、聊天审核、玩家调查、证据和管理员日志,无需让管理员在多个插件之间跳转或手动编辑数据文件。
每条处罚都拥有独立的 ID 和历史记录。管理员可以稍后查阅、附加证明、检查状态,或在情况变化时进行更正。
服务器所有者青睐的原因
- 在统一的处罚历史中处理封禁、静音、静默静音、警告和踢出
- 可配置的违规等级以应对重复违规行为
- 针对活跃、过期、撤销及旧处罚的分页仪表盘
- 举报、管理员备注、玩家档案、冻结工具及小号提示
- 聊天过滤、反垃圾信息、慢速模式、全局静音及聊天清理
- 默认采用本地 YAML 存储,支持可选的 Supabase 同步
- 直接对接 Discord Components V2 Webhook,提供可自定义的英文/德文通知
- 可选集成 LuckPerms 静音组和 Vulcan 标记功能
主要功能
易于管理的处罚系统
BetterPunish 支持永久性和临时性的封禁、静音、静默静音,以及警告和踢出。原因和默认时长存储在 config.yml 中。当不需要公开公告时,管理员可在支持的处罚命令中使用 -s 或 --silent 参数。
警告同样适用于离线玩家。它们会被保存并在玩家下次登录时送达。
证据通过 /proof 命令与处罚 ID 绑定。一条处罚可以关联多个证明链接,这些链接可通过查询和新详情菜单访问。
管理员工作台
/punishgui 和 /punishments 提供了集中的处罚工作仪表盘。
第一个菜单链接到活跃、近期、过期和撤销的记录,以及分别列出的封禁、静音、警告和静默静音列表。列表采用分页显示,使用玩家头像,并展示关键细节,避免冗长的文本堆砌。
左击记录可查看其详情。拥有 betterpunish.edit 权限的管理员可右击记录进行编辑。详情菜单链接至证据和玩家历史,并且在移除活跃的封禁、静音或静默静音之前会显示确认界面。
玩家搜索通过简短的聊天提示完成,无需玩家在线。输入 cancel 可退出提示;未完成的提示会自动过期。
更正处罚而非替换
/punishedit <id> 打开现有记录的编辑器。原因、总时长和显示的管理员也可以直接更改:
/punishedit <id> reason <new reason>
/punishedit <id> duration <duration>
/punishedit <id> staff <staff>
时长更改使用标准的 BetterPunish 格式,例如 30m、12h、7d、30d 或 permanent。总时长从原始创建时间开始计算,仅适用于封禁(bans)、静音(mutes)和静默静音(shadowmutes)。
原始处罚 ID 永远不会被替换。每次编辑都会在本地历史记录和控制台日志中记录字段、旧值和新值、执行操作的管理员以及时间。证明系统仍继续使用 /proof,而不是单独的仅编辑证据系统。
渐进式违规处理
/offend 对某个规则类别应用下一个配置的处罚。首次违规可能是警告,下一次是临时处罚,之后再犯则是永久处罚。类别、层级、显示名称、重置时间和默认时长均可配置。
处罚系统可以运行在 LEGACY、OFFENSE 或 HYBRID 模式下,因此无需一次性替换现有的命令工作流。
聊天保护
聊天过滤器会移除格式化内容、标准化 Unicode 和常见的 Leetspeak 字符、检查拼接单词,并在测试配置的规则之前压缩重复字符。被阻止的消息可以被记录、向管理员展示,并放入 /chatreview 中进行审查决策。
BetterPunish 还能检测重复消息的刷屏行为,并通过私聊命令、告示牌、书籍和铁砧重命名等方式阻止常见的静音绕过手段。处于静默静音状态的玩家仍然能看到自己的消息,而其他普通玩家则看不到。
对于更广泛的聊天问题,管理员可以使用 /clearchat、/mutechat 和 /slowmode。
举报与管理员工具
玩家可以使用 /report 举报在线玩家。管理员通过 /reports 库存界面处理待处理、已认领和已解决的举报。
内部备注可以通过 /note 添加到已知玩家身上。/check、/checkban 和 /pinfo 可汇总当前有效的处罚、冻结状态、备注、历史记录以及本地关联的账号(如有这些信息可用)。
冻结系统会在调查期间锁定玩家的移动和常见交互行为。它会显示配置的支持链接,如果玩家断开连接,还可以触发一个可配置的冻结日志封禁。
Vulcan 支持
当安装 Vulcan 时,BetterPunish 会监听标记事件并构建嫌疑评分。/sus 和 /suspects 可打开由此生成的管理员仪表板。Vulcan 是可选组件;即使没有它,BetterPunish 的其他功能也能正常工作。
命令与私聊日志
当启用日志记录时,BetterPunish 会记录玩家执行的命令以及配置的私聊别名。管理员可以按玩家搜索、查看最近的私聊消息,或实时监视命令和消息。
最大日志大小、查询限制、别名单词和自动保存间隔均可配置。
本地存储与 Supabase
本地数据存储在 plugins/BetterPunish/data/ 下的独立 YAML 文件中,分别用于存储处罚、举报、备注、聊天审查条目、命令日志和观察到的玩家 IP。插件根目录中的旧文件在首次加载时会被移动到 data 文件夹中。
Supabase 是可选的。配置后,BetterPunish 可以通过 Supabase REST API 同步处罚、证据、支持的处罚编辑、待处理的警告、举报以及玩家 IP 观察记录。/punishmigrate 上传本地处罚历史,而 /punishpull 将处罚记录导入回本地存储。
直接 Discord Webhook
将管理日志直接发送到您自己的 Discord 传入 webhook。无需机器人或额外的 Minecraft 插件。通知使用 Components V2:彩色容器、表情符号标题、分隔符、玩家和管理员详情、原因、适用时长、处罚 ID、时间戳以及一个微妙的页脚。
支持的事件包括 Ban(封禁)、Tempban(临时封禁)、Mute(静音)、Tempmute(临时静音)、Kick(踢出)、Unban(解封)和 Unmute(解除静音),包括静默处罚。单独的 discord.yml 中的设置涵盖英文/德文标签、事件开关、颜色、用户名/头像、标题/页脚、可见字段、时间戳以及可选的玩家头像缩略图。
enabled: true
webhook:
url: "https://discord.com/api/webhooks/WEBHOOK_ID/WEBHOOK_TOKEN"
username: "TGGPunish"
language: en # 或 de
timestamp:
format: "yyyy-MM-dd HH:mm:ss z"
timezone: "Europe/Berlin"
用您的 Discord webhook URL 替换 URL 占位符。运行 /betterpunish webhook reload,然后运行 /betterpunish webhook test;/tggpunish 是其别名。这两个命令默认需要 OP 权限。Webhook 日志记录在未配置前处于禁用状态。
发送在后台工作线程上运行,具有超时、有界队列、显式的 HTTP 429 重试和安全提及处理。最近接受的唯一事件 ID 会进行去重。网络/HTTP 5xx 失败不会自动重试,因为消息可能已经到达。重载/关闭会取消待处理的通知;队列不持久化。
当直接日志记录启用时,这七种事件类型将使用 webhook 而不是传统的配套广播。其他配套警报和 Supabase 同步仍然可用。完整的 webhook 设置和故障排除。
准确的持续时间公告
新的七天处罚被宣布为 7d,即使存储或消息传递需要一点时间。创建和过期使用相同的参考时间戳。封禁屏幕和活动处罚视图仍会显示剩余时间。
Discord 配套服务
配置的 Discord 邀请链接可以在封禁和冻结屏幕上显示。拥有兼容的 BetterPunish 配套服务的服务器还可以设置 discord.bot-url 以将处罚、举报和可疑玩家事件转发到其 HTTP 广播端点。
配套服务不与插件捆绑,也不是必需的。
安装
- 停止服务器。
- 对于 Paper 1.21.11 使用 Java 21,或者对于 Paper 26.1 及更高版本使用 Java 25。
- 将 BetterPunish 1.4.2 JAR 放入服务器的
plugins 文件夹中。
- 启动服务器一次以生成
plugins/BetterPunish/config.yml、plugins/BetterPunish/discord.yml 和本地数据文件夹。
- 设置原因、违规等级、消息、GUI 标题、聊天规则以及任何可选集成。
- 为每个员工组仅授予其所需的权限。
现有安装不需要为 1.4.2 进行数据库迁移。现有的 YAML 和 Supabase 数据格式保持不变。
命令与权限
| 命令 |
功能 |
权限 |
/betterpunish webhook test |
发送一条真实的 Components V2 测试通知。 |
betterpunish.webhook.test |
/betterpunish webhook reload |
重载 discord.yml 并重置投递状态。 |
betterpunish.webhook.reload |
/ban <player> <reason> |
封禁一名玩家,使用配置好的或自定义的理由。 |
betterpunish.ban |
/tempban <player> <duration> <reason> |
临时封禁一名玩家。 |
betterpunish.tempban |
/unban <player|id> |
撤销一项正在生效的封禁。 |
betterpunish.unban |
/mute <player> <reason> |
禁言一名玩家,使用配置好的或自定义的理由。 |
betterpunish.mute |
/tempmute <player> <duration> <reason> |
临时禁言一名玩家。 |
betterpunish.tempmute |
/unmute <player|id> |
撤销一项正在生效的禁言或静默禁言(shadowmute)。 |
betterpunish.unmute |
/shadowmute <player> <reason> |
对一名玩家实施静默禁言。 |
betterpunish.shadowmute |
/tempshadowmute <player> <duration> <reason> |
临时对一名玩家实施静默禁言。 |
betterpunish.tempshadowmute |
/warn <player> <reason> |
警告一名玩家,或将警告排入离线玩家的队列。 |
betterpunish.warn |
/kick <player> <reason> |
踢出在线玩家并记录该操作。 |
betterpunish.kick |
/offend <player> <reason> |
针对某个类别提升玩家的违规等级。 |
betterpunish.offend |
/history <player> [page] |
显示某玩家的处罚历史。 |
betterpunish.history |
/checkban <player|id> |
检查正在生效的制裁措施,或查看某项具体处罚。 |
betterpunish.checkban |
/check <player|id> |
检查制裁措施、冻结状态和备注。 |
betterpunish.checkban |
/pinfo <player|id> |
打开该玩家的管理档案。 |
betterpunish.checkban |
/punishgui [category] [page] |
打开处罚仪表盘或筛选后的列表。 |
betterpunish.gui |
/punishments [category] [page] |
打开处罚仪表盘。 |
betterpunish.gui |
/punishedit <id> |
打开某项处罚的记录编辑器。 |
betterpunish.edit |
/punishedit <id> reason <reason> |
更改显示的处罚理由。 |
betterpunish.edit |
/punishedit <id> duration <duration> |
从原始开始时间起更改总持续时间。 |
betterpunish.edit |
/punishedit <id> staff <staff> |
更改显示的管理人员。 |
betterpunish.edit |
/proof <add|remove|list> <id> [url] |
管理与某项处罚关联的证据。 |
betterpunish.proof |
/report <player> <reason> |
举报一名在线玩家。 |
betterpunish.report |
/reports [page] |
打开举报队列。 |
betterpunish.reports |
/chatreview [page] |
打开被拦截消息的审查队列。 |
betterpunish.chatreview |
/note <add|list|remove|clear> <player> [text/id] |
管理内部员工备注。 |
betterpunish.note |
/freeze <player> [reason] |
冻结或解冻一名在线玩家。 |
betterpunish.freeze |
/unfreeze <player> |
解冻一名在线玩家。 |
betterpunish.freeze |
/clearchat [all] [reason] |
清除普通玩家或所有玩家的聊天内容。 |
betterpunish.clearchat |
/mutechat [reason] |
切换全局聊天禁言状态。 |
betterpunish.mutechat |
/slowmode <seconds|off> |
设置或禁用聊天延迟。 |
betterpunish.slowmode |
/playermsgs <player> [limit] |
显示涉及某玩家的已记录私聊消息。 |
betterpunish.commandlogs |
/playercommands <player> [limit] |
显示某玩家的已记录命令。 |
betterpunish.commandlogs |
/allmsgs [limit] |
显示最近记录的私聊消息。 |
betterpunish.commandlogs |
/livemsgs <player|all|off> |
开始或停止实时私聊监控。 |
betterpunish.live |
/livecommands <player|all|off> |
开始或停止实时命令监控。 |
betterpunish.live |
/sus 或 /suspects |
打开可疑玩家菜单。 |
betterpunish.sus |
/punishreload |
重载配置和处罚数据。 |
betterpunish.reload |
/punishmigrate |
将本地处罚历史记录上传至 Supabase。 |
betterpunish.migrate |
/punishpull |
从 Supabase 导入处罚历史记录。 |
betterpunish.pull |
/punishcleardb |
清除本地及配置的远程处罚数据。 |
betterpunish.cleardb |
默认情况下,/report 对所有玩家开放。管理命令默认仅服务器操作员可用。
有用的辅助权限包括:
betterpunish.staff:用于通用员工警报和部分绕过权限
betterpunish.chatfilter.notify:用于聊天过滤器通知
betterpunish.chatfilter.bypass:用于显式绕过过滤器
betterpunish.offend.exempt:防止 /offend 针对特定玩家执行
仪表盘访问不会自动授予编辑、证据、历史、解封或解除禁言的权限。这些按钮会单独检查其对应的权限。
要求
- 稳定服务器版本: Paper 1.21.11, 26.1, 和 26.2
- 预览版: Paper 26.3 alpha 已通过启动测试,但不属于稳定支持范围
- Java 版本: Paper 1.21.11 需要 Java 21;Paper 26.1 及更高版本需要 Java 25
- Spigot/Folia: 不在支持的服务器策略范围内;请选择 Paper
- 必需插件: 无
- 可选: LuckPerms 5.x 用于禁言组同步
- 可选: Vulcan 用于反作弊标记追踪
- 可选服务: Direct Discord 传入 Webhook、Supabase 以及兼容的 Discord 配套端点
适用场景
BetterPunish 适合 SMP、生存、PvP 和网络服务器,这些服务器希望拥有共享的处罚历史和直观的管理工具,而无需依赖远程数据库。
文档
阅读公开文档 以获取配置、权限、命令和集成设置的说明。
支持
在寻求帮助时,请提供 BetterPunish 版本、Paper 版本、Java 版本以及相关控制台错误信息。在分享文件之前,请移除 Discord Webhook URL、Supabase 密钥、玩家 IP、证据链接和其他隐私数据。
BetterPunish
BetterPunish is a staff toolkit for Paper servers. It handles punishments, reports, chat moderation, player investigations, evidence, and staff logs without forcing moderators to jump between several plugins or edit data files by hand.
Every punishment gets its own ID and history. Staff can look it up later, attach proof, check its status, or correct it when something changes.
Why Server Owners Like It
- Bans, mutes, shadowmutes, warns, and kicks in one punishment history
- Configurable offense tiers for repeat rule breaks
- A paginated dashboard for active, expired, revoked, and older punishments
- Reports, staff notes, player profiles, freeze tools, and alt-account hints
- Chat filtering, anti-spam, slowmode, global mute, and chat clearing
- Local YAML storage by default, with optional Supabase synchronization
- Direct Discord Components V2 webhooks with customizable English/German notifications
- Optional LuckPerms mute-group and Vulcan flag integrations
Main Features
Punishments That Stay Manageable
BetterPunish supports permanent and temporary bans, mutes, and shadowmutes, plus warns and kicks. Reasons and default durations live in config.yml, and staff can use -s or --silent on supported punishment commands when a public announcement is not wanted.
Warnings also work for offline players. They are saved and delivered when the player next joins.
Evidence stays tied to the punishment ID through /proof. A punishment can have several proof links, and those links remain available from lookups and the new details menu.
The Staff Desk
/punishgui and /punishments provide a central dashboard for punishment work.
The first menu links to active, recent, expired, and revoked records, along with separate lists for bans, mutes, warns, and shadowmutes. Lists are paginated, use player heads, and show the important details without filling the lore with walls of text.
Left-click a record to open its details. Staff with betterpunish.edit can right-click it to edit. The details menu links to proof and player history and uses a confirmation screen before an active ban, mute, or shadowmute can be removed.
Player search works through a short chat prompt and does not require the player to be online. Type cancel to leave the prompt; abandoned prompts expire automatically.
Correct a Punishment Instead of Replacing It
/punishedit <id> opens the editor for an existing record. Reason, total duration, and displayed moderator can also be changed directly:
/punishedit <id> reason <new reason>
/punishedit <id> duration <duration>
/punishedit <id> staff <staff>
Duration changes use the normal BetterPunish format, such as 30m, 12h, 7d, 30d, or permanent. The total duration is measured from the original creation time and is only available for bans, mutes, and shadowmutes.
The original punishment ID is never replaced. Each edit records the field, old and new values, staff member, and time in local history and the console log. Proofs continue to use /proof rather than a separate edit-only evidence system.
Progressive Offenses
/offend applies the next configured punishment for a rule category. A first offense can be a warning, the next a temporary punishment, and a later one permanent. Categories, tiers, display names, reset time, and default duration are all configurable.
The punishment system can run in LEGACY, OFFENSE, or HYBRID mode, so an existing command workflow does not need to be replaced all at once.
Chat Protection
The chat filter removes formatting, normalizes Unicode and common leetspeak, checks joined words, and squeezes repeated characters before testing the configured rules. Blocked messages can be logged, shown to staff, and placed in /chatreview for a decision.
BetterPunish also catches repeated-message spam and blocks common mute bypasses through private-message commands, signs, books, and anvil renames. Shadowmuted players still see their own messages while regular players do not.
For wider chat problems, staff can use /clearchat, /mutechat, and /slowmode.
Reports and Staff Tools
Players can report an online player with /report. Staff handle open, claimed, and resolved reports from the /reports inventory.
Internal notes can be added to known players with /note. /check, /checkban, and /pinfo bring together active punishments, freeze state, notes, history, and locally linked accounts where that information is available.
The freeze system locks movement and common interactions while a player is being investigated. It shows the configured support link and can issue a configurable freeze-log ban if the player disconnects.
Vulcan Support
When Vulcan is installed, BetterPunish listens for flag events and builds a suspicion score. /sus and /suspects open the resulting staff dashboard. Vulcan is optional; the rest of BetterPunish works without it.
Command and Private-Message Logs
BetterPunish records player commands and configured private-message aliases when logging is enabled. Staff can search by player, review recent private messages, or watch commands and messages live.
The maximum log size, query limit, aliases, and autosave interval are configurable.
Local Storage and Supabase
Local data is stored under plugins/BetterPunish/data/ in separate YAML files for punishments, reports, notes, chat-review entries, command logs, and observed player IPs. Older files in the plugin root are moved into the data folder when they are first loaded.
Supabase is optional. When configured, BetterPunish can synchronize punishments, proofs, supported punishment edits, pending warnings, reports, and player IP observations through the Supabase REST API. /punishmigrate uploads local punishment history, and /punishpull imports punishment records back into local storage.
Direct Discord Webhooks
Send moderation logs straight to your own Discord incoming webhook. No bot or extra Minecraft plugin is required. Notifications use Components V2: a colored container, emoji heading, separators, player and moderator details, reason, applicable duration, punishment ID, timestamp, and a subtle footer.
Supported events are Ban, Tempban, Mute, Tempmute, Kick, Unban, and Unmute, including silent punishments. Settings in the separate discord.yml cover English/German labels, event toggles, colors, username/avatar, title/footer, visible fields, timestamps, and optional player-head thumbnails.
enabled: true
webhook:
url: "https://discord.com/api/webhooks/WEBHOOK_ID/WEBHOOK_TOKEN"
username: "TGGPunish"
language: en # or de
timestamp:
format: "yyyy-MM-dd HH:mm:ss z"
timezone: "Europe/Berlin"
Replace the URL placeholders with your Discord webhook URL. Run /betterpunish webhook reload, then /betterpunish webhook test; /tggpunish is an alias. Both commands default to OP. Webhook logging starts disabled until you configure it.
Delivery runs on a background worker with timeouts, a bounded queue, explicit HTTP 429 retries, and safe mention handling. Recently accepted event IDs are deduplicated. Network/HTTP 5xx failures are not retried automatically because the message may already have arrived. Reload/shutdown cancel pending notifications; the queue is not persisted.
While direct logging is enabled, these seven event types use the webhook instead of the legacy companion broadcast. Other companion alerts and Supabase synchronization remain available. Full webhook setup and troubleshooting.
Accurate Duration Announcements
A new seven-day punishment is announced as 7d, even if storage or message delivery takes a moment. Creation and expiration use the same reference timestamp. Ban screens and active punishment views still display the remaining time.
Discord Companion Service
The configured Discord invite can be shown on ban and freeze screens. Servers with a compatible BetterPunish companion service can also set discord.bot-url to forward punishment, report, and suspicious-player events to its HTTP broadcast endpoint.
The companion service is not bundled with the plugin and is not required.
Installation
- Stop the server.
- Use Java 21 for Paper 1.21.11, or Java 25 for Paper 26.1 and newer.
- Put the BetterPunish 1.4.2 JAR into the server's
plugins folder.
- Start the server once to generate
plugins/BetterPunish/config.yml, plugins/BetterPunish/discord.yml, and the local data folder.
- Set up reasons, offense tiers, messages, GUI titles, chat rules, and any optional integrations.
- Give each staff group only the permissions it needs.
Existing installations do not need a database migration for 1.4.2. Existing YAML and Supabase data formats remain unchanged.
Commands & Permissions
| Command |
What it does |
Permission |
/betterpunish webhook test |
Send a real Components V2 test notification. |
betterpunish.webhook.test |
/betterpunish webhook reload |
Reload discord.yml and reset delivery. |
betterpunish.webhook.reload |
/ban <player> <reason> |
Ban a player with a configured or custom reason. |
betterpunish.ban |
/tempban <player> <duration> <reason> |
Temporarily ban a player. |
betterpunish.tempban |
/unban <player|id> |
Revoke an active ban. |
betterpunish.unban |
/mute <player> <reason> |
Mute a player with a configured or custom reason. |
betterpunish.mute |
/tempmute <player> <duration> <reason> |
Temporarily mute a player. |
betterpunish.tempmute |
/unmute <player|id> |
Revoke an active mute or shadowmute. |
betterpunish.unmute |
/shadowmute <player> <reason> |
Shadowmute a player. |
betterpunish.shadowmute |
/tempshadowmute <player> <duration> <reason> |
Temporarily shadowmute a player. |
betterpunish.tempshadowmute |
/warn <player> <reason> |
Warn a player or queue an offline warning. |
betterpunish.warn |
/kick <player> <reason> |
Kick an online player and record it. |
betterpunish.kick |
/offend <player> <reason> |
Apply the next offense tier for a category. |
betterpunish.offend |
/history <player> [page] |
Show a player's punishment history. |
betterpunish.history |
/checkban <player|id> |
Check active sanctions or inspect one punishment. |
betterpunish.checkban |
/check <player|id> |
Check sanctions, freeze state, and notes. |
betterpunish.checkban |
/pinfo <player|id> |
Open the player moderation profile. |
betterpunish.checkban |
/punishgui [category] [page] |
Open the punishment dashboard or a filtered list. |
betterpunish.gui |
/punishments [category] [page] |
Open the punishment dashboard. |
betterpunish.gui |
/punishedit <id> |
Open the editor for a punishment. |
betterpunish.edit |
/punishedit <id> reason <reason> |
Change the displayed reason. |
betterpunish.edit |
/punishedit <id> duration <duration> |
Change the total duration from its original start time. |
betterpunish.edit |
/punishedit <id> staff <staff> |
Change the displayed moderator. |
betterpunish.edit |
/proof <add|remove|list> <id> [url] |
Manage evidence attached to a punishment. |
betterpunish.proof |
/report <player> <reason> |
Report an online player. |
betterpunish.report |
/reports [page] |
Open the report queue. |
betterpunish.reports |
/chatreview [page] |
Open the blocked-message review queue. |
betterpunish.chatreview |
/note <add|list|remove|clear> <player> [text/id] |
Manage internal staff notes. |
betterpunish.note |
/freeze <player> [reason] |
Freeze or unfreeze an online player. |
betterpunish.freeze |
/unfreeze <player> |
Unfreeze an online player. |
betterpunish.freeze |
/clearchat [all] [reason] |
Clear chat for regular players or everyone. |
betterpunish.clearchat |
/mutechat [reason] |
Toggle the global chat mute. |
betterpunish.mutechat |
/slowmode <seconds|off> |
Set or disable the chat delay. |
betterpunish.slowmode |
/playermsgs <player> [limit] |
Show logged private messages involving a player. |
betterpunish.commandlogs |
/playercommands <player> [limit] |
Show a player's logged commands. |
betterpunish.commandlogs |
/allmsgs [limit] |
Show recent logged private messages. |
betterpunish.commandlogs |
/livemsgs <player|all|off> |
Start or stop live private-message monitoring. |
betterpunish.live |
/livecommands <player|all|off> |
Start or stop live command monitoring. |
betterpunish.live |
/sus or /suspects |
Open the suspicious-player menu. |
betterpunish.sus |
/punishreload |
Reload configuration and punishment data. |
betterpunish.reload |
/punishmigrate |
Upload local punishment history to Supabase. |
betterpunish.migrate |
/punishpull |
Import punishment history from Supabase. |
betterpunish.pull |
/punishcleardb |
Clear local and configured remote punishment data. |
betterpunish.cleardb |
/report is available to players by default. Staff commands default to server operators.
Useful supporting permissions include:
betterpunish.staff for general staff alerts and selected bypasses
betterpunish.chatfilter.notify for chat-filter notifications
betterpunish.chatfilter.bypass for an explicit filter bypass
betterpunish.offend.exempt to block /offend from targeting a player
Dashboard access does not automatically grant edit, proof, history, unban, or unmute access. Those buttons check their own permissions.
Requirements
- Stable servers: Paper 1.21.11, 26.1, and 26.2
- Preview: Paper 26.3 alpha has passed startup testing but is not a stable support claim
- Java: 21 for Paper 1.21.11; 25 for Paper 26.1 and newer
- Spigot/Folia: Outside the supported server policy; choose Paper
- Required plugins: None
- Optional: LuckPerms 5.x for mute-group synchronization
- Optional: Vulcan for anti-cheat flag tracking
- Optional services: Direct Discord incoming webhook, Supabase, and a compatible Discord companion endpoint
Best For
BetterPunish fits SMP, survival, PvP, and network servers that want a shared punishment history and straightforward staff tools without requiring a remote database.
Documentation
Read the public documentation for configuration, permissions, commands, and integration setup.
Support
When asking for help, include the BetterPunish version, Paper version, Java version, and the relevant console error. Remove Discord webhook URLs, Supabase keys, player IPs, proof links, and other private data before sharing files.
评论 0
登录后参与评分
还没有评论,来抢沙发吧