control.ROLEPLAY
All news
1 min read

A little context goes a long way.

The details that help turn a support request into a useful conversation.

Start with what you expected

A useful report explains the action you took and the result you expected. That gives the team a clear starting point before they look through logs or ask for more context.

Include the details that matter

  1. Describe where you were and what you were doing.
  2. Record the approximate time and time zone.
  3. Copy the exact error message, if there was one.
  4. Explain whether the problem happened once or repeatedly.

Avoid guessing at a cause. A clear description of what you observed is more useful than a confident explanation without evidence.

Share evidence thoughtfully

Screenshots or clips can help, but remove unrelated private information first. Never include a password, linking code, authentication code, or private appeal token.

Keep related information in one conversation so the team can follow the whole sequence.

Use the right channel

Send technical and account questions through Support. Moderation review requests belong in the appeal form, where the relevant context can be reviewed privately.

Ready for your next chapter?

Find practical advice in the player handbook.

Explore guides