建议、错误报告或问题?请使用插件反馈表单。
ReportSystem
玩家通过菜单提交举报,工作人员在各自的界面查看,并同步副本至 Discord。
玩家输入 /report 后选择目标及原因,然后提交举报。工作人员会立即收到聊天室中的举报通知,并通过 /reports 菜单处理这些举报。举报也可以自动发送到指定的 Discord 频道。ReportSystem 不包含自动处罚功能或反作弊功能。
概述
- 玩家举报菜单。 选择目标,从列表中选择理由,添加额外信息以及可选的 Discord 联系方式。或者你也可以完整输入举报内容:
/report player Steve griefing broke my base - 工作人员举报队列,支持排序、筛选、优先级设置、备注,以及使用关闭备注关闭举报的功能
- 三种类型的举报: 玩家、工作人员(私密)和 Bug
- 举报以 Discord 嵌入卡片形式呈现,每条举报对应一个嵌入卡片,颜色表示状态
- 支持多网络架构。 在单个 MySQL 数据库中使用共享的单一举报列表。使用 Redis 实现实时全局通知。
特性
- 队列。 按违规行为或类型进行筛选,按最旧、最新或优先级排序,分页浏览队列,刷新页面,并查看特定用户的举报历史。
- 优先级 可以是普通、高或低,也可以根据发起举报的用户等级自动分配。
- 带理由关闭: 已核实或已撤销、虚假举报、证据不足或自定义理由。已关闭的举报会被添加到被举报用户的举报历史中。
- 备注与笔记本。 版主可以为举报添加备注,并且有一本笔记本存储每条举报的备注。点击笔记本中的坐标可以传送到该位置。每次使用笔记本时都会检查权限,如果用户已被授予笔记本权限,则不会执行任何操作。
- 被举报用户在举报时的位置 也包含在举报信息中。
- 防止滥用举报的工具。 禁止使用
/report命令的永久封禁和临时禁言,并记录谁发出了什么处罚。 - 可疑视图。 使用
/suspicious显示拥有三个或以上未关闭举报的用户列表。可将列出为“可疑”所需的举报数量由用户设定。仅生成列表,不提供其他额外信息。 - 工作人员警报 在聊天中显示(也可设置为全宽或小写字母)。网络警报包括警报来源的服务器。
- 受保护用户 可被豁免。只有拥有
reportsystem.moderate.staffreports权限的版主才能查看工作人员举报。 - 原生菜单。 可在 Paper 1.21.7+ 和 Spigot 1.21.6+ 上使用 Minecraft 自带的表单屏幕来使用 /report。工作人员菜单也可以使用,但不推荐。
- Mojang 聊天举报 是可选的。举报界面上的按钮会告知工作人员是否可以以及如何向 Mojang 举报玩家的聊天内容。
- 自定义布局。 高级用户可以通过 YAML 文件创建自定义布局。更改、隐藏或移动菜单项,添加玩家头颅、带有自定义数据的任意物品、更改表单屏幕等。
附加信息
- 它不是反作弊工具。
/suspicious仅跟踪未关闭的举报,不进行重新登录检测或 IP 匹配。 - 方块破坏限制和超时仅适用于
/report,封禁和静音由你的惩罚插件执行。 - 无法将分开的 SQLite 数据库合并到网络列表中。请为此使用 MySQL。
- 选择器默认显示在线玩家。输入名称可以对任何曾经连接过的玩家生效。设置
show-offline-players: true以同时显示曾经连接过的离线玩家。 - 网络使用不需要 Redis。如果不使用 Redis,其他服务器上的工作人员需要手动刷新页面才能看到新举报,而不是实时接收。
详情
Commands
| 命令 | 功能 |
|---|---|
/report |
打开举报菜单 |
/report player <player> <reason> [notes] |
从聊天窗口举报玩家 |
/report staff <staff> <reason> <details> |
从聊天窗口举报工作人员 |
/report bug <reason> <details> |
从聊天窗口举报漏洞 |
/reports |
查看工作人员的举报队列 |
/suspicious |
显示举报数超过可疑阈值的玩家 |
/rs alert |
切换你自己的警报通知 |
/rs report, /rs reports, /rs suspicious |
快捷命令 |
/rs doctor |
执行健康检查 |
/rs debug confirm |
支持对 plugins/ReportSystem/debug-reports/ 中的脱敏报告进行调试确认 |
/rsreload |
重新加载配置 |
/rsproxy status|reload|doctor|debug confirm |
支持 BungeeCord 或 Velocity |
可通过单个单词(例如 cheating_hacking、griefing)或数字补全原因。Sponge 特有:使用 close、priority、lowpriority 和 note 的 /report <player> <reason>、/reports、/suspicious、/rs 以及 /rsreload
权限
| 节点 | 涵盖范围 | 默认值 |
|---|---|---|
reportsystem.report |
使用 /report 的权限 |
所有人 |
reportsystem.report.staff |
/report 中的工作人员标签页 |
所有人 |
reportsystem.moderate |
所有管理命令及举报队列 | op |
reportsystem.moderate.close, .priority, .notes, .notebook, .staffreports |
上述命令的子命令 | op |
reportsystem.suspicious |
可疑玩家视图 | op |
reportsystem.advanced, .advanced.timeout, .advanced.block |
超时、封禁及用户管理 | op |
reportsystem.alerts |
启用接收举报警报 | op |
reportsystem.staff |
若未使用 LuckPerms,则在选择器中被视为工作人员 | op |
reportsystem.report.exempt |
不可被举报 | 无人 |
reportsystem.punishment.exempt |
不会被超时或封禁 | 无人 |
reportsystem.reload, .doctor, .debug, .updates |
管理员权限 | op |
reportsystem.* |
所有权限 | op |
网络配置示例
multi-platform:
instance-name: "Survival-1" # 每个服务器唯一
platform: auto
database:
type: mysql
mysql:
host: "127.0.0.1"
port: 3306
database: "reportsystem"
username: "reportsystem"
password: "change-me"
pool-size: 5
ssl-mode: PREFERRED # 如果 MySQL 位于另一台机器上,则必须为 REQUIRED 或 VERIFY_CA
redis:
enabled: true
host: "127.0.0.1"
port: 6379
password: ""
ssl: false # 如果 Redis 位于另一台机器上,则为 true
channel: "reportsystem-sync"
开发者 API
if (ReportAPI.openReportsAgainst(player) > 0) {
return; // 工作人员已经在查看该玩家
}
if (ReportAPI.isClaimed(reportId)) {
continue; // 已有工作人员接手此举报
}
所有方法均为空安全(null safe),若 ReportSystem 未安装,将返回 false 或 0。举报数量已被缓存,因此可在主线程中安全调用。事件:ReportCreateEvent(可取消)、ReportClaimEvent、ReportCloseEvent 和 ReportAppealEvent。
Suggestions, bug reports or questions? Please use the plugin feedback form.
ReportSystem
Reports by players via menu with staff viewing from their own side and a copy in Discord.
A player will type /report and select a target and a cause then submit the report. Staff will receive an immediate in-chat notification of the report and will process the reports via the /reports menu. Reports can also be automatically sent to a Discord channel. ReportSystem does not include auto-take action or anti-cheat.
Overview
- A player menu to report. Select a target, select a reason from a list, add additional information and an optional Discord contact. Or you can also type the report in full:
/report player Steve griefing broke my base - A staff report queue with sorting, filtering, priorities, notes and the ability to close the report with a closing note
- Three types of reports: player, staff (private) and bug
- Reports appear as Discord embeds, one per report with a colour indicating the status
- Supports multiple networks. Uses a single shared report list in a single MySQL database. Uses Redis for real-time global notifications.
Features
- Queue. Filter by offense or type, sort by oldest, newest or priority, page through the queue, refresh the page and view a specific user's report history.
- Priority can be normal, high or low or auto assigned based on the rank of the user that made the report.
- Close with reason: verified or struck out, false report, insufficient evidence or a custom reason. Closed reports are added to the reported user's report history.
- Notes and note book. Moderators can add notes to reports and there is a book that stores a note of each report. By clicking the coordinates in the book you can be teleported to that location. The permission is checked each time you use the book and if the user has been given the book it will do nothing.
- The location of the reported user at the time the report was made is also included in the report.
- Tools to combat report abuse. Permanent bans and timeouts from using the
/reportcommand with a record of who issued what. - Suspicious view. Using
/suspiciousa list of users with three or more open reports is displayed. The number of reports to list as suspicious can be set by the user. Only a list is generated and not any additional information. - Staff alerts in chat (can also be in full width or in small caps). Network alerts include the server the alert originated from.
- Protected users can be exempted. Staff reports are only viewable by moderators with the permission
reportsystem.moderate.staffreports - Vanilla menus can be used that makes /report use Minecraft's own form screens on Paper 1.21.7+ and Spigot 1.21.6+. Staff menus can too, but not recommended.
- Mojang chat reports are optional. A button on reports shows staff whether a player's chat can be reported to Mojang, and how to do so.
- Custom layouts can be made with YAML files for more experienced users. Change, hide or move menu items, add player heads, any item with custom data, change form screens, etc.
Extra Information
- It is not an anti cheat.
/suspiciousonly tracks open reports it does not do any rejoin detection or IP matching. - Blocks and timeouts only apply to
/report, bans and mutes are done by your punishment plugin - Split sqlite databases cannot be combined into a network list. Use MySQL for this.
- The picker by default shows online players. Entering a name will work for any player that has previously connected. Set
show-offline-players: trueto also show previously connected players. - Redis is not required for network usage. If Redis is not used, staff on other servers will need to manually refresh the page to see a new report instead of receiving it as it occurs.
Details
Commands
| Command | What it does |
|---|---|
/report |
Opens the report menu |
/report player <player> <reason> [notes] |
Reports a player from chat |
/report staff <staff> <reason> <details> |
Reports a staff member from chat |
/report bug <reason> <details> |
Reports a bug from chat |
/reports |
Reports queue for staff |
/suspicious |
Players with reports above the suspicious threshold |
/rs alert |
Toggles your own alerts |
/rs report, /rs reports, /rs suspicious |
Shortcuts |
/rs doctor |
Performs health checks |
/rs debug confirm |
Supports redacted reports in plugins/ReportSystem/debug-reports/ |
/rsreload |
Reloads the configuration |
/rsproxy status|reload|doctor|debug confirm |
Supports BungeeCord or Velocity |
Tab complete reasons by single word (e.g. cheating_hacking, griefing) and by number. Sponge specific: /report <player> <reason>, /reports with close, priority, lowpriority and note, /suspicious, /rs and /rsreload
Permissions
| Node | Covers | Default |
|---|---|---|
reportsystem.report |
Permissions for use of /report |
everyone |
reportsystem.report.staff |
Staff tab in /report |
everyone |
reportsystem.moderate |
All moderation commands and the reports queue | op |
reportsystem.moderate.close, .priority, .notes, .notebook, .staffreports |
Sub-commands of above | op |
reportsystem.suspicious |
Suspicious view | op |
reportsystem.advanced, .advanced.timeout, .advanced.block |
Timeouts, blocks and user management | op |
reportsystem.alerts |
Enables receiving of report alerts | op |
reportsystem.staff |
Treated as staff in the picker if LuckPerms isn't used | op |
reportsystem.report.exempt |
Cannot be reported | nobody |
reportsystem.punishment.exempt |
Cannot be timed out or blocked | nobody |
reportsystem.reload, .doctor, .debug, .updates |
Admin | op |
reportsystem.* |
All permissions | op |
Network config example
multi-platform:
instance-name: "Survival-1" # unique per server
platform: auto
database:
type: mysql
mysql:
host: "127.0.0.1"
port: 3306
database: "reportsystem"
username: "reportsystem"
password: "change-me"
pool-size: 5
ssl-mode: PREFERRED # REQUIRED or VERIFY_CA if MySQL is on another machine
redis:
enabled: true
host: "127.0.0.1"
port: 6379
password: ""
ssl: false # true if Redis is on another machine
channel: "reportsystem-sync"
Developer API
if (ReportAPI.openReportsAgainst(player) > 0) {
return; // staff are already looking at this player
}
if (ReportAPI.isClaimed(reportId)) {
continue; // someone on staff has it
}
All methods are null safe and will return false or 0 if ReportSystem is not installed. Report numbers are cached so can be safely called on the main thread. Events: ReportCreateEvent (cancelable), ReportClaimEvent, ReportCloseEvent, and ReportAppealEvent.
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 ReportSystem
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
v1.21.3 更新日志
- 修复了从举报菜单中取走物品的问题
- 聊天证据现在支持 ChatSystem
- 使用 /report 不再显示隐身状态的工作人员是否在线
- 修复了代理提醒问题
- 改进了所有语言的翻译
- 修复了一些错误
- 一些小的更新
v1.21.2 更新日志
- 更新了 18 种语言的翻译
- 未修改的语言文件现在可以自动更新
- 修复了与捆绑 Redis 或数据库库的插件的兼容性问题
- 默认时区自动设置为服务器的时区
- 员工交互菜单不再处于实验性阶段(if)
- 修复了一些 bug
- 一些次要更新
关于这个资源的讨论、问题反馈与使用心得
还没有讨论,来发第一帖吧
你是这个资源的作者?登录后可认领此资源。
相似资源
插件
PacketEvents 是一款专为 Minecraft Java 版打造的协议库,旨在简化数据包的处理与传输。
插件
ExyliaPlugins 的库。
插件
通过对话框或铁砧界面帮助你的 Anthme
插件
自定义你的Minecraft头像!
插件
重新定义服务器上的生物运输方式。使用高度可定制的口袋道具,安全地捕获、存储和释放任何实体。
插件
为基于 Spigot/Paper/Folia 的服务器添加对 Vivecraft 的支持
评论 0
登录后参与评分
还没有评论,来抢沙发吧