Help & Reference
When something in a game does not behave as expected, slow down and test one small piece at a time. The fastest fix usually starts with a clear description of what the player did, what you expected, and what actually happened.
Start with the player path
- Join from the intended spawn point.
- Repeat the exact player action that caused the problem.
- Check the item, task, or setting directly involved.
- Change one setting or one effect, then retest.
Do not rebuild the whole interaction before you know which part is failing.
Choose the right route
| If you need help with | Start here |
|---|---|
| A task, trigger, or effect | Interactive Studio |
| A custom interface or script | Code & Custom UI |
| Player starts, portals, or scene layout | Build Your Game |
| Assets, Marketplace items, or AI Lab drafts | Assets and AI |
| A first build plan | First-game Checklist |
| External creator workflows | MCP and API Help |
| A player-facing community question | Play and Community |
| Harmful content or behavior | Safety and Reporting |
| Account, product, or support contact | Contact Portals |
Existing troubleshooting guides
Ask for help with useful context
For a normal building or product issue, include the game name, the shortest reproducible steps, what you expected, what happened, and whether the issue appears in the player experience. Screenshots or a short recording can make a confusing issue much easier to understand.
For a safety concern, use the reporting route instead of a normal support request. See Safety and Reporting.
See Getting Help for a ready-to-copy support outline.