Support and contact
Support and contact
Before you write#
Most problems can be diagnosed in two minutes:
- Open the game in the Preview tool with the browser console open and
?sdk_debug=true. - Look for the first red error. Note its message.
- Search this documentation and the FAQ. Check the error code lists.
- Try the game in an incognito window with extensions off, in a second browser.
What to include#
A request with these details is answered fastest:
- The game name and the build version or upload time.
- A preview link, or the exported event log from the Preview tool.
- What you did, what you expected and what happened.
- The
codeandmessageof any SDK error, and theenvironment. - Browser, operating system and device.
- A screenshot or short screen recording.
- For payout questions: the period and the figure you expected.
Do not send passwords, API keys or tokens. If you pasted a token or leaderboard key by accident, tell us so we can rotate it.
Where to write#
Use the Support page in the developer console; it shows the developer support contact and what to include. Replies usually arrive within a working day.
Security reports#
If you find a security problem in the portal or the SDK, report it privately through the developer support contact on the console's Support page, and say in the first line that it is a security report. Please give us reasonable time to fix it before you disclose it.
What support cannot do#
Support does not debug your game code, but we will tell you what the portal sees. We do not provide tax advice. We cannot promote a game on request; see the introduction for how promotion works.