Getting Help

A good support request lets another person see the same problem without guessing. Focus on observable behavior, not every experiment you have already tried.

Use this path for normal account, product, or building help. For harmful content or behavior, use Safety and Reporting instead.

Include these details

1. What you are building — one sentence about the player goal.
2. Where it happens — the game name and the item, task, or setting involved.
3. Steps to reproduce — the fewest player actions that reveal the problem.
4. Expected result — what should happen.
5. Actual result — what happens instead.
6. What you already checked — one or two relevant checks, not a long list of unrelated changes.
7. Player impact — whether players are blocked, confused, or only seeing a visual issue.

Copy this outline

Goal:
I am trying to...

Where:
Game: ...
Item or task: ...

Steps:
1. ...
2. ...
3. ...

Expected:
...

Actual:
...

What I checked:
...

Add useful evidence

• A short video of the player path.
• A screenshot of the selected item or task configuration.
• The exact name of a spawn point, value, or leaderboard label involved.
• Whether the behavior changes after you start from the intended player spawn.

Send the request to the right place

Start with the Help Center for self-service answers. For questions it does not cover, account access, or a product issue that needs support, use the current details on the Contact page.

Keep private details private

Remove personal information, private links, and connection details before sending a request. Share only the information needed to reproduce the behavior.

For self-service checks, begin at Help and Reference.