Report a problem clearly

A small amount of precise context is more useful than a screenshot full of secrets.

Include

• The environment and approximate time, including timezone.
• The world or screen and the action you attempted.
• What you expected and what actually happened.
• Steps that reproduce the issue, if known.
• The error code and trace ID, if shown.
• A screenshot with private information removed.

Leave out

Passwords, mnemonics, private keys, session tokens, callback credentials and private account data. A public Problem message is intended for sharing; raw diagnostic logs can contain information that is not.

Use the reporting channel offered by the game or project. For technical investigation, the error reference explains how codes and transport relate.