CoreCaseX
CoreCaseX 是一款仅适用于 Paper 的服务端案件管理插件。它为玩家提供了一种引导式的流程来开启支持工单、报告问题、提供上下文信息并回复工作人员;同时为工作人员提供了游戏内的完整工作流,包括分类、分配、回复、备注、结案以及 Discord 通知等功能。
目标很简单:让服务器客服工作井井有条,无需强制工作人员通过聊天记录回溯、截图、Discord 私聊或零散的工单笔记来管理一切。
本页面为商业风格的特性概览。具体的配置键名、默认值、限制及操作细节请参阅
CoreCaseX 的功能
- 添加结构化的玩家支持工单。
- 内置五种工单类型:支持请求、玩家举报、错误报告、丢失物品、破坏/盗窃报告。
- 使用物品栏 GUI 作为主要游戏内界面。
- 使用 Paper Dialogs 进行文本输入,如描述、回复、备注和结案说明。
- 为玩家提供工单列表、工单详情查看及回复流程。
- 为工作人员提供带有筛选功能、分页列表和详细工单板块的工单看板。
- 支持认领、分配/重新分配、优先级更改、状态更改、内部备注、工作人员回复、信息请求、结案、拒绝、归档和传送等操作。
- 将工单历史、回复、备注、证据、结案记录和事件时间线存储在 SQLite 中。
- 支持证据可见性规则,分为玩家可见、仅限工作人员和敏感证据。
- 支持游戏内工作人员通知和可选的 Discord Webhook 通知。
- 包含可配置的工单类型、消息、物品栏菜单文本、Dialog 输入文本、权限和存储设置。
统计数据

使用方法
将 jar 文件安装到 Paper 服务器上,启动服务器,CoreCaseX 将自动生成其默认配置文件。
玩家使用 /case 打开主菜单,创建工单,查看自己的工单,并在工作人员需要更多信息时进行回复。
工作人员使用 /case board 或工作人员工具菜单浏览工单、认领或分配任务、检查证据、添加备注、回复玩家、请求更多信息、结案或拒绝工单,并归档已完成的工单。
工单类型
CoreCaseX 附带五种专注的工作流:
- Support Request:用于一般帮助请求。
- Player Report:用于举报其他玩家,需说明理由和描述。
- Bug Report:用于技术或游戏玩法问题。
- Lost Items:用于物品丢失、死亡相关问题或恢复请求。
- Grief / Theft:用于基于地点的事件、可疑编辑、恶意破坏或盗窃。
每种工单类型均可启用或禁用,并可拥有各自的默认优先级和位置收集行为。
工作人员工作流
CoreCaseX 的设计围绕真实的工作人员工作流,而非一次性报告。
工作人员可按所有未关闭、未分配、分配给我、高优先级/紧急、等待玩家、等待工作人员、最近关闭或已归档等条件筛选工单。
工单详情分为可读的部分:概览、描述、证据、对话、内部备注和结案信息。工作人员的操作受权限控制,且在应用工作流更改前会重新进行检查。
Discord 与通知
CoreCaseX 包含可选的 Discord Webhook 输出,用于重要工单事件。
支持的事件包括:工单创建、紧急工单、认领、分配、状态更改、优先级更改、玩家回复、信息请求、工作人员回复、结案和拒绝。
Discord 投递尽最大努力完成:无效的 Webhook URL、发送失败和非 2xx 响应会被记录,但不会阻塞实际的工单工作流。
当前状态
CoreCaseX 目前:
- 支持 Paper 1.21.11 及以上版本
- 需要 Java 21 或更高版本
- 作为独立的 Paper 插件运行
- 使用本地 SQLite 存储
- 不需要 MySQL
- 不需要 Vault
- 不需要 PlaceholderAPI
- 不需要 Web 仪表板
- 不需要 Discord 机器人
- 通过 Webhooks 保持 Discord 集成为可选功能
总结
CoreCaseX 专为那些希望玩家支持和工作人员管理工作结构化、可视化且可直接在游戏内管理的服务器而构建。
它是针对 Paper 服务器的专注型案件系统:玩家通过引导式菜单提交问题,工作人员通过工作人员看板处理它们,完整的历史记录始终附加在工单上,而不会消失在聊天或 Discord 中。
也可以试试
CoreCaseX
CoreCaseX is a Paper-only staff case management plugin for Minecraft servers. It gives players a guided way to open support cases, report issues, provide context, and reply to staff, while giving staff an in-game workflow for triage, assignment, replies, notes, resolutions, and Discord notifications.
The goal is simple: server support should feel organized without forcing staff to manage everything through chat scrollback, screenshots, Discord DMs, or scattered ticket notes.
This page is a commercial-style feature overview. Exact config keys, defaults, limits, and operational details are documented at
What CoreCaseX Does
- Adds structured player support cases.
- Includes five built-in case types: support requests, player reports, bug reports, lost items, and grief/theft reports.
- Uses inventory GUIs as the main in-game interface.
- Uses Paper Dialogs for typed input such as descriptions, replies, notes, and resolution text.
- Gives players a case list, case detail views, and reply flow.
- Gives staff a case board with filters, paginated lists, and detailed case sections.
- Supports claim, assign/reassign, priority changes, status changes, internal notes, staff replies, info requests, resolve, reject, archive, and teleport actions.
- Stores case history, replies, notes, evidence, resolutions, and timeline events in SQLite.
- Supports evidence visibility rules for player-visible, staff-only, and sensitive evidence.
- Supports in-game staff notifications and optional Discord webhook notifications.
- Includes configurable case types, messages, inventory menu text, Dialog input text, permissions, and storage settings.
Stats

