Case Types
five guided flows
One case system, not scattered reports
Structured case management for Paper servers.
CoreCaseX gives players a guided way to report issues, ask for help, provide evidence, and reply to staff while your team manages every case from a focused in-game board.
- Paper 1.21.11+
- Java 21
- SQLite storage
- Discord webhooks
Staff Case Board Preview
case #128
Waiting Staff
Staff Board
filters and actions
Evidence
visibility rules
Open
Claimed
Resolved
SQLite
local case history
Core feature set
Everything staff need to handle player issues in one workflow.
CoreCaseX keeps submissions, triage, evidence, player replies, internal notes, status changes, and final outcomes connected inside one Paper plugin.
Guided Player Submissions
Players use the `/case` Dialog flow to create support requests, reports, bug reports, lost item or death issue cases, and grief or theft cases without learning a large command tree.
Staff Board Filters
Staff can review all open cases, unassigned cases, cases assigned to them, high and urgent cases, waiting-player cases, waiting-staff cases, recent closed cases, and archived cases.
Claim, Assign / Reassign, and Act
Staff can claim cases, assign or reassign online staff, change priority, change status, add notes, reply to players, request more information, resolve, reject, teleport, and archive.
Evidence Visibility
Evidence can include reporter context, locations, target player snapshots when available, death details, manual location text, and case-specific options with player-visible, staff-only, or sensitive access levels.
Timeline History
Case creation, claims, assignment changes, status changes, priority changes, replies, notes, information requests, resolutions, rejections, and archive actions become an audit trail.
Player Case List
Players can view their own cases, inspect status and priority, read staff replies, and add replies while the case is still open.
Internal Staff Notes
Staff-only notes keep moderation context, observations, handoff details, and evidence interpretation away from player-visible conversation.
Discord Webhooks
Optional Discord output can route events by priority, case type, or default webhook, with safe JSON escaping and disabled allowed mentions.
SQLite Persistence
Cases, timeline events, replies, internal notes, resolutions, evidence, migrations, and common query indexes are stored locally.
Safe Dialog Actions
Clickable Dialog rows use short owner-bound tokens with permission checks, one-use successful callbacks, expiration checks, and stale cleanup.
Granular Permissions
Player, staff, and admin permissions let server owners decide who can view, claim, assign, archive, teleport, or inspect sensitive evidence.
Why CoreCaseX
Support work should be visible, owned, and traceable.
CoreCaseX is built for servers where staff need more than chat messages, screenshots, and scattered reminders. Each case has state, ownership, evidence, conversation, and history.
Players Submit a Guided Case
The Dialog UI collects the right information for the chosen case type, including descriptions, configured options, optional location context, and case-specific evidence.
Staff Triage from the Board
Staff use board filters, claim and assign/reassign flows, priorities, statuses, notes, replies, and information requests to decide what needs attention next.
Cases Close with a Clear Outcome
Resolved and rejected cases keep their final message and full timeline, then can be archived when staff are ready to move them out of active work.
Setup and compatibility
A focused Paper MVP with practical server-owner controls.
CoreCaseX targets Paper servers today. The configuration files are commented, reloadable where safe, and designed around real staff workflows rather than a generic form builder.
Runtime
Paper 1.21.11+ and Java 21
CoreCaseX uses modern Paper Dialog APIs and disables itself gracefully when the required runtime support is not available.
- Native Paper Dialog menus and forms
- Commands for players, staff, and admins
- Maven Wrapper build workflow
Configuration
Commented YAML Files
Server owners can adjust global limits, case type defaults, Discord event routing, visible text, and the SQLite file path.
config.ymlfor limits and staff notificationscase-types.ymlfor enabled flows and prioritiesmessages.ymlfor commands and Dialog text
Paper only
Java 21
SQLite included
Discord optional
Resources
Docs for owners who want exact behavior, not guesses.
Hub
Documentation Hub
Start from the structured documentation hub for overview, setup, configuration, FAQ, and operations.
ProductProduct Overview
Review CoreCaseX features, workflows, case types, staff tools, storage, notifications, and verified state.
ConfigConfiguration Reference
Read the owner-facing guide for config files, reload rules, permissions, commands, and troubleshooting.
FAQ preview
Short answers before installation.
These answers summarize the current MVP. Use the configuration reference when you need exact keys, permission nodes, command formats, and operational notes.
What is CoreCaseX?
CoreCaseX is a structured staff case management plugin for Paper servers. It helps players submit issues and helps staff triage, discuss, resolve, reject, and archive those cases in-game.
What case types are included?
Support request, player report, bug report, lost items or death issue, and grief or theft are included in the current MVP.
Does it require an external database?
No. CoreCaseX stores its current MVP data in a local SQLite database under the plugin data folder.
Can Discord notifications be disabled?
Yes. Discord webhook output is disabled by default and only runs when the server owner configures it.
Can staff permissions be separated?
Yes. CoreCaseX has separate permissions for board access, view, claim, assign/reassign, notes, replies, information requests, priority, status, resolution, archive, teleport, and evidence access.
Also try
More CoreX plugins for the same server stack.
Each project stays focused, so you can add only the systems your Paper server actually needs.
Armor
CoreArmorX
Vanilla+ armor upgrade paths, netherite skins, metadata-safe conversions, and YAML control.
Tools
CoreToolsX
Vanilla+ tool upgrade paths, material skins, protected crafting, and admin-controlled recipes.
Chat
CoreChatX
Channels, private messages, pings, ChatItems, moderation, bridges, locales, and Velocity support.
Extraction
CoreExtractionX
YAML-driven block extraction, block replacement, natural drops, and configurable extra item drops.
Ready to organize server support?
One case workflow for players, staff, evidence, and outcomes.
Replace scattered follow-up with a focused Paper workflow that keeps every support case visible, assigned, documented, and ready for a final decision.