FAQ

Answers for server owners before setup.

Short, practical answers based on the current CoreCaseX MVP documentation.

Questions

Common setup and operation notes.

Use the configuration reference for exact keys, commands, permissions, and troubleshooting checks.

What is CoreCaseX?

A structured staff case management plugin for Paper servers. It gives players guided case submission and gives staff an in-game workflow for triage, assignment changes, replies, notes, evidence, status changes, and final outcomes.

What server runtime does it support?

The current MVP supports Paper 1.21.11 or newer with Java 21.

Does it need a separate database?

No. CoreCaseX uses local SQLite storage in the current MVP.

Which case types are included?

Support request, player report, bug report, lost items or death issue, and grief or theft.

Can case types be configured?

Yes. Built-in case types can be enabled or disabled, given default priorities, and configured for location collection. Player report reasons and bug report categories are configurable.

Can players see their own cases?

Yes. Players can list their own cases, inspect status and priority, read staff replies, and add replies while the case remains open.

Can staff reassign cases?

Yes. The MVP uses /case assign for assign and reassign. The target staff member must be online, assignment changes are written to the timeline, and resolved, rejected, or archived cases reject assignment.

Are internal staff notes visible to players?

No. Internal notes are staff-only and separate from player-visible replies.

How does evidence visibility work?

Evidence can be player-visible, staff-only, or sensitive. Staff-only and sensitive evidence require dedicated permissions.

Does Discord support block case workflows?

No. Discord webhooks are optional and best-effort. Invalid URLs, send failures, and non-2xx responses are logged without failing case actions.

What can `/case reload` reload?

It reloads config values into memory and logs validation warnings. Replacing the jar, changing Paper runtime, regenerating deleted defaults, or changing an already-open SQLite path requires restart or careful handling.