Player Reports, Appeals & Administrative Review

The report and appeal process exists to resolve rule violations fairly, correct mistakes, and protect the community—not to continue personal conflicts.

Active reports

Use when an issue is happening and a staff member must intervene. Keep the message factual and brief. Do not repeatedly submit the same report or demand a specific administrator.

When no immediate intervention is needed, finish the scene and use the forum or support system with complete evidence.

What to include

A useful report normally includes:

• The names of the involved players and characters.
• The date, approximate time, and location.
• A clear sequence of events.
• The specific rule concern.
• Full screenshots, video, or logs showing relevant context.
• Any attempts made to resolve a technical misunderstanding.

Evidence should be unedited except for reasonable privacy redaction. Cropping that removes important context may reduce its reliability.

Conduct during an investigation

Do not contact the reported player to threaten punishment, coordinate stories, pressure witnesses, or provoke additional evidence. Do not publish the report for community voting.

All participants must answer staff questions honestly. Deliberately false statements or fabricated evidence may lead to separate punishment.

Staff review

Staff should consider the full scene, not a single line in isolation. Prior history may affect the consequence but should not be used as proof that a new allegation occurred.

A staff member with a serious conflict of interest should transfer the case when another qualified reviewer is available.

Appeals

An appeal should identify a factual error, missing evidence, procedural problem, disproportionate consequence, or meaningful new information. Repeating “I disagree” without addressing the decision is not enough.

Appeals must remain respectful and may be limited after a final review. Contacting multiple staff members, creating alternate accounts, or moving the argument into public channels does not create another appeal.

Refund requests

Refunds require evidence that a confirmed technical problem or rule violation directly caused the loss. Provide the approximate value, item details, time, and proof of prior ownership.

Staff may deny speculative requests, duplicated claims, losses caused by ordinary roleplay, or claims submitted too late to verify.

Staff complaints

Complaints about staff conduct should be submitted privately to the appropriate management level with evidence. Staff status does not shield a member from review, but disagreement with an unfavorable ruling is not automatically misconduct.

Finality

Management may close a case when the evidence has been reviewed and available appeal steps are complete. Continuing to relitigate a final decision through unrelated tickets, public threads, or third parties may result in platform restrictions.