# GameArter Game Publishing Standard v0.2 > **First version, in testing.** This standard, its tools and the GameArter player are early versions and may still change. Please report bugs, suggestions and improvements via https://www.gamearter.com/contact. This document tells you (a developer or an AI agent) exactly what to deliver to publish a game on GameArter. Everything that is not game-specific is defined here, so you never need to ask GameArter about formats. Version 0.2 describes **what to deliver** (information about the game, texts, images). HTML5 games need no SDK: GameArter adds its player automatically (section 13). Further player modules (ads, analytics, leaderboards) will come in later versions. ## Tools The standard uses the tools below. Each is available in two equal ways – use whichever your agent can reach. Both are public and read-only: **no login, no API key**, and nothing is stored. | Tool | Plain HTTP (works in any agent that can send HTTP requests) | MCP | |---|---|---| | `list_categories` | `GET https://www.gamearter.com/api/publishing/categories` (optional `?search=car`) | `list_categories` | | `validate_package` | `POST https://www.gamearter.com/api/publishing/validate` | `validate_package` | | JSON Schemas (optional) | `GET https://www.gamearter.com/api/publishing/schema` | `get_package_schema` | - **Plain HTTP:** nothing to set up. Validate with a JSON body `{ "manifest": , "texts": , "images": [], "partial": false }` (max 1 MB – image metadata only, never image files). Write the body to a file and send it, for example with curl: ``` curl -s -X POST https://www.gamearter.com/api/publishing/validate -H "content-type: application/json" --data-binary @validate-request.json ``` These are ordinary HTTP requests – curl is only an example, any HTTP client works (wget, PowerShell `Invoke-RestMethod`, a short script). In Windows PowerShell call `curl.exe`, not `curl`. Keep `validate-request.json` outside the package folder. - **MCP:** remote server `https://www.gamearter.com/api/mcp` (Streamable HTTP, no authentication). Worth adding for agents without a shell or for repeated use. This document as Markdown: `https://www.gamearter.com/api/publishing/standard` **Never ask the developer for their GameArter password or any token.** Preparing and validating a package needs no account access; the developer uploads the finished folder in their GameArter account themselves (section 14). ## 1. Workflow 1. **Learn the game.** Play it, read its code or ask the developer. Collect: genre, setting, goal, core loop, progression, modes, controls (desktop and touch), supported languages, content rating. **Never invent features, numbers or modes.** 2. **Get the slug from the developer.** The developer signs up or signs in at https://studio.gamearter.com/ and adds the game as a new project there – that gives the game its slug. The slug cannot be changed by the package. Ask the developer for it, never invent one. Check the name against the rules (section 4). The developer name comes from the GameArter account the game is uploaded under – do not ask for it and do not put it in the package. 3. **Pick genres and tags** from section 3a (also available through `list_categories`). Choose 1 main genre, optionally up to 2 more, and 3–8 tags that really describe the game. 4. **Write `texts.json`** in English (section 8) and fill in gameplay facts, content and declarations (sections 6–7). 5. **Create images** in the required aspect ratios (section 9), optionally a preview video (section 10). 6. **Write `manifest.json`** (section 3). 7. **Validate.** Call `validate_package` (see Tools above) with the manifest, the texts and image metadata. Fix every error, fix warnings when you can. Repeat until `valid: true`. Validation checks the slug format only; that it matches the game in the account is checked on upload. 8. **Submit** the package folder (section 14). ## 2. Package layout ``` / ├─ manifest.json ├─ media/ │ ├─ cover-4x3.png (required) │ ├─ wide-16x9.png (required) │ ├─ square-1x1.png (optional) │ ├─ portrait-2x3.png (optional) │ ├─ screenshot-1.png … (Unity WebGL only, 3–5) │ └─ preview.mp4 (optional) ├─ texts.json (required, English – filled into the │ game page form, not uploaded as a file) └─ build/ (hosted games only) ``` - All JSON files are UTF-8, no comments. - File names in `media/` are fixed (section 9): only the extension may differ (png, jpg or webp). After approval the originals stay available under these names for the websites that take the game over. ## 3. manifest.json | Field | Required | Format | |---|---|---| | `standard` | **yes** | `"0.2"` | | `slug` | **yes** | Exactly the slug of the project the developer added at https://studio.gamearter.com/ (ask the developer). Becomes the game URL. | | `name` | **yes** | English game name, max 40 chars (section 4). | | `version` | **yes** | Game version, e.g. `"1.0"` or `"1.2.3"` (section 13). | | `changelog` | no | What changed in this version, plain text, max 1000 chars. | | `languages` | **yes** | Languages the game itself supports, ISO 639-1 codes. Must include `"en"` (section 5). | | `genres` | **yes** | 1–3 genre slugs, main genre first (section 3a). | | `tags` | no | Up to 8 tag slugs (section 3a), ideally 3–8. Pick precise ones, most relevant first. | | `min_age` | **yes** | Recommended minimum age of players: 3 / 7 / 12 / 16 / 18. Your honest estimate based on the content (violence, fear, language). Older packages may still use the name `pegi`. | | `platforms` | **yes** | `{ "desktop": bool, "mobile": bool }`. `mobile: true` only if the game is fully playable with touch. | | `orientation` | no | `landscape` (default) / `portrait` / `any` – how the game should be held on mobile. | | `game` | **yes** | Hosted on GameArter: `{ "type": "hosted", "engine": "html5" | "unity" }` (Unity may add `"build_folder"`, default `"Build"`). Elsewhere: `{ "type": "external", "url": "https://…" }`. | | `media` | **yes** | Paths to images (keys from section 9), `screenshots` for Unity WebGL (section 9), optional `preview_video` and `youtube` (https URL of a gameplay trailer). | | `theme` | no | `{ "primary": "#RRGGBB", "background": "#RRGGBB" }` (section 11). | | `gameplay` | **yes** | Player modes, session length, audience, saving (section 6). | | `content_descriptors` | **yes** | Content behind the recommended age, may be empty (section 6). | | `declarations` | **yes** | Rights and privacy confirmations (section 7). | | `credits` | no | Third-party assets and licenses (section 7). | Example: ```json { "standard": "0.2", "slug": "turbo-drift", "name": "Turbo Drift", "version": "1.0.0", "languages": [ "en", "de", "es", "fr", "pt", "ru" ], "genres": [ "racing", "arcade" ], "tags": [ "drifting", "cars", "stunts", "3d" ], "min_age": 3, "platforms": { "desktop": true, "mobile": true }, "orientation": "landscape", "game": { "type": "hosted", "engine": "unity", "build_folder": "Build" }, "gameplay": { "player_modes": [ "single" ], "session_length": "short", "audience": "everyone", "saves": "browser" }, "content_descriptors": [], "media": { "cover_4x3": "media/cover-4x3.png", "wide_16x9": "media/wide-16x9.png", "square_1x1": "media/square-1x1.png", "portrait_2x3": "media/portrait-2x3.png", "screenshots": [ "media/screenshot-1.png", "media/screenshot-2.png", "media/screenshot-3.png" ], "preview_video": "media/preview.mp4" }, "theme": { "primary": "#FF5A1F", "background": "#14141F" }, "credits": [ "Music: Example Composer (CC BY 4.0)" ], "declarations": { "owns_rights": true, "no_personal_data": true, "no_third_party_tracking": true } } ``` ## 3a. Genres and tags Genres are the game categories used by Google Play and the App Store, so players, stores and websites understand them the same way. Tag names follow Steam tags where one exists. Use the slugs exactly as written. **Genres** (`manifest.genres`, main genre first): `action`, `adventure`, `arcade`, `board`, `card`, `casino`, `casual`, `educational`, `music`, `puzzle`, `racing`, `role-playing`, `simulation`, `sports`, `strategy`, `trivia`, `word` **Tags** (`manifest.tags`, optional): - **gameplay:** `shooter`, `fps`, `sniper`, `fighting`, `platformer`, `runner`, `parkour`, `battle-royale`, `io`, `clicker`, `idle`, `merge`, `match-3`, `hidden-object`, `physics`, `tower-defense`, `survival`, `sandbox`, `building`, `crafting`, `management`, `tycoon`, `escape-room`, `stealth`, `roguelike`, `bullet-hell`, `drawing`, `coloring`, `dress-up`, `makeover`, `cooking`, `parking`, `drifting`, `stunts`, `jigsaw`, `mahjong`, `solitaire`, `chess`, `snake`, `upgrades` - **theme:** `animals`, `horses`, `dinosaurs`, `cars`, `trucks`, `motorbikes`, `bicycles`, `flight`, `trains`, `naval`, `tanks`, `military`, `police`, `zombies`, `monsters`, `robots`, `space`, `sci-fi`, `fantasy`, `medieval`, `pirates`, `ninja`, `stickman`, `superhero`, `horror`, `christmas`, `halloween`, `food`, `fashion`, `farming`, `city`, `doctor` - **sports:** `soccer`, `basketball`, `american-football`, `tennis`, `golf`, `hockey`, `baseball`, `boxing`, `skiing`, `fishing`, `hunting`, `billiards`, `bowling` - **style:** `3d`, `2d`, `pixel-graphics`, `low-poly`, `cartoon`, `cute`, `funny`, `relaxing`, `difficult` - **education:** `math`, `language`, `geography`, `science`, `typing` - Do not use tags for things the manifest already says: number of players (`gameplay.player_modes`), audience (`gameplay.audience`), mobile support (`platforms`) or the engine (`game`). - No brand, franchise or character names. Missing a tag that fits the game? Tell us via the contact form. - Packages made for standard 0.1 with numeric `category` and `tags` are still accepted for now, but please switch to `genres` and tag slugs. ## 4. Game name The name is the most important piece of SEO and marketing – it appears in search results, on tiles and in links. Choose it deliberately. - **Short and punchy:** 1–3 words, ideally up to 25 characters (hard max 40). Easy to say, spell and remember. - **Tells what the game is about** where possible: one word players would search for (drift, tower, merge, parking, sniper…) combined with a distinctive word (`Turbo Drift`, `Merge Kingdom`, `Sky Sniper`). - **Unique:** must not copy or imitate an existing game or brand.. - **No filler words:** "game", "games", "online", "free", "unblocked", "html5", "browser", "play", "new", "best", "hd" – portals add such words to their titles themselves. - No version numbers, years, emoji or special characters. Title Case, not ALL CAPS. - English. The name stays the same in every language. ## 5. Game language - **English is required:** the game must be fully playable in English and English is its default language. - **Recommended languages:** `en` English, `ar` Arabic, `cs` Czech, `de` German, `es` Spanish, `fr` French, `ja` Japanese, `pl` Polish, `pt` Portuguese, `ru` Russian, `tr` Turkish. - **Multilingual games** pick the language automatically from the browser (`navigator.languages`): the first browser language the game supports wins. If the game does not support any of the browser languages, it falls back to **English**. A language switch in the game menu is welcome, but the game must never start with a language selection screen. - List every supported language in `manifest.languages`, e.g. `["en", "de", "es"]`. Use the base code (`pt`) or a region code (`pt-BR`) as the game does. ## 6. Gameplay and content Facts about the game in `manifest.gameplay` and `manifest.content_descriptors`. Players filter by them and websites use them in their texts. | Field | Required | Values | |---|---|---| | `gameplay.player_modes` | **yes** | Array of `single`, `local_multiplayer`, `online_multiplayer`. | | `gameplay.max_players` | for multiplayer | Maximum number of players. | | `gameplay.session_length` | **yes** | Typical play session: `short` (under 5 minutes), `medium` (5–20 minutes), `long` (over 20 minutes). | | `gameplay.audience` | **yes** | Main target audience: `kids`, `teens`, `everyone`, `adults`. Must match `min_age` (`kids` only with min_age 3 or 7). | | `gameplay.saves` | **yes** | `none` or `browser` – progress saved in the browser (localStorage / IndexedDB) and kept after a page reload. Cloud saves will come later. | | `content_descriptors` | **yes** | What led to the recommended age, may be empty: `violence`, `bad_language`, `fear`, `gambling`, `sex`, `drugs`, `discrimination`, `in_game_purchases`. | ## 7. Rights and privacy `manifest.declarations` must confirm all of the following with `true`. A game that cannot confirm them cannot be published yet. - `owns_rights` – You own or have a license for everything in the game: code, graphics, music, sounds and fonts. No third-party IP (characters, brands, names) without permission. - `no_personal_data` – The game itself does not collect personal data (names, e-mails, location, device identifiers). - `no_third_party_tracking` – The game contains no own tracking, analytics or advertising code of third parties. `manifest.credits` (optional) lists third-party assets and their licenses, one line each, e.g. `"Music: Jane Doe (CC BY 4.0)"`. Assets whose license requires attribution must be listed. ## 8. Texts (texts.json) **English only.** These texts are the source for the GameArter game page and for every website that distributes the game – each of them creates its own language versions and its own SEO texts from your English text. Do not send other languages. All four fields are required. Put `texts.json` into the package folder. When the developer drops the folder in their GameArter account, the texts are filled into a form on the game page (the file itself is not stored). The developer can review and edit them there before submitting. | Key | Format | Length | Content | |---|---|---|---| | `title` | plain | max 60 chars, ideal 30–60 chars | SEO title tag. Starts with the game name, then a short natural description of the game type (e.g. "Turbo Drift - Neon Street Racing Game"). No keyword stuffing. | | `meta_desc` | plain | max 160 chars, ideal 110–150 chars | Meta description. One or two natural sentences saying what the player does and why it is fun. Mentions the game name. | | `controls` | controls | – | Complete control mapping, one control per line in the format `*key* = action`, including touch controls for mobile games (see Controls format). | | `description` | html | min 200 words, ideal 250–700 words | Detailed description of the game – the source for every other text about the game (see What the description must cover). Paragraphs (

) with

subheadings, lists allowed. | Formats: - **plain** – text only, no HTML, no Markdown. - **html** – an HTML fragment. Allowed tags: `

`, `

`, `

`, `