Publishing and review

How to package a build, how versions move through review, and what gets a game rejected.

Create a game

In your dashboard, create a game with a name, an engine (html5, threejs, unity, cocos or other), an orientation (portrait or landscape), a category and a description. You can have up to 20 games. You only ever see your own games.

You get an app id (d plus 14 hex characters) and a server secret. The secret is shown once. GOOF keeps only a hash of it, so it cannot show it again.

Package rules

Upload either:

The zip must hold index.html at the root, or inside one single top folder. That folder is then removed, so build/index.html becomes index.html.

Versions

Each upload makes a new version. You can add notes to it. A version goes through these states:

StateMeaning
uploadedStored. You can test it.
in_reviewSubmitted. Only one version can be in review at a time.
approvedPassed review.
livePlayed on GOOF.
rejectedDid not pass. The reason is shown in your dashboard.

Your game itself is draft, in_review, live, rejected or suspended. You can delete a game only while it has never been live.

Test before you submit

Review

Every game is reviewed by a person before it goes live, and so is every new version. We check that it loads, plays, follows the ad rules and our policies.

What gets a game rejected