A bug report records a reproducible server, state, or interface fault for asynchronous review. This guide remains a draft while guided disclosure, duplicate handling, private evidence delivery, and real-client submission and tracking await final verification.
Use gameplay help for a question or blocked prerequisite, and use the urgent player-conduct route for a live issue involving another player. A bug report is not an emergency staff call and does not promise an immediate response.
Prepare a useful report
Before submitting, record:
- what you observed;
- what you expected instead;
- the shortest safe sequence that produced it;
- the affected character, item, vehicle, property, or other visible entity;
- the location and approximate time; and
- the exact final message or visible state.
Describe observations rather than guessing at an internal cause. Do not repeat a destructive action, expose another player’s private information, or create additional losses merely to collect evidence.
For an accessibility defect, include the supported client and version, resolution, relevant /accessibility values, exact command or surface, text shown, expected task, and whether a command or dialog alternative worked. Describe the barrier without naming or guessing a diagnosis.
Submit in game
Use /bug while authenticated and in character. The guided flow collects observed behavior, expected behavior, and safe reproduction steps. The direct form can submit a concise observation when the full guided draft is unnecessary.
Review the report before submission. Only a successful save creates a durable public BUG- reference. Keep that reference with any evidence you preserve.
A guided draft is temporary session state. You can reopen /bug to continue or delete the active draft, but disconnecting or changing character clears it. If saving fails and the game says the draft was retained, reopen it rather than starting over.
When a submission matches one of your recent reports, the response names that existing reference and keeps your draft, so you can reopen /bug to edit or delete it rather than retyping the report.
Track a submitted report
Use /bugstatus to list the account’s recent retained reports or open one of its current references. Public status can include a resolution, linked issue, or fixed release when available.
A submitted report is durable and does not depend on keeping the same game session open. Check its status before filing another report for the same fault. No guide can promise a response or fix time.
Internal notes, private diagnostic context, and another player’s reports are not part of the public status view.
Protect privacy and evidence
The server can retain a bounded point-in-time diagnostic snapshot. That context helps reproduce the observation but does not prove its cause.
Do not include passwords, login codes, private messages, unrelated personal information, or private organization communications. Screenshots and video are not collected automatically. Preserve them with the returned reference, but do not send them through an improvised public route; verified private evidence delivery remains a publication blocker.
If login, character selection, startup, or a crash prevents in-game commands, preserve the observation without exposing credentials or diagnostic files publicly and use only a privately confirmed community support route.
Recover from an unclear submission
- Stop if repeating the action could duplicate or destroy state.
- Check
/bugstatusfor a new reference before submitting again. - Reopen
/bugif the game explicitly retained the draft. - Preserve the exact result and approximate time if neither report nor draft is visible.
- Use
/helpfor current syntax rather than guessing actions.
For choosing among all player-help routes, see the draft Support and reporting guide during review. Account login codes and recovery evidence belong under Account security and recovery, never in a bug report.