Automated checks
Every upload is checked before it can be reviewed:
| Check | Fails when |
|---|---|
| Archive | Paths escape the archive, files are executables or nested archives, or limits are exceeded. |
| Malware scan | The scanner flags a file. |
| Browser load | The game contacts undeclared hosts, opens popups or uses excessive CPU in an isolated browser. |
| Dependencies | A managed server package has unpinned or vulnerable production dependencies (reported for review). |
Each finding explains what happened. Fix the build and upload a replacement; failed builds can't be submitted.
Staff review
Reviewers check the listing and the build: that the game runs, that the page describes it honestly, and that it follows the content guidelines. They approve it or request changes with a note. Address every note, test again and resubmit.
After approval
Test the public page as a player: on a free game, check that it loads on the page and plays; on a paid game, check the purchase box and the player page. A new build later goes through checks and review again before it replaces the live release.