Ticket system

The ticket system is the primary way to request staff members for a particular reason, id est, to resolve an issue, to request authorisation, and whatnot.

Opening tickets

1. Join the RetroMC Discord guild.
2. Head to #helpdesk, and select the category of ticket you wish to open.
3. Input your Minecraft username and the reason you're opening a ticket.
4. Go to the ticket thread that Atlas Utilities just created, and post details about your issue.
   • Staff members will respond within from a few hours to 1 day (Timezones play a factor), so please be patient and don't ping them.

• 
• 
• 

  Links are available at the main page.

• 

  Ticket metadata that is sent to the ticker creator when it's closed.

Reviewing tickets

In #helpdesk, tickets are stored as threads, so you can view closed tickets by opening the threads list.

Desktop	Mobile (Android is used here)
At the header, where the channel name is displayed.

Ticket commands

• !close <time> <reason> - Closes the ticket after time with reason.
  • Atlas will DM the user who created the ticket with metadata about the ticket.
• !add <user-ID-or-username-or-mention> - Adds a user into a ticket.
• !betaevo - Gives information about BetaEvolutions.
• !transfer - Sends a link to the account transfer form.

Cases for creating tickets

This is a non-exhaustive list of cases for ticket creation.

General Issue	Report Player	Login Trouble
Account transfers (if UUID-based transfer fails) Requests for authorisation for specific actions (Moving a player's build in a village.) Clarifications on various things (JVillage for example)	Reporting instances of griefs. Reporting someone on RMC that disrespects others, attempts to ruin others' experience, and/or expresses bigotry in some way.	Assistance for linking MC account on the Discord guild. Resolving account-per-IP limits. BetaEvolutions bypasses this. Resetting wiki account passwords. Note: Players are responsible for the security of their Microsoft/Mojang and/or wiki accounts.