How To Use
Install the jar on a Paper server, start the server, and let CoreCaseX generate its default files.
Players use /case to open the main menu, create a case, view their own cases, and reply when staff need more information.
Staff use /case board or the staff tools menu to browse cases, claim or assign work, inspect evidence, add notes, reply to players, request more information, resolve or reject cases, and archive finished cases.
Case Types
CoreCaseX ships with five focused workflows:
- Support Request for general help.
- Player Report for reporting another player with a reason and description.
- Bug Report for technical or gameplay issues.
- Lost Items for missing items, death issues, or recovery requests.
- Grief / Theft for location-based incidents, suspicious edits, griefing, or theft.
Each case type can be enabled or disabled and can have its own default priority and location collection behavior.
Staff Workflow
CoreCaseX is designed around a real staff workflow instead of one-off reports.
Staff can filter cases by all open, unassigned, assigned to me, high/urgent, waiting player, waiting staff, recent closed, or archived.
Case details are split into readable sections for overview, description, evidence, conversation, internal notes, and resolution information. Staff actions are permission-controlled and rechecked before workflow changes are applied.
Discord And Notifications
CoreCaseX includes optional Discord webhook output for important case events.
Supported events include case creation, urgent cases, claim, assignment, status changes, priority changes, player replies, info requests, staff replies, resolution, and rejection.
Discord delivery is best-effort: invalid webhook URLs, send failures, and non-2xx responses are logged without blocking the actual case workflow.
Current State
CoreCaseX currently:
- supports Paper 1.21.11 and above
- requires Java 21 or newer
- works as a standalone Paper plugin
- uses local SQLite storage
- does not require MySQL
- does not require Vault
- does not require PlaceholderAPI
- does not require a web dashboard
- does not require a Discord bot
- keeps Discord integration optional through webhooks
Summary
CoreCaseX is built for servers that want player support and staff moderation work to be structured, visible, and manageable directly in-game.
It is a focused case system for Paper servers: players submit issues through guided menus, staff handle them through a staff board, and the full history stays attached to the case instead of getting lost in chat or Discord.
Also try
评论 0
登录后参与评分
还没有评论,来抢沙发吧