KrispyXI support keeps Website, Discord, and in-game reports under one ticket ID. Each ticket shows its source, issue type, player and character, assigned GM, status, creation time, last update, and staff reply history.
During the current local/LAN Alpha, the dashboard form and Discord intake may still be shown as previews. Do not treat a disabled form as a submitted request. Until the secure connector is enabled, use the Alpha contact route given directly by staff.
Choose the closest issue type
Choosing the right tab places the request in the correct staff queue:
| Issue type | Use it for |
|---|---|
| Character recovery or stuck | Invalid position, battlefield state, home-point return, or hub recovery |
| Account, login, or 2FA | KrispyXI account access; never include a password or Square Enix credentials |
| Mission or quest progression | Cutscene, objective, mission, quest, or progression flag |
| Auction house or economy | Listings, proceeds, delivery, gil, or economy records |
| Item, equipment, or inventory | Missing/incorrect items, equipment, wardrobes, storage, or inventory |
| Custom content or encounter | Expedition, League, Dungeon, Apex, Chronicle, crafting, or other original KrispyXI systems |
| Crash, disconnect, or technical issue | Client error, crash, disconnect, patching, or connection behavior |
| Website or launcher | Dashboard, Wiki, download flow, or KrispyXI Launcher |
| Discord or community access | Discord linking, roles, channels, or community access |
| Player conduct report | Harassment, chat, blocking, or player behavior |
| Exploit or security report | Duplication, exploit, or security concern; keep details private |
| Other | No closer category applies |
Ticket statuses
| Color | Status | What it means |
|---|---|---|
| Green | Open | The report was received and is waiting for staff triage. |
| Blue | In progress | An assigned GM is actively working on it. |
| Orange | Escalated investigation | The first safe action did not resolve it, or deeper logs/state review is required. |
| Red | Closed | Work is complete and the outcome is recorded. |
The dashboard should update the assigned GM and timestamp whenever work changes. A closed ticket remains readable so the player and staff can review the result without opening duplicate requests.
What to include
- player name and affected character;
- the closest issue type;
- a short, specific subject;
- zone, mission, quest, encounter, item, or website page involved;
- approximate date, time, and time zone;
- what you expected;
- what actually happened;
- exact steps that reproduce it; and
- a redacted screenshot or short log excerpt when useful.
For a crash or disconnect, say whether it happened once or repeats. For inventory/economy issues, leave the affected item or listing unchanged when possible. For a stuck character, say which safe-return action was already attempted.
Keep private information out
Never place passwords, one-time codes, recovery keys, IP addresses, database exports, private server addresses, Discord bot tokens, or Square Enix credentials in a ticket. KrispyXI staff do not need your Square Enix password.
Exploit and security reports should be visible only to authorized senior staff. Do not reproduce a duplication or exploit on another player's account, in public chat, or in a public Discord channel.
How staff handle a request
- The system creates one ticket and records its source and timestamp.
- Staff confirm the category, urgency, player, and affected character.
- A GM claims the ticket; it moves to blue In progress.
- If the first safe action cannot resolve it, the ticket moves to orange Escalated investigation with a reason.
- Staff record replies and actions in the same history.
- The ticket moves to red Closed only when the outcome is recorded.
Do not open the same issue through Website, Discord, and in-game support. If you already have a ticket ID, reply to that ticket so its timeline stays complete.