Publishing your game
The listing, the review, the release — and what happens to a published game afterwards.
Publishing gives your game a public page anyone can play. Until you publish, the project is yours and your collaborators' only.
It is a store release, not a deploy button: you fill in a listing, submit a version for review, and then release it. That shape exists so a player arriving at your game finds a page that explains what it is, and so every release is a version you can point at.
Everything below lives in the project's Publish tool.
The listing
Required before you can submit:
| Field | Notes |
|---|---|
| Title | |
| Description | What the game is. Can be AI-drafted, then edited. |
| Category | One of: arcade, platformer, puzzle, shooter, RPG, adventure, simulation, strategy, racing, sports, casual, other. |
| Cover image | The wide promotional image on your game's page. Can be generated with AI (costs credits). |
| Logo | A square 1024×1024 icon — your game reduced to an icon, used where a wide cover would be unreadable (the loading splash, for one). Exactly 1024×1024; upload only, no generator yet. |
| At least one screenshot | Up to ten. |
| Age rating | Answer a short questionnaire; the rating is computed from your answers. |
| Target platforms | Desktop, touch, or both. |
Target platforms is a claim about playability, not marketing. Mobile feeds filter on it. A keyboard-only game declared as touch lands at the top of a phone feed and is unplayable there. Declare what your input actually supports — genre is not evidence.
Optional, and worth doing:
- Intro — a longer illustrated write-up shown on the play page under the short description. Images can be embedded. Nothing forces you to fill it in.
- Video — a gameplay clip.
- Links — your own site, socials.
- Translations — per-language title and description. See Languages.
The tool can draft copy for you: description, tagline, and release notes from your recent commits. Every draft is yours to edit before it saves — read them, they are a starting point and not always right.
Submitting and releasing
Complete the listing. If anything required is missing, submit tells you exactly which fields — nothing is saved half-way.
Submit for review. Pick how the version number moves — patch, minor or major — and optionally write release notes. The version is recorded immediately as in-review.
The automated content check runs. It looks at the game and the listing. This is not instant and you don't have to sit there; the notification bell tells you when it's done and links you back here.
You click Publish. The build runs, the bundle uploads, and the approved version is stamped live. Review happens before publishing, so nothing goes public that hasn't passed.
Every release is kept: a version list with its number, release notes and date. Players always play the current release — there is no per-version URL.
Updating a published game
Any agent turn, any explicit save, any push from your machine creates a new commit, and the project is then marked as having unpublished changes. Those changes are not live until you go through Submit → Publish again.
That separation is the point. You can keep building on a published game without the next broken experiment reaching your players.
What your players see
A published game lives at <AppDomain />/play/{gameId}, and anyone with the
link can play it — no account needed, unless your game
declares AI.
On that page: the cover and screenshots, your description and intro, the
developer (you), comments and replies, likes and favourites, sharing, and —
if anyone has forked it — the games made from yours. Fullscreen play is
<AppDomain />/play/{gameId}/fullscreen, which is also what the share button
copies.
On a phone, a landscape game rotates to fill the screen. On desktop it is letterboxed to its own aspect ratio.
Embedding
Point an iframe at the fullscreen URL:
<iframe
src="https://umicat.ai/play/{gameId}/fullscreen"
width="800"
height="600"
allowfullscreen
></iframe>Replace {gameId} with your game's id. The embedded player adapts to the
size you give it.
Discovery and tags
Published games appear in the site's game feeds. Category is the fixed
taxonomy above; tags are yours — up to ten freeform ones that drive the
browse-by-tag shelves and <AppDomain />/tags/{tag} pages.
Pick three to eight tags that are actually true: genre, visual style, mechanics, length. Tags are a shared key across the whole platform, so irrelevant ones are a moderation matter, and they are deliberately not translated — a translated tag would just be a second, unrelated tag.
Taking it down
You can unpublish your own game — owner only. It stops being playable and drops out of every feed while staying entirely intact: the project, the editor, the comments, the likes and the play count are all untouched, so republishing restores it exactly.
It comes back the normal way (Submit → review → Publish), not with a one-click restore, and there is a 24-hour cooldown between unpublishes.
For reports, moderation and blocking, see Reports and moderation.