Review & publishing
Automatic checks followed by a manual super-admin decision.
On this page
Status pipeline
Draft → Checking → Ready for review → Live. Hard-check failures return the version to Draft. Staff can request changes or reject it with notes. A super-admin approval publishes the complete game page and catalogue entry; no separate developer publish button is needed. A game can be Hidden by staff. For live games with pending updates, the game remains Live while the current version has its own Draft/Checking/Ready for review status.
Checks and manual review
Checks cover metadata, all artwork sizes, SDK references, known tracker/ad references, ZIP structure or HTTPS/embedding behavior, and an English heuristic. Hard failures block approval; warnings require manual attention. Static scans and header checks are limited evidence. Staff test gameplay, controls, dependencies and safety.
Notes and timing
Review timelines are not guaranteed. Track notes and the timestamped history on your game page. Versions under checking or review are locked against edits. After a request for changes or rejection, address the feedback, save details and rerun checks. Use Support for questions and include the game ID. No audience size, placement, acceptance or income is promised.