Tickets & Reports

Minecraft Country uses a custom system called CaseCraft for tickets and reports. Tickets are for back-and-forth conversations with staff. If you have a question, need help with something, or have an issue staff may need to follow up on with you, a ticket is usually the right choice.

  • Create a Ticket – The preferred command is /ticket create <your message>. The older /ticket submit <your message> command still works as an alias.

  • View Tickets In-Game – Use /ticket list to see your tickets. The top of the list includes quick actions for a new ticket and the web portal. Ticket rows also have clearer buttons: [Open] opens the ticket in-game, and [Web View] opens it in your browser.

  • Read Ticket Conversations – Use /ticket read <ticket id> to read a ticket in-game. Ticket pages show the newest messages first by default, with clearer page labels like newest and oldest.

  • Use the Web Portal – Use /ticket login or /ticket weblogin to open the ticket web portal. From there, you can read the full conversation and reply from your browser. The web ticket list shows unread/new reply badges, high priority tickets, player avatars, online status, and last-seen info.

  • Resolved and Closed Tickets – You can view resolved tickets in the web portal for history, but resolved tickets cannot be replied to. Ticket submitters can close their own ticket from the web portal, but they must enter a reason. Participants can reply and view the ticket, but cannot close it.

  • Creating Tickets From the Web – The web portal has a new ticket option too, but you must be online in-game when submitting so CaseCraft can collect the normal player information attached to tickets.

Report System

Reports are different from tickets. A report is a one-way alert to staff, meant for situations where staff should know about or review something, but where you do not necessarily need a conversation. Reports automatically include useful information for administrators, like your world, coordinates, and other context depending on the report type.

If staff need to ask follow-up questions, they may occasionally convert a player report into a ticket. If you already know you need a back-and-forth conversation, use the ticket system instead.

You can submit a few different types of reports in-game:

  • Bug Reports – Sends a bug report message to administrators that includes pertinent information like your world, coordinates, and a custom message explaining what’s going on.

    Usage: /report bug <your message>

  • Build Reports – Sends a build report message to administrators that includes pertinent information like your world, coordinates, and a custom message explaining what’s going on.

    Usage: /report build <your message>

  • Lag Reports – Sends a lag report message to administrators that includes pertinent information like your world, coordinates, your ping, the server TPS, the server MSPT, server CPU usage, total server mobs, total server chunks, entities near you, and a custom message explaining what’s going on.

    Usage: /report lag <your message>

  • Player Reports – Sends a player report message to administrators that includes the player you define when sending the command, and a custom message to explain why you’re reporting them.

    Usage: /report player <playername> <your message>

  • Claim Reports – Sends a claim report message to administrators that includes pertinent information like your world, coordinates, and a custom message explaining the claim issue.

    Usage: /report claim <your message>

  • Miscellaneous Reports – Sends a misc. report message to administrators that includes pertinent information like your world, coordinates, and a custom message explaining what’s going on.

    Usage: /report misc <your message>

  • COOLDOWN: There is a 60-second cooldown on reports currently, but as more players join the server – this may be extended to a longer period to prevent report flooding to the administrators in the discord.

Leave A Comment