# Blazium Games documentation Concatenated documentation for language models. The short indexes are https://docs.blazium.games/llms.txt, https://blazium.games/llms.txt, and https://mcp.blazium.games/llms.txt. # docs/about.md # About Blazium Games is a place to publish and download games, applications, mods, and assets. Players keep a library, and developers host a page for each project. Builds are uploaded with the chauffeur CLI and served from this platform. Divine Games, Inc. operates Blazium Games. Publishing an account is free. When a game is sold or a donation is made, the fee is fixed: $0.25 plus 8% of the price, taken from the developer. There is no seller-chosen revenue share. The rest of the payment rules are on [Payments](./payments/index.md). Downloads for a published project are hosted here. A player who owns a game, or who downloads a free one, gets the files from Blazium Games. Help with an account or a payment is on the [support page](https://blazium.games/support). The [introduction](./intro.md) lists the other guides. # docs/account-security.md # Account security and sign-in Signing in to [blazium.games](https://blazium.games) takes two steps: your password, then a second step. The second step is a code from your authenticator app if you set one up, or otherwise a 6-digit code we email you. For email-and-password sign-in without an authenticator, a browser that verified an emailed code is remembered for 30 days and isn't asked again. An authenticator code, and the second step of a GitHub, X, or Discord sign-in, are asked for every time. Signing in with GitHub, X, or Discord works the same way. See [Linked accounts and sign-in](./linked-accounts.md). ## Passwords - 10 to 128 characters. A password that matches your email or username is refused. - Passwords that have appeared in known data breaches are refused. Only the first 5 characters of the password's SHA-1 hash leave our servers for that check (the [Have I Been Pwned](https://haveibeenpwned.com/Passwords) range API), never the password itself. - Change it at [Settings > Password](https://blazium.games/settings/password). If you forget it, use **Forgot password** on the login page. ### Changing or setting a password 1. Open [Settings > Password](https://blazium.games/settings/password). 2. Enter your current password and the new one. If the account has no password yet (some accounts made through GitHub, X, or Discord), the page says **Set a password** and asks only for the new one. 3. Choose **Email me a code**, then enter the 6-digit code we email you, valid for 10 minutes, and choose **Save password**. Saving signs out every session, including the one you used, so log in again with the new password. ### Resetting a forgotten password 1. On [blazium.games/password/forgot](https://blazium.games/password/forgot), enter your email and choose **Email me a code**. 2. We email a 6-digit password reset code, valid for 10 minutes. Enter it on the same page, or open **Reset your password** in the email, which takes you back to that page with your email filled in. 3. Choose a new password and select **Reset password**. Your other sessions are signed out. The page answers the same way whether or not the email has an account, so it never reveals who has one. An account that only signed in through GitHub, X, or Discord and never had a password gets a code too; the reset sets its first password. If no code arrives, check your spam folder for mail from noreply@blazium.games, then use **Send a new code**. A code meant for a password reset doesn't work as a sign-in code. ## After you sign in Before the site opens, you may be asked to finish up to three things, in this order. Each one takes you to [blazium.games/account/finish](https://blazium.games/account/finish), and when you're done you continue to the page you were going to. **Log out instead** is always there if you want to stop. 1. **Accept changed terms.** If the [Terms of Service or Privacy Policy](./legal/index.md) changed since you last accepted them, you'll see a short summary of each change with a link to the full text. Tick the box and choose **Accept and continue**. If the terms change again while the page is open, you'll be asked to review the newer version instead. 2. **Finish setting up your account.** Accounts created through GitHub, X, or Discord before passwords were required choose a username and a password here. If your email isn't verified yet, we email a code to confirm it. 3. **Choose whether to use an authenticator app.** Set one up (see below) or choose **Skip for now**. Either way, your choice is recorded and you won't be asked again. You can set one up later from settings. Until these are done, the website's account pages answer with the matching error code (see [Error codes](#error-codes)) and send you back to this page. MCP keys and connected agents keep working; they can see which step is open but never finish it for you. ## Authenticator app An authenticator app (Google Authenticator, Microsoft Authenticator, 1Password, Authy, or any app that supports time-based codes) shows a new 6-digit code every 30 seconds. Once it is set up, sign-in asks for that code after your password. ### Set it up 1. Choose **Set up an authenticator app**, either during sign-in or at [Settings > Authenticator app](https://blazium.games/settings/authenticator). From settings, or if you signed in more than 15 minutes ago, confirm your password first. 2. Scan the QR code with the app, or type in the secret shown under it. 3. Enter the code the app shows and choose **Turn on the authenticator**. 4. Save the 10 **recovery codes**. They are shown only once. Each works once in place of an authenticator code if you lose your phone. Each new setup shows a new QR code. An earlier one you didn't finish stops working. ### Skipped it? Set it up again If you chose **Skip for now** (or turned the authenticator off), [Settings > Authenticator app](https://blazium.games/settings/authenticator) shows the date you skipped it and **Set up an authenticator app again**. That shows a new QR code. Confirm it with a code from the app and you get new recovery codes. ### Replace or turn it off From [Settings > Authenticator app](https://blazium.games/settings/authenticator): - **Replace the authenticator** (for example, on a new phone) needs your password and a code from the current app. The old app keeps working until you confirm the new one. - **Turn off the authenticator** needs your password and a code. Sign-in goes back to emailed codes, your recovery codes stop working, and the choice is recorded as skipped. - **Generate recovery codes** replaces your recovery codes with 10 new ones. ### Phone not with you? Use an emailed code Wherever an authenticator code is asked for, you can use an emailed code instead: - **At sign-in:** choose **Email me a code instead** on the authenticator step. - **In settings:** choose **Email me a code** before replacing or turning off the authenticator. The code works for 10 minutes. You can ask for another after 30 seconds. A recovery code works too. ## Signed out once Session cookies are now limited to the exact site that set them (blazium.games, each developer's store page, and the MCP server each have their own). Everyone was signed out once when this changed. Sign in again and the store pages and MCP connections pick up your session as you visit them. The cookies are listed under [Permissions & Scopes > Cookies](./legal/permissions.md#cookies). ## Your timezone Your timezone sets when daily limits and reports roll over. New accounts take it from your browser. Change it at [Settings](https://blazium.games/settings). Agents connected over MCP can set it with `set_timezone`, using your timezone, never the timezone of the machine they run on. ## Troubleshooting **The email with my code didn't arrive.** Check spam and any filters for `@blazium.games`. Wait 30 seconds, then ask for another code. Each new code replaces the last one. Delivery is usually under a minute. If it takes longer, check [status.blazium.games](https://status.blazium.games) for an email delay, or contact [support](https://blazium.games/support). **The authenticator code is refused.** Make sure your phone's clock is set automatically; codes depend on the time. Each code can be used once, so wait for the next one. Or use a recovery code or an emailed code. **I lost my phone.** Sign in with a recovery code or an emailed code, then replace the authenticator from settings. **"Too many attempts".** Wait a minute and try again. Sign-in, signup, and code checks are limited per address and per network. **I keep being sent back to "Finish signing in".** One of the steps above is still open. Finish it or choose **Log out instead**. ## For agents (MCP) - `get_account` returns `legal_acceptance_required`, `legal_changes`, `setup_required`, `authenticator` (`on`, `skipped`, or `not_chosen`) and `gate` (the next open step, empty when none). - `get_security_status` returns the authenticator `state`, `enabled_at`, `skipped_at`, `recovery_codes_left`, and `email_code_alternative`. It only reads. - Agents never accept terms, finish setup, or set up or skip an authenticator for you. When a step is open, they send you to [blazium.games/account/finish](https://blazium.games/account/finish). See the [MCP reference](./mcp/reference.md). ## Error codes | Code | HTTP | Meaning | | --- | --- | --- | | `4110` | 403 | Accept the changed Terms of Service and Privacy Policy first (`legal_required`) | | `4111` | 403 | Finish setting up the account first (`setup_required`) | | `4112` | 403 | Set up an authenticator app or skip it first (`authenticator_choice_required`) | | `4085` | 400 | The timezone is not a known IANA name | | `4096` | 403 | Verify your email first | | `4290` | 429 | Too many requests; wait a minute | Only website sessions get `4110`, `4111`, and `4112`. Those responses include the open step in `data`, in the same fields as `get_account`. # docs/anonymous-downloads.md # Anonymous downloads Blazium Games is a game publishing platform, with an infrastructure focus. Normally a visitor signs in before downloading, and the first download of a free project adds it to their library with a free license. Anonymous downloads is a setting on each project. When it is on, anyone can download the project's public files without an account, and a signed-out visitor can play the web build and the web demo with no license: - from the store page, where signed-out visitors get a direct download link; - from the Godot or Blazium [editor asset library](./editor-asset-library.md), which doesn't sign in; - from the public API, `GET /api/v1/public/downloads/{file_uid}` (see the [API reference](./api-reference.md)). Signed-in players still download the usual way and still get a free license. ## What you give up Read this before turning it on. The website shows the same list and asks you to confirm it. - **No license or library entry.** Anonymous downloads and anonymous play don't add the project to anyone's library, so the visitor doesn't own it on Blazium Games. - **The web build and the demo play with no account.** A signed-out visitor on the store page starts the full web build when that build can play, and the web demo when it cannot. Turning the setting off stops new play sessions. Embed, Discord, and Telegram are unchanged. - **You can't see who downloaded.** Anonymous downloads are counted in [download analytics](./download-analytics.md), with the source, client, and country, but not tied to an account. - **No update notices.** Anonymous downloaders don't hear about new versions through their library. - **Problems can't be followed up.** A failed or broken anonymous download has no account to contact. - **Downloaded files can't be taken back.** Turning the setting off stops new anonymous downloads. Files already downloaded stay with whoever has them. - **No price or editions while it is on.** See below. ## Free projects only Anonymous downloads only work on free projects: - You can't turn it on while the project has a price or an active edition (error `4113`). - While it is on, setting a price or adding an edition is refused (error `4114`). Turn it off first. - Adult and non-public listings are never served anonymously, even with the setting on. - Files that are still being virus-scanned aren't served (error `4099`). ## Turning it on or off The owner or an accepted admin turns it on from the website, or an agent does it after the human agrees. 1. Open your project's editor on blazium.games and go to the **Settings** tab. 2. Under **Anonymous downloads**, choose **Turn on anonymous downloads**. 3. Read the list, tick **I understand downloads will not be tied to an account**, and choose **Turn on**. **Turn off anonymous downloads** on the same tab switches it off after a confirmation. Turning it off needs no extra confirm. An agent reads `anonymous_downloads` from `get_game`, tells the human that signed-out visitors can download the files and play the web build and the demo with no license, and calls `set_anonymous_downloads` only after the human agrees. The call is `PUT /api/v1/private/games/{game_id}/anonymous-downloads` with `{"enabled": true, "confirm_no_license": true}`. Turning it on without `confirm_no_license` returns `400`, code `4109`. The tool needs `mcp:write`. A paid game or a game with an edition returns `4113`. Setting a price while it is on returns `4114`. After a successful call, `get_game` shows `anonymous_downloads: true`. ## Signed-out download routes These routes answer for any file in the project's public channels: | Route | Answer | |---|---| | `GET /api/v1/public/downloads/{file_uid}` | `{"success": true, "data": {"url", "expires_at", "expires_in", "filename", "checksum", "game_uid"}}`. The link is valid for five minutes. | | `GET /api/v1/public/downloads/{file_uid}/redirect` | A `302` to the same link. The store page links here. | The file uid is in the listing's `files`. When the setting is off, or the project is paid, both routes return `401`, code `4001`, with `data.browse_url`. An unknown, private, or adult file returns `404`, code `4040`. Both routes allow 60 requests a minute per IP address. Every attempt is recorded in download analytics, including refusals. # docs/anticheat.md # Anticheat Anticheat on Blazium Games is per game. The owner of that game is the person who asks for it. Players never see these settings. A developer on a different game cannot read them. ## Asking for access Open **Anticheat** on the game editor and enter the email staff should use. The button is **Enable**. It does not turn anticheat off later. Enabling sends a request. A staff member writes to that email. The conversation is how Blazium fits anticheat to this game. The detailed setup stays off this site so it is not published where someone trying to break games can study it. Settings, reports, and server keys stay closed until an NDA and a contract are signed. Staff record both. The owner cannot mark them signed. ## After both are signed The owner can shut accepted admins out of anticheat. That switch works the same way as shutting admins out of MCP for the game. While it is on, only the owner can open anticheat. The game has one profile. The editor shows the settings that apply to every game, and the settings for the profile you picked. It does not show the other profile. | Profile | What it covers | | --- | --- | | Generic | Checks that apply to any game. | | Platformer | Those same checks, plus checks suited to jumping and falling. Shooter checks are not part of this profile. | | FPS | The checks any game gets, plus checks suited to aiming and weapons. The platformer-only checks are not part of this profile. | The copy of anticheat you ship beside the game is built for that one profile. ## Servers and the game client A dedicated server sends its reports to Blazium with a server key and the game id. A game can have more than one server key. Each key has a name you choose, so a report shows which server sent it. The secret is shown once, when the key is created or rotated. Put it on the dedicated server only. It is not an upload key, and it does not belong in the player build. The game client sends its reports with the player's existing Blazium session and the same game id. The client does not use a server key. Both kinds of report are kept for that game. The owner can read them and can ask the dedicated server to warn, mute, kick, or ban a player, or to take a screenshot. ## Where it lives in a game A Blazium game uses the engine's anticheat module. The store plugin, the games module, and the games SDK do not load anticheat. A game on another engine receives an integration sample as part of the agreement. The launcher does not download anticheat for the player. Running anticheat on your own servers, outside Blazium Games, is a separate license. It is not a setting on the game page. ## Agents Anticheat tools are on the developer MCP server only. They need the scope `mcp:anticheat`. `mcp:read`, `mcp:write`, and **Full access** do not include that scope. The consent page offers an **Anticheat** preset that grants only `mcp:anticheat`. The player MCP server has none of these tools. The tool names and what each one is for are on the [MCP reference](./mcp/reference.md#anticheat). They do not describe how a check decides. # docs/api-reference.md # Public API reference Blazium Games is a game publishing platform, with an infrastructure focus. The public API at `https://api.blazium.online` serves the catalog, the editor asset library, signed-out downloads, game telemetry, and build registration. ## OpenAPI description The public endpoints are described in OpenAPI 3.1: - JSON: [https://api.blazium.online/api/v1/public/openapi.json](https://api.blazium.online/api/v1/public/openapi.json) - YAML: [https://api.blazium.online/api/v1/public/openapi.yaml](https://api.blazium.online/api/v1/public/openapi.yaml) Load either into Swagger UI, Redocly, Postman, or a client generator. The document is also linked from the [API catalog](./discovery.md#developer-discovery) as `service-desc`. Signed-in account routes (`/api/v1/private/...`) are used by the website and the MCP servers and are not part of it. Agents should use the [developer](./mcp/index.md) or [player](./mcp/player.md) MCP server instead. Game chat isn't part of this API either. It is IRC at `irc.blazium.online`; see [Chat](./chat/index.md). Chat tokens are managed in Settings > Chat or with the player MCP chat tools, and the [client developer reference](./chat/client-developers.md) covers sign-in, capabilities, tags, and numerics. ## Authentication Most public routes need no credentials. The rest take a header: | Scheme | Header | Used by | |---|---|---| | Player key or player OAuth token | `Authorization: Bearer ...` (or the `BLAZIUM_GAMES` header) | Optional on the [editor asset library](./editor-asset-library.md). Needs `player:read`. | | Deploy key | `X-Access-Token` and `X-Secret-Key` | Build registration. See [Deploy builds](./deploy.md). | | Game id | `X-App-Id` and `X-Build-Id` | Crash and event ingest. See [Crash reporting](./crash-reporting.md). | | Steam auth key | `Authorization: Bearer ...` | The `server` routes of [Steam auth verification](./steam-auth.md), from your own servers. | Player keys start with `bgames_play_` and are created at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). Player OAuth tokens come from `https://mcp.blazium.games/.well-known/oauth-authorization-server/player`. See [Player MCP](./mcp/player.md). Credentials are always headers. These routes never read cookies. ## Responses Answers use the Blazium envelope: ```json { "success": true, "data": { } } ``` ```json { "success": false, "error": { "code": 4040, "message": "File not found" } } ``` Some errors add a top-level `data` object. A download that needs a sign-in or a purchase, for example, adds `browse_url` and the price. The editor asset library is the exception. Its successful answers are the raw objects the Godot and Blazium editors parse, with no envelope. Its errors still use the envelope. ### Common error codes | Code | HTTP | Meaning | |---|---|---| | `4001` | 401 | Sign in to download (or sign in and buy). | | `4023` | 402 | Buy this game to download it. | | `4031` | 403 | The token lacks the scope this route needs (`player:read`). | | `4033` | 403 | This kind of token can't use this route. | | `4040` | 404 | Not found, or not public. | | `4099` | 409 | The file is still being virus-scanned. | | `4130` | 413 | Too many events or metadata keys in one request. | | `5030` | 503 | The download link couldn't be signed. Try again. | An invalid or expired token returns `401`. It is never treated as anonymous. ## Rate limits Unless a row says otherwise, these limits are per IP address, per minute. Past a limit the answer is `429`. | Routes | Limit | |---|---| | Asset library browsing (`configure`, `asset`, `asset/{asset_id}`) | 300 | | Asset library download | 60 | | Signed-out downloads (`/downloads/{file_uid}` and `/redirect`) | 60 | | OpenAPI document | 120 | | Press kit zip | 30 | | Events (`POST`) | 60 | | Crash reports (`POST /api/v1/public/crashes`) | 60 per game (counted by `X-App-Id`), not per IP | Shelves, tags, the sitemap, mods and tools, and press kits also have overall limits across all callers. ## CORS The asset library, signed-out downloads, and the OpenAPI document allow any origin (`Access-Control-Allow-Origin: *`), without credentials. A browser tool on any site can call them. ## Endpoints | Method and path | What it does | |---|---| | `GET /health`, `GET /ready` | Liveness and readiness. | | `GET /api/v1/public/openapi.json`, `.yaml` | The OpenAPI document. | | `GET /api/v1/public/asset-library/configure` | Editor categories and sign-in details. | | `GET /api/v1/public/asset-library/asset` | Search editor packages. | | `GET /api/v1/public/asset-library/asset/{asset_id}` | One editor package. | | `GET /api/v1/public/asset-library/asset/{asset_id}/download` | Redirect to the package zip. | | `GET /api/v1/public/downloads/{file_uid}` | A signed link for a file, without an account, when [anonymous downloads](./anonymous-downloads.md) are on. | | `GET /api/v1/public/downloads/{file_uid}/redirect` | The same, answered with a redirect. | | `GET /api/v1/public/search` | Catalog search. See [Listings](./listings.md). | | `GET /api/v1/public/shelves/{kind}` | A home page shelf, such as `new`, `browser_playable`, or `tonight`. `limit` is 1 to 24. See [Shelves](./listings.md#shelves). | | `GET /api/v1/public/tags/popular` | The most used tags. | | `GET /api/v1/public/sitemap` | Indexable listings and developers. | | `GET /api/v1/public/store-rules` | Price limits and fees. | | `GET /api/v1/public/games/{game_id}` | A listing. | | `GET /api/v1/public/games/{game_id}/reviews` | Its reviews. | | `GET /api/v1/public/games/{game_id}/relations` | Its parent, dependencies, and similar titles. | | `GET /api/v1/public/games/{game_id}/children` | Its mods and tools. | | `GET /api/v1/public/games/{game_id}/press`, `/press.zip` | Its [press kit](./press-kit.md). | | `GET /api/v1/public/games/{game_id}/files/{file_uid}/provenance` | Where a build file came from, and its scan state. | | `GET /api/v1/public/user/{user_id}/games/{game_id}/files` | A listing's public files. | | `POST /api/v1/public/crashes` | Send a crash report. | | `POST /api/v1/public/events` | Send game events. | | `POST /api/v1/tool/upload/build` | Register a build with a deploy key. | | `POST /api/v1/oauth/token` | Exchange a project's sign-in code, or refresh that access token. See [Sign in with a project's application](./project-oauth.md). | | `GET /api/v1/oauth/userinfo` | The claims a player agreed to share. Accepts only an access token from the row above. | | `POST /api/v1/steam/{game_uid}/auth`, `/refresh` | Trade a Steam session ticket for a session token, or refresh one. See [Steam auth verification](./steam-auth.md). | | `POST /api/v1/steam/{game_uid}/server/verify`, `/server/revoke` | Check or revoke session tokens with the game's Steam auth key. | | `GET /api/v1/steam/{game_uid}/server/ownership/{steam_id}` | Ask whether a Steam account owns the game, with the Steam auth key. | File uploads go to `uploader.blazium.online` and are described in [Deploy builds](./deploy.md) and the [chauffeur CLI](./cli/index.md). # docs/bug-reporter.md # In-game bug reporter The reporter is off until you turn it on for that game. A licensed Blazium player can still file a ticket from the store with `report_bug`. The in-game route is only available when the reporter is on. ## Turn it on On the listing's **Bug reporter** tab, or with `set_bug_reporter`: - `enabled` - `daily_cap`, from 1 to 10000, default 10. The store route and the in-game route share this cap, per game and per reporter. - up to five `https` webhook URLs. A sixth is rejected. `http://127.0.0.1` is accepted only for a local receiver. The first time the reporter is turned on, that game gets its own signing key. It is shown in the settings so you can copy it into your receiver. **Refresh signing key** replaces only that game's key. A signature from one game does not verify another game's webhook or screenshot. `get_bug_reporter` needs `mcp:bugs.read`. `set_bug_reporter` and `update_bug_ticket` need `mcp:bugs.write`. `mcp:crash.read` does not cover these. ## File a report from the game `POST /api/v1/games/{game_uid}/bugs` accepts a Blazium player JWT or a Steam session for that same game. The body is multipart: | Field | Limit | |---|---| | `message` | required, 4000 characters | | `client_version`, `os`, `arch`, `build_id` | optional. `build_id` is the fallback when `X-Build-Id` is absent | | `log` | 512 KiB. The service redacts a SteamID64, `discord_id`, a bearer token, an API key, an email address, and a session cookie before the log is stored. The text is stored with the ticket and is not put in the webhook | | `screenshot` | one PNG, JPEG, or WebP, up to 32 MiB, stored at the size the game sent | Send `X-App-Id` and `X-Build-Id` with the report, the same headers crash ingest uses. `X-App-Id` is the game uid and must match the path. `X-Build-Id` is that game's build uid. The signed webhook JSON and the Discord embed include `app_id` and `build_id` next to the version. Over the daily cap returns code `4291`. The Godot plugin, the Unity package, the Unreal plugin, and the C++ SDK expose two calls. `report_bug` is the short store-style report and does not send `X-Build-Id`, the log, or the screenshot. The longer in-game call (`report_ingame_bug` on the engine, `ReportInGameBug` on the native library) sends those fields. Godot, Unity, and Unreal take the extra fields on their `report_bug` entry point and send the in-game call when a build id or a screenshot path is set. A screenshot path has to sit under the game's user directory, and the read stops at 32 MiB. They send the Blazium JWT, or the Steam session from `sign_in_with_steam_ticket`, and they do not link Steamworks. See [Engines](./engines.md). ## Webhooks A new report is delivered to every URL. Each URL is posted up to three times with the same signed body, and a 2xx stops the retries. The settings response includes `last_delivery` for each URL: the time, the HTTP status or error, and whether it succeeded. - A Discord webhook (`https://discord.com/api/webhooks/` or `https://discordapp.com/api/webhooks/`) gets an embed with the game, ticket id, version, and whether a log or screenshot exists. The file is not attached. - Any other URL gets JSON. The body includes `signature`, an HMAC-SHA1 of the JSON before that field was added, and a time-limited `screenshot_url` when there is an image. The screenshot URL is signed the same way Spaces signs a private object: base64 HMAC-SHA1 over `GET\n\n\n{expires}\n/{path}`, carried as `Expires` and `Signature`. Your service checks that signature with this game's key and can download the image without a Blazium login. Refreshing the key invalidates older signatures for that game only. ## Notices When a ticket is marked `fixed` or `unidentified`, the player who filed it can read it from `GET /api/v1/games/{game_uid}/bugs/notices` and acknowledge it with `POST .../notices/ack`. `fixed` means the bug was fixed. `unidentified` means the report could not be pinned down, and it does not say the bug was fixed. A `closed` ticket stays silent in the game. A stable build's changelog uses the same pull: `GET /api/v1/games/{game_uid}/patch/notices` and `POST .../patch/notices/ack`. See [Deploy builds](./deploy.md). ## On the website A developer triages tickets at `/edit//bugs` and sets `open`, `fixed`, `unidentified`, or `closed`. A player reads their own reports, including closed ones, at `/bugs`. The player cannot change status. ## From MCP and chauffeur `list_bug_tickets` returns 50 tickets a page. Follow `next_page`. `get_bug_ticket` reads one. `request_bug_screenshot` returns a one-hour link, not the image. `get_bug_log` returns at most 16 KiB; call it again with `next_offset` until that field is absent. `chauffeur bugs` lists the same tickets with the game's deploy key. `chauffeur bugs screenshot`, `chauffeur bugs log`, and `chauffeur bugs pull` save the files. The deploy key cannot change status and cannot read crash dumps. # docs/chat/client-developers.md # For client developers Blazium Games chat is standard IRC (UnrealIRCd 6) with a few additions for games. Anything a normal IRC client does keeps working; the additions are opt-in. ## Connecting | Transport | Address | |---|---| | TLS | `irc.blazium.online:6697` | | Websocket (browsers) | `wss://irc.blazium.online:8000`, one IRC line per text frame | Every connection must sign in before it is let on to the network. ## Signing in The password is one of two tokens: - **A chat token** (`bzc_...`) the player made in [Settings > Chat](https://blazium.games/settings/chat). Long-lived; see [IRC clients](./irc-clients.md#get-a-chat-token). - **A short-lived sign-in token** that works for 10 minutes. BlaziumLauncher and the website get one for the signed-in player. An AI agent gets one from the player MCP tool [`get_chat_connection`](../mcp/player.md#chat), which also returns the host, port, and websocket address. **SASL PLAIN** (preferred): ```text CAP LS 302 CAP REQ :sasl blazium.games/tags blazium.games/commands blazium.games/membership NICK username USER username 0 * :username AUTHENTICATE PLAIN AUTHENTICATE CAP END ``` Send `CAP END` after `903`. `904` means the token was refused. **GAMEAUTH**, for clients without SASL: send `GAMEAUTH ` before `NICK` and `USER`. The answer is `1800 :You are now logged in as `, or `1841`/`1846` on failure. Three failures in 30 seconds give `1852` until the window passes. A second login on the same connection gets `1843`. After sign-in the nick is forced to the account's username, and changing it is refused. Only `PLAIN` is offered as a SASL mechanism. ## ISUPPORT After registration, `005` includes: | Token | Meaning | |---|---| | `GAMESERVICES=2` | The game chat commands and numerics on this page are available. Version 2 added `GAMEAUTH`, spectating, `GAMES`, `LFGWHO`, `LFGMETA`, the capabilities, and the tags | | `GAMEVENDOR=blazium.games` | The vendor prefix used by the capabilities and tags | ## Capabilities | Capability | What it adds | |---|---| | `blazium.games/tags` | Messages in game channels carry the `blazium.games/game` and `blazium.games/role` tags | | `blazium.games/commands` | Turns on `GAMES` | | `blazium.games/membership` | With `blazium.games/tags`, the server sends you a `TAGMSG` to the channel when you join a game chat and whenever your role in it changes | ## Message tags | Tag | Value | |---|---| | `blazium.games/game` | The game's uid | | `blazium.games/role` | The sender's role in that game's chat: `owner` (owner and accepted admins), `chat` (voiced), or `spectator` (no voice) | Example, with `blazium.games/tags`: ```text @blazium.games/game=550e8400-e29b-41d4-a716-446655440000;blazium.games/role=chat;msgid=...;time=... :alice!alice@... PRIVMSG #g0123456789abcdef :gg ``` The membership `TAGMSG` carries your own role and the game uid: ```text @blazium.games/role=chat;blazium.games/game=550e8400-e29b-41d4-a716-446655440000 :irc1.blazium.online TAGMSG #g0123456789abcdef ``` Game channels are mode `+A `, so a client can map a channel back to its game without the tags. ## Game invites BlaziumLauncher invites a friend to a game with a private message whose text is `PLAY:`. The launcher shows a play card instead of the text. Other clients can send and recognise the same text. ## Commands | Command | Notes | |---|---| | `GAMEJOIN ` / `GAMEPART ` | The only way into a game channel. `JOIN` on a game channel fails with `473` "Join game chat with GAMEJOIN" | | `LFGSUB ` / `LFGUNSUB ` | Spectate (no voice). Up to 10 at once | | `GAMES [uid]` | Needs `blazium.games/commands` | | `LFGWHO ` | Members of a game chat you're in | | `LFGMETA ` | Name, channel, and counts | | `REGISTER`, `VERIFY` | Answer with `1822` pointers to the website; accounts aren't made over IRC | User-facing descriptions are on the [Commands](./commands.md) page. ## Numerics Every numeric is sent as `: `. | Numeric | Parameters | When | |---|---|---| | `1800` | ` :You are now logged in as ` | GAMEAUTH succeeded | | `1801` | ` :Joined game chat` | `GAMEJOIN` | | `1802` | ` :Spectating game chat` | `LFGSUB` | | `1803` | ` :Left game chat` | `GAMEPART`, `LFGUNSUB` | | `1804` | ` :` | One per game in `GAMES` | | `1805` | ` :End of GAMES` | End of `GAMES` | | `1810` | ` :` | One per member in `LFGWHO` | | `1811` | ` :End of LFGWHO` | End of `LFGWHO` | | `1812` | ` :` | `LFGMETA` keys: `name`, `channel`, `users`, `chat`, `spectators`, `listed` (`yes`/`no`), `bound` (`yes`/`no`) | | `1813` | ` :End of LFGMETA` | End of `LFGMETA` | | `1822` | `REGISTER :` or `VERIFY :` | `REGISTER` or `VERIFY` | | `1830` | ` :is in game chat` | In your own `WHOIS` | | `1841` | `:Authentication failed` | The token was refused | | `1842` | ` :No such game chat` | `GAMES `, `LFGWHO`, `LFGMETA` | | `1843` | `[] :...` | Already logged in, or already in that game chat | | `1844` | ` :Too many spectated games` | `LFGSUB` over the limit | | `1845` | ` :Invalid game id` | Not a uid | | `1846` | `:That chat token is not valid` | GAMEAUTH with text that isn't a token | | `1847` | `[] :Game chat is unavailable right now` | The game service couldn't be reached | | `1848` | ` :You are not in that game chat` | `LFGWHO`, `LFGUNSUB` | | `1850` | ` :Capability required for this command` | `GAMES` without `blazium.games/commands` | | `1851` | ` :Game chat is full on this server` | The game's channel is full on this server | | `1852` | `:` | Too many login attempts, or a login is already in progress | | `1860` | ` :Try connecting to this server` | Sent after `1851` with a server that has room | Numerics `1818`-`1821` are for network operators. ## Notices to expect | Notice | Meaning | |---|---| | "Authenticate before joining game chat" | A game command before sign-in | | "You cannot join that game chat" | No license with guests off, or banned | | "You need a license to speak in this game chat" | A message from someone without voice (`404`) | | "This game chat has closed" | The game's chat was taken down; the channel no longer belongs to a game | | "License changed" (as a part reason) | Access was re-checked and you're no longer allowed in | ## Good behaviour - Reconnect with backoff. A rate-limited client (`1852`) should wait at least 30 seconds. - Don't store short-lived tokens; ask for a new one each time you connect. - Never log or display a chat token after the player has copied it. # docs/chat/commands.md # Commands Game chat commands take the game's uid, the long id in its store page address, for example `550e8400-e29b-41d4-a716-446655440000`. In most IRC clients, type them with `/quote` in front: ```text /quote GAMEJOIN 550e8400-e29b-41d4-a716-446655440000 ``` You have to be signed in. Before that, the commands answer "Authenticate before joining game chat". ## Join and leave | Command | What it does | Reply | |---|---|---| | `GAMEJOIN ` | Joins the game's chat. Owners and admins join as operators, licensed players with voice, and guests (when allowed) without voice | `1801 :Joined game chat` | | `GAMEPART ` | Leaves it | `1803 :Left game chat` | `GAMEJOIN` is the only way into a game channel. `/join #g...` is refused with "Join game chat with GAMEJOIN". If you can't join, you get the notice "You cannot join that game chat": you don't own the game and guests are off, or you're banned from it. ## Spectate a game | Command | What it does | Reply | |---|---|---| | `LFGSUB ` | Joins the game's chat to read only, with no voice, even if you own the game | `1802 :Spectating game chat` | | `LFGUNSUB ` | Stops spectating and leaves | `1803 :Left game chat` | You can spectate up to 10 games at once. You can only spectate a game you could join. ## Find out about games | Command | What it does | Reply | |---|---|---| | `GAMES` | Lists every game that has a chat channel | One `1804 :` line per game, then `1805 :End of GAMES` | | `GAMES ` | The same line for one game | `1804`, then `1805 1 :End of GAMES` | | `LFGWHO ` | Who is in a game chat you're in | One `1810 :` line per person, then `1811 :End of LFGWHO` | | `LFGMETA ` | What the server knows about a game chat | `1812 :` for `name`, `channel`, `users`, `chat`, `spectators`, `listed`, and `bound`, then `1813 :End of LFGMETA` | | `WHOIS ` | Your own WHOIS lists the game chats you're in | `1830 :is in game chat` per game | `GAMES` needs the `blazium.games/commands` capability. Ask for it with `/quote CAP REQ blazium.games/commands`, or see [For client developers](./client-developers.md#capabilities). A game's name shows in `GAMES` only while its store page is public; otherwise the uid is shown in its place. Roles in replies are `owner` (operators: the owner and accepted admins), `chat` (voiced), and `spectator` (no voice: guests and spectators). ## Everyday IRC Normal IRC works as usual: private messages to a friend's username, `/me`, `/names`, `/whois`, `/away`, and so on. Recent channel history is shown when you join, so you can catch up. If a game's chat is taken down, people in its channel see "This game chat has closed". ## Replies and errors Every reply is a numeric in the 1800 range sent to your nick. | Numeric | Meaning | What to do | |---|---|---| | `1841` | Authentication failed | The token is wrong, expired, revoked, or the account is locked out of chat. Check it, or regenerate it in Settings > Chat | | `1842` | No such game chat | That game has no chat channel right now: nobody has joined it yet, or its chat was closed. `GAMEJOIN` opens it if you're allowed in | | `1843` | Already logged in, or already in that game chat | Nothing to do | | `1844` | Too many spectated games | Stop spectating one with `LFGUNSUB` first (the limit is 10) | | `1845` | Invalid game id | Use the full uid from the game's store page | | `1846` | That chat token is not valid | The text you sent isn't shaped like a token. Copy it again | | `1847` | Game chat (or the game list) is unavailable right now | Try again in a minute. Check the [status page](https://status.blazium.games) | | `1848` | You are not in that game chat | Join it first | | `1850` | Capability required for this command | Request the capability named in the reply | | `1851` | Game chat is full on this server | Reconnect; a `1860` line names a server to try | | `1852` | Too many login attempts, or a login is already in progress | Wait about 30 seconds and try again | The full list, with every parameter, is in [For client developers](./client-developers.md#numerics). # docs/chat/for-publishers.md # Chat for publishers Every game, app, mod, or asset on Blazium Games can have a chat channel. You don't have to set anything up. ## Your channel - The channel is created the first time someone joins it. Its name is `#g` followed by 16 characters derived from your project's uid, and it never changes. - Players reach it from BlaziumLauncher, their own IRC client with `GAMEJOIN `, or a client that lists games with `GAMES`. - Your project's name shows in game lists only while its store page is public. - The **Chat** tab on your project's edit page shows the channel name, and **Connect** signs you in to talk there from the browser. ## Who can talk | Who | Role | |---|---| | You and your accepted [team admins](../storefront/team-and-keys.md#admins) | Operators. You can always talk and can't be banned or muted | | Players with a license | Voiced. They can talk | | Guests (no license) | Only when you allow them. They can read, and talk once they own the game | | The platform account `blazium` | Sits in the channel to carry out bans and mutes. It can't be banned or muted | Licenses are checked again while players are in the channel, so a player who buys the game gets a voice, and one who loses the license is removed. ## Guests Guests are off by default. On the **Chat** tab, tick **Let people without a license join** and select **Save**. Turning guests off removes guests who are in the channel at their next access check. ## Bans and mutes On the **Chat** tab, type a username and pick an action: | Action | Effect | |---|---| | **Ban** | Removes the player from the channel now and keeps them out until you unban them | | **Unban** | Lifts a ban | | **Suspend** | Mutes the player for the number of minutes you enter (1 to 43,200, which is 30 days). They can still read | | **Lift suspension** | Ends a mute early | **Who cannot talk** lists everyone banned or muted, with when each mute ends. Bans and mutes are saved and still apply after the player reconnects. The same actions are on the [developer MCP server](../mcp/reference.md#game-chat): `get_game_chat`, `set_chat_guests`, `ban_chat_user`, `unban_chat_user`, `suspend_chat_user`, and `unsuspend_chat_user`. ## What Blazium Games does Chat follows the [Chat Rules](../legal/chat-rules.md). Blazium Games can lock an account out of all chat or suspend it, on any channel. Reports go to [support@blazium.games](mailto:support@blazium.games); see [Something in chat](../storefront/report.md#something-in-chat). If your project's chat is taken down, people in the channel see "This game chat has closed". # docs/chat/index.md # Chat Blazium Games chat is IRC on `irc.blazium.online`. It carries two things: - **Friend messages.** Private messages between accounts. Your nick is always your username, so a message to a friend goes to their username. - **Game chat.** Every game has its own channel, named like `#g0123456789abcdef`. You get into it with the game's uid, not by typing the channel name. Chat follows the [Chat Rules](../legal/chat-rules.md): anything legal is allowed, nothing illegal, and never any harm to children. Chat is not logged. ## Ways in | Where | How it signs you in | Port | |---|---|---| | The website | The **Chat** tab on a project's edit page signs you in with a short-lived token | `8000` (websocket, TLS) | | [BlaziumLauncher](../storefront/desktop-app.md) | Signs you in for you. Chat opens one tab per friend and per game, and asks before it sends | `6697` (TLS) | | Your own IRC client | Your username and a chat token from [Settings > Chat](https://blazium.games/settings/chat). See [IRC clients](./irc-clients.md) | `6697` (TLS) | | An AI agent | The [player MCP server](../mcp/player.md#chat) can sign the agent in as you for 10 minutes | `6697` or `8000` | Every connection signs in to a Blazium Games account. There are no anonymous users, and nobody can take your nick. ## Who can talk in a game's chat | Who | In the channel | Can talk | |---|---|---| | The project owner and accepted admins | Operators (`@`) | Yes | | Players with a license | Voiced (`+`) | Yes | | Guests (no license), only when the project allows guests | Joined without voice | No, until they own the game | | Anyone spectating | Joined without voice | No | Guests are off unless the project turns them on. Licenses are checked again while you're in the channel, so buying the game gives you a voice, and losing the license takes it away. ## Spectating Spectating lets you read a game's chat without talking, even if you own the game. You can spectate up to 10 games at once. The access rules are the same as joining: you can only spectate a game you could join. See [Commands](./commands.md#spectate-a-game). ## Moderation - The project owner and accepted admins can ban someone from the game's channel, or mute them for up to 30 days. A muted player can still read. The owner, accepted admins, and the platform account `blazium` can't be banned or muted. See [Chat for publishers](./for-publishers.md). - Blazium Games can lock an account out of all chat, for a set time or until lifted, or suspend the account. A lock disconnects the account right away and refuses new sign-ins. - Bans, mutes, and locks are saved, so they still apply after a reconnect. ## What chat keeps Messages aren't logged. Each channel keeps its last 50 lines for up to a day in the servers' memory, so people who join can catch up. The [Chat Rules](../legal/chat-rules.md#5-what-we-keep) list everything else that is kept. ## Status The [status page](https://status.blazium.games) shows two chat components: - **Game chat**: the chat servers on ports 6697 and 8000. A problem on 8000 doesn't stop people who are already on 6697 from talking. - **Chat commands**: live moderation and disconnecting a regenerated token. When only this is down, people can still talk. Saved bans still keep people out, and a regenerated or revoked token is still cut off within about a minute. Removing or muting someone who is already in a channel waits until it's back. Chat updates are rolled out without disconnecting anyone. You may see a short notice from the network before and after. ## In this section - [IRC clients](./irc-clients.md): chat tokens and setting up HexChat, WeeChat, irssi, and others. - [Commands](./commands.md): joining, spectating, listing games, and every reply. - [For client developers](./client-developers.md): sign-in, capabilities, message tags, and numerics. - [Chat for publishers](./for-publishers.md): guests, admins, bans, and mutes for your game. - [Troubleshooting](./troubleshooting.md): can't sign in, can't talk, and other problems. # docs/chat/irc-clients.md # IRC clients Any IRC client that does TLS and SASL PLAIN works: HexChat, WeeChat, irssi, Textual, KVIrc, and others. You sign in with your Blazium Games username and a **chat token**. ## Get a chat token 1. Open [Settings > Chat](https://blazium.games/settings/chat). 2. Select **Create token**. 3. Copy the token (it starts with `bzc_`). It is shown once and can't be shown again. Settings > Chat also shows the start of your current token, when you made it, and when it was last used. It never shows the whole token again. | Action | What happens | |---|---| | **Regenerate token** | Makes a new token. Tick **Disconnect clients using my current token** first. The old token stops working and every client signed in with it is disconnected right away | | **Revoke token** | Removes the token and disconnects every client signed in with it. Your account keeps working on the website and in the launcher | You can create, regenerate, or revoke up to 10 times an hour. An AI agent on the [player MCP server](../mcp/player.md#chat) can do the same, but only when you ask, and the token is shown once in that answer. **Keep it secret.** Anyone with your token can chat as you. If it leaks, or you lose it, regenerate it. ## Client settings | Setting | Value | |---|---| | Server | `irc.blazium.online` | | Port | `6697`, TLS on | | Sign-in | SASL PLAIN | | Username / nick | Your Blazium Games username | | Password | Your chat token | Your nick is always your username. The network sets it when you sign in, and `/nick` to anything else is refused with "Your nickname is your Blazium username". ## Set up a client **irssi** ```text /network add -sasl_username YOUR_USERNAME -sasl_password YOUR_TOKEN -sasl_mechanism PLAIN blazium /server add -tls -network blazium irc.blazium.online 6697 /connect blazium ``` **WeeChat** ```text /server add blazium irc.blazium.online/6697 -tls /set irc.server.blazium.sasl_mechanism plain /set irc.server.blazium.sasl_username YOUR_USERNAME /set irc.server.blazium.sasl_password YOUR_TOKEN /connect blazium ``` **HexChat:** add a network with server `irc.blazium.online/6697`, tick **Use SSL for all the servers on this network**, set **Login method** to **SASL (username + password)**, and enter your username and token. **Textual, KVIrc, and others:** turn on TLS, pick SASL PLAIN (sometimes called "SASL username and password"), and use the settings above. After you connect, join a game's chat with `/quote GAMEJOIN `. The [Commands](./commands.md) page lists the rest. ## Clients without SASL Bots and small clients that can't do SASL can send `GAMEAUTH ` as their first line, before `NICK` and `USER`: ```text GAMEAUTH bzc_yourtoken NICK anything USER bot 0 * :My bot ``` A good login answers `1800 :You are now logged in as `, and the network sets your nick to your username. A wrong token answers `1841` (or `1846` if it isn't shaped like a token). After 3 failed tries in 30 seconds you get `1852` and have to wait before trying again. A connection that never signs in is not let on to the network. ## Making an account over IRC Accounts are made and verified on the website, not over IRC. `REGISTER` and `VERIFY` only answer with a pointer to [blazium.games](https://blazium.games) and how to sign in. # docs/chat/troubleshooting.md # Troubleshooting ## I can't sign in | What you see | Fix | |---|---| | `904` or "SASL authentication failed" | Check the username is your Blazium Games username and the password is your whole chat token. Regenerate it in [Settings > Chat](https://blazium.games/settings/chat) if you're not sure | | `1841` Authentication failed | Same as above. A revoked or replaced token stops working right away | | `1852` Too many login attempts | Wait about 30 seconds, then try once with the right token | | The client hangs after connecting | Turn on TLS for port 6697 and SASL PLAIN. A connection that never signs in is not let on to the network | | "Set a username before chatting" | Chat needs a username. Set one in your profile first | | "Your account can't use chat right now" in Settings > Chat | Your account is locked out of chat. Email [support@blazium.games](mailto:support@blazium.games) if you think that's a mistake | The website and BlaziumLauncher sign you in for you. If they fail, sign out and back in, then try again. ## I can't join a game's chat - `/join #g...` doesn't work for game channels. Use `/quote GAMEJOIN `. - "You cannot join that game chat" means you don't own the game and the project doesn't allow guests, or you're banned from that channel. - `1845` means the uid is wrong. Copy the full uid from the game's store page address. - `1847` means chat couldn't check your access just then. Try again in a minute. ## I'm in the channel but can't talk "You need a license to speak in this game chat" means one of: - You don't own the game. Guests can read but not talk; buy the game and you get a voice. - You joined with `LFGSUB` to spectate. Leave with `LFGUNSUB` and join with `GAMEJOIN` instead. - The owner or an admin muted you. Mutes last up to 30 days and you can still read. ## "Game chat is full on this server" The game's channel is busy on the server you landed on. Reconnect to `irc.blazium.online`; the `1860` line names a server with room. ## Chat or commands look down Check the [status page](https://status.blazium.games). If only **Chat commands** is down, you can still talk; moderation and token disconnects catch up when it's back. If **Game chat** is down on port 8000 only, the website Chat tab is affected, but launcher and IRC clients on 6697 keep working. During an update you may see a notice that chat maintenance is starting. You stay connected. ## My chat token leaked Go to [Settings > Chat](https://blazium.games/settings/chat), tick **Disconnect clients using my current token**, and select **Regenerate token**. Everyone using the old token is disconnected right away. **Revoke token** does the same without making a new one. ## Still stuck See [Get help](../storefront/get-help.md). To report someone breaking the [Chat Rules](../legal/chat-rules.md), see [Something in chat](../storefront/report.md#something-in-chat). # docs/cli/authentication.md # Authentication chauffeur uses the game's **deploy key**. A deploy key is two values for one project: an access token and a secret. chauffeur and CI need both. It sends the access token as `X-Access-Token` and the secret as `X-Secret-Key`, over HTTPS only. The access token is `BLAZIUM_ACCESS_TOKEN`. It stays on the Deploy keys tab. The secret is `BLAZIUM_SECRET_KEY`. It is shown once. Copy it before you leave the page. It cannot be shown again. ## Deploy keys and MCP keys | | Deploy key | MCP key | |---|---|---| | Used by | chauffeur, CI, the upload API | Agents through the MCP server | | Scope | Upload builds, symbols and store images for one game; read that game's info and builds | Manage store pages, read analytics and crashes, and more, depending on scopes | | Can upload files | Yes | No | | Issued on | The game's edit page, **Deploy keys** tab, or MCP `request_deploy_key` | Settings, or MCP `request_mcp_key` | An MCP key can't upload, and a deploy key can't change the store page's text, price or channels. ## Where chauffeur reads the key Flags win over environment variables, and environment variables win over the defaults. | Setting | Flag | Environment variable | Default | |---------|------|----------------------|---------| | Access token | `--access` | `BLAZIUM_ACCESS_TOKEN` | none | | Secret key | `--secret-stdin` or `--secret` | `BLAZIUM_SECRET_KEY` | none | | API URL | `--url` | `BLAZIUM_API_URL` | `https://api.blazium.online/api/v1` | | Upload URL | `--upload` | `BLAZIUM_UPLOAD_URL` | `https://uploader.blazium.online/api/v1` | Service URLs must use `https` (plain `http` is allowed only for `localhost`) and can't contain a user name or password. ### Passing the secret - **Environment variable** (recommended in CI): set `BLAZIUM_SECRET_KEY` from your CI's secret store. - **stdin**: `--secret-stdin` reads the first line of stdin, which keeps the secret out of the process list and shell history: ```bash pass show blazium/deploy-secret | chauffeur --secret-stdin info ``` - **`--secret`**: works, but any user on the machine can read command-line arguments, so chauffeur prints a warning. Avoid it on shared machines and in CI logs. chauffeur never prints the secret, including in error messages and `--json` output. ## Rotating the key Issue a new deploy key on the **Deploy keys** tab or with MCP `request_deploy_key`. Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. `request_deploy_key` returns both values once, after the project owner approves. The access token can be copied later from the Deploy keys tab. The secret cannot. Rotate the key if it may have leaked, when someone with access leaves the project, or on a schedule. ## Checking a key ```bash chauffeur info ``` prints the game the key belongs to, its store URL, what still blocks a public listing, and the upload limits. A rejected key exits with code `2` and error `4025`. The game owner's email must be verified before uploads are accepted (`4096`). # docs/cli/bugs.md # Bug reports `chauffeur bugs` uses the game's deploy key. It lists that game's tickets and can save the screenshot and the full log. It cannot change a ticket's status, and it cannot read crash dumps. ```bash chauffeur bugs chauffeur bugs --status open chauffeur bugs --page 2 chauffeur bugs screenshot bug_123 --out shot.png chauffeur bugs log bug_123 --out game.log chauffeur bugs pull bug_123 --dir ./bugs ``` `--json` prints the list. With no `--page`, chauffeur follows `next_page` until the list ends. The log command walks every page and writes one file. The screenshot command downloads the image bytes. `pull` writes both when they exist. MCP does not download these files. `request_bug_screenshot` returns a one-hour link, and `get_bug_log` returns one page of at most 16 KiB. See [In-game bug reporter](../bug-reporter.md). # docs/cli/ci.md # CI Store the deploy key as two secrets, `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY`, and expose them as environment variables to the job. Never print them or pass them with `--secret`. ## GitHub Actions One job per platform, on every `v*` tag: ```yaml name: Deploy to Blazium Games on: push: tags: ["v*"] jobs: deploy: runs-on: ubuntu-latest strategy: matrix: include: - { os: windows, arch: x86_64, export: export/windows } - { os: linux, arch: x86_64, export: export/linux } - { os: macos, arch: universal, export: export/macos } env: BLAZIUM_ACCESS_TOKEN: ${{ secrets.BLAZIUM_ACCESS_TOKEN }} BLAZIUM_SECRET_KEY: ${{ secrets.BLAZIUM_SECRET_KEY }} VERSION: ${{ github.ref_name }} steps: - uses: actions/checkout@v4 - name: Install chauffeur run: | curl -fsSL -o chauffeur.zip https://cdn.blazium.online/tools/chauffeur/linux-amd64/latest/archive/default unzip -o chauffeur.zip chauffeur && chmod +x chauffeur ./chauffeur info - name: Register the build run: ./chauffeur build --asset build.yml --os ${{ matrix.os }} --arch ${{ matrix.arch }} --json > build.json # Export the game into ${{ matrix.export }} here, writing the build_id # from build.json into the crash reporter settings first. - name: Upload files and symbols run: | ./chauffeur setfiles --version "${VERSION#v}" --os ${{ matrix.os }} --arch ${{ matrix.arch }} --files ${{ matrix.export }} ./chauffeur addfiles --asset addfiles.yml --symbols build/symbols --json > files.json ``` `build.yml` must have the same `version` as the tag (without the `v`) so `addfiles` finds the build that `build` registered. `jq -r '.builds[0].build_id' build.json` reads the `build_id`. ## GitLab CI Add `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY` as masked, protected CI/CD variables. ```yaml deploy: image: debian:stable-slim rules: - if: $CI_COMMIT_TAG before_script: - apt-get update && apt-get install -y curl unzip jq - curl -fsSL -o chauffeur.zip https://cdn.blazium.online/tools/chauffeur/linux-amd64/latest/archive/default - unzip -o chauffeur.zip chauffeur && chmod +x chauffeur script: - ./chauffeur setfiles --version "${CI_COMMIT_TAG#v}" --os linux --arch x86_64 --files export/linux - ./chauffeur addfiles --asset addfiles.yml --json | tee files.json - echo "BLAZIUM_GAMES_BUILD_ID=$(jq -r '.builds[0].build_id' files.json)" >> build.env artifacts: reports: dotenv: build.env ``` ## Any shell ```bash #!/usr/bin/env bash set -euo pipefail : "${BLAZIUM_ACCESS_TOKEN:?}" "${BLAZIUM_SECRET_KEY:?}" version="$1" ./chauffeur setfiles --version "$version" --os linux --arch x86_64 --files export/linux if ! out=$(./chauffeur addfiles --asset addfiles.yml --json); then echo "$out" | jq -r '.error, .hint // empty' >&2 exit 1 fi echo "$out" | jq -r '.builds[0].build_id' ``` ## JSON output With `--json`, chauffeur prints exactly one JSON object on stdout; progress and warnings go to stderr. `build` and `addfiles` print: ```json { "ok": true, "builds": [ { "build_id": "5f1c2d3e-0000-4000-8000-000000000000", "app_id": "0a1b2c3d-0000-4000-8000-000000000000", "os": "windows", "arch": "x86_64", "channel": "stable", "file_uid": "…", "checksum": "…", "symbols": 3 } ] } ``` `file_uid` and `checksum` come from `addfiles`, and `symbols` is the number of symbol files uploaded. `build` with media also includes a `media` object. On failure: ```json { "ok": false, "exit_code": 2, "error": "API error [4096]: …", "code": 4096, "status": 403, "hint": "the game owner must verify their email on blazium.games before uploading." } ``` `code`, `status` and `hint` are present for API errors. Check the exit code as well as `ok`; see [exit codes](./index.md#exit-codes). ## Crash reporter IDs The crash reporter needs the game uid as `X-App-Id` and the build's `build_id` as `X-Build-Id`. Every `build` and `addfiles` run prints them as: ```text BLAZIUM_GAMES_APP_ID=0a1b2c3d-… BLAZIUM_GAMES_BUILD_ID=5f1c2d3e-… ``` Register the build before exporting so the export can include its `build_id`: in Blazium Engine, set `application/crash_reporter/app_id` and `build_id` in the export's project settings. Each OS, arch and channel is a separate build with its own `build_id`. See [Crash reporting](../crash-reporting.md). # docs/cli/commands.md # Commands Every command also takes the [global flags](./index.md#global-flags) (`--access`, `--secret-stdin`, `--url`, `--upload`, `--json`). `chauffeur --help` prints the same reference, and `chauffeur gendocs --dir ` writes it as Markdown so it always matches your binary. ## Builds and files ### `chauffeur build` Create builds from a `build.yml` (one `build_id` per platform), with release notes, and optionally upload symbols and store images. ```bash chauffeur build --asset build.yml [flags] ``` | Flag | Meaning | |------|---------| | `--asset` | Path to build.yml (required) | | `--os`, `--arch`, `--channel` | Replace the file's platforms with this one (`--arch` defaults to `x86_64`) | | `--app`, `--app-name` | The [app](./configuration.md#apps) the build belongs to, overriding the file. Default: the main app | | `--engine-version` | Engine version, like `4.3` or `4.3.0-beta.2` | | `--symbols` | A `.sym` file, a folder of `.sym` files, or a `.zip` to upload for the build (needs a single platform) | ```bash chauffeur build --asset build.yml chauffeur build --asset build.yml --os windows --arch x86_64 --symbols build/symbols chauffeur build --asset build.yml --engine-version 4.3 --json ``` ### `chauffeur addfiles` Zip, checksum and upload one platform's files from an `addfiles.yml`. It adds them to the matching build, or creates the build if none matches. See [Uploads](./uploads.md) for how large files are sent. ```bash chauffeur addfiles --asset addfiles.yml [flags] ``` | Flag | Meaning | |------|---------| | `--asset` | Path to addfiles.yml (required) | | `--os`, `--arch`, `--channel` | Override the file's platform | | `--app`, `--app-name` | Override the file's [app](./configuration.md#apps) | | `--engine-version` | Engine version, used when the build is created | | `--symbols` | Symbols to upload for the build after the files | ```bash chauffeur addfiles --asset addfiles.yml chauffeur addfiles --asset addfiles.yml --os linux --arch arm64 --channel beta chauffeur addfiles --asset addfiles.yml --symbols build/game.sym --json ``` ### `chauffeur genbuild` Write a starter `build.yml` in the current folder. | Flag | Meaning | |------|---------| | `--version` | Build version (default `0.0.1`, up to 32 characters) | | `--engine-version` | Engine version | | `--app`, `--app-name` | Write this [app](./configuration.md#apps) into the file | | `--images` | Folder of gallery images (PNG, JPEG, GIF, WebP) to add to `media.gallery` | ```bash chauffeur genbuild --version 1.0.0 --engine-version 4.3 --images art/screenshots ``` ### `chauffeur addchangelog` Append a changelog entry to `build.yml` in the current folder (up to 100 entries). ```bash chauffeur addchangelog --title "Fixed saves" --description "Saves no longer corrupt on exit." ``` Both `--title` and `--description` are required. ### `chauffeur setfiles` Write a starter `addfiles.yml` in the current folder. | Flag | Meaning | |------|---------| | `--files` | Folder whose files are all added | | `--os` | Default `windows` | | `--arch` | Default `x86_64` | | `--channel` | Default `stable` | | `--version` | Default `0.0.1` | | `--type` | Build type (default `game`) | | `--engine-version` | Engine version | | `--app`, `--app-name` | Write this [app](./configuration.md#apps) into the file | | `--symbols` | Symbols path to record in the file | ```bash chauffeur setfiles --files build/windows --os windows --arch x86_64 --version 1.0.0 chauffeur setfiles --files build/linux --os linux --symbols build/symbols ``` ## Symbols ### `chauffeur symbols` Upload Breakpad `.sym` files for a build so its crash reports show function names and lines. See [Symbols](./symbols.md). ```bash chauffeur symbols --build-id ``` ```bash chauffeur symbols --build-id 5f1c2d3e-0000-4000-8000-000000000000 build/game.sym chauffeur symbols --build-id "$BLAZIUM_GAMES_BUILD_ID" build/symbols/ ``` ## Store images All `media` commands act on the game that owns the deploy key. See [Store images](./media.md) for sizes and rules. | Command | What it does | |---------|--------------| | `chauffeur media list` | Show the cover, thumbnail and gallery with each image's uid | | `chauffeur media cover ` | Replace the cover | | `chauffeur media thumbnail ` | Replace the thumbnail | | `chauffeur media add ... [--position N]` | Add 1 to 10 gallery images, appended or inserted at index `N` (0 is first) | | `chauffeur media delete ` | Delete a gallery image, or clear the cover or thumbnail | | `chauffeur media move --to N` | Move one gallery image to index `N` | | `chauffeur media order ...` | Set the whole gallery order; list every gallery uid once | ```bash chauffeur media list --json chauffeur media cover art/cover.png chauffeur media add shots/*.png --position 0 chauffeur media move 5f1c2d3e-0000-4000-8000-000000000000 --to 2 ``` ## Game info ### `chauffeur info` Show the game the deploy key belongs to: name, store URL, visibility, what still blocks a public listing, images, build count, channels, and the service's upload limits. Use it to check a key before a CI run. ```bash chauffeur info chauffeur info --json ``` ### `chauffeur bugs` List bug reports for this deploy key's game. `--status` keeps one of `open`, `fixed`, `unidentified`, or `closed`. `--page` reads one page; otherwise every `next_page` is followed. The key cannot change status. ```bash chauffeur bugs chauffeur bugs screenshot bug_123 --out shot.png chauffeur bugs log bug_123 --out game.log chauffeur bugs pull bug_123 --dir ./bugs ``` See [Bug reports](./bugs.md). ### `chauffeur builds list` List the game's builds, newest first, with their files and how many symbol files each has. | Flag | Meaning | |------|---------| | `--version` | Only this version (exact match) | | `--os`, `--arch`, `--channel` | Only this platform or channel | | `--page` | Page number, 1 to 10,000 (default 1) | | `--page-size` | Builds per page, 1 to 100 (default 20) | ```bash chauffeur builds list chauffeur builds list --os windows --channel beta chauffeur builds list --version 1.2.0 --json ``` ## Scripted lobbies Turn the lobby on, choose relay or scripted, and switch TURN. Pass at least one of `--enabled`, `--type`, or `--ice`: ```bash chauffeur lobby set --enabled true --type scripted chauffeur lobby set --ice false chauffeur lobby publish --dir . chauffeur lobby list chauffeur lobby status ``` See [Multiplayer](../multiplayer.md). ## Progress `chauffeur progress apply --file progress.yml` replaces each section the file includes: `achievements`, `stats`, `funnels`, and `presence_writers`. A missing section is left as it is. The file starts with `spec: progress`. `chauffeur progress show` prints the current definitions. `--json` works on both. Server keys are not in this file. See [Progress](../progress.md). ## Blog `chauffeur blog` lists published posts, newest first. `chauffeur blog show ` prints the title and the markdown. Both call the public articles API and do not need a deploy key. `--json` works on both. ```bash chauffeur blog chauffeur blog show pardon-our-dust ``` ## Patrons These commands use the signed-in account token (`BLAZIUM_USER_TOKEN` or `--user-token`), not a deploy key. ```bash chauffeur patron status chauffeur patron list chauffeur patron get chauffeur patron tiers chauffeur patron tier create --name Supporter --rank 1 --price-cents 500 --billing monthly chauffeur patron tier update --name Supporter --price-cents 700 --active true chauffeur patron tier delete chauffeur patron posts chauffeur patron post create --title Hello --body "A note" --status published --visibility public chauffeur patron post update --title Hello --visibility tiers --tier chauffeur patron post delete ``` Rank, billing, and unlock stay fixed after a tier is created. `--active false` hides a tier that still has members. ## Shell completion `chauffeur completion bash|zsh|fish|powershell` prints a completion script. For example, `chauffeur completion powershell | Out-String | Invoke-Expression`. ## What chauffeur doesn't do Promoting builds between channels, rolling back, changing prices and editing store page text happen on the website or through [MCP](../mcp/index.md). A deploy key can't do them. # docs/cli/configuration.md # Configuration chauffeur reads two YAML files. `build.yml` registers builds and their release notes, and can upload symbols and store images. `addfiles.yml` uploads the files of one platform build. `chauffeur genbuild` and `chauffeur setfiles` write starter versions. Both files start with: | Key | Value | |-----|-------| | `version` | `v1` (the only version) | | `spec` | `build` or `addfiles` | | `asset` | The fields below | Everything is validated locally before chauffeur sends anything; a bad value exits with code `1`. ## Platform values | Field | Allowed values | |-------|----------------| | `os` | `windows`, `macos`, `linux`, `android`, `ios`, `web`, `any`. `darwin`, `mac` and `osx` mean `macos`; `win`, `win32` and `win64` mean `windows`. Use `any` for files that work on every platform, such as a content pack | | `arch` | `x86_64`, `x86`, `arm64`, `arm32`, `arm`, `universal`, `wasm32`, `wasm`. `amd64` and `x64` mean `x86_64`; `aarch64` means `arm64` | | `channel` | 1 to 32 lowercase letters, digits, `-` or `_`, starting with a letter or digit. Default `stable` | ## Apps One project can ship more than one app, for example the game plus a dedicated server or a level editor. Each app has its own builds and its own channels, and the store page groups downloads by app ("Download Server for Windows"). Leave `app` out for the project's main app; existing files keep working unchanged. | Key | Type | Limit and notes | |-----|------|-----------------| | `app.id` | string | 1 to 32 lowercase letters, digits or `-`, starting with a letter or digit, for example `server` | | `app.name` | string | Optional display name on the downloads, up to 80 characters. Needs `app.id` | `--app` and `--app-name` on `build`, `addfiles`, `genbuild` and `setfiles` set the same values, and on `build` and `addfiles` they override the file. A build is only matched and reused within its own app, and a `build_id` from another app is refused. Clean files of a non-main app are stored as `----.zip`. Optional downloads for a game, such as track packs, models or soundtracks, are an app with `os` set to `any`. They sit next to the game's downloads, show as "All platforms" on the store page, and are not counted as a platform or as a playable build: ```bash chauffeur setfiles --version 1.0.0 --app tracks --app-name "Track Pack" --os any --arch universal --files ./export/tracks ``` ```yaml version: v1 spec: addfiles asset: type: game version: 1.2.0 app: id: server name: Dedicated server os: linux arch: x86_64 channel: stable files: - file: export/server/MyGameServer.x86_64 ``` A tool that is its own product, such as a mod manager sold separately, is better as its own [listing](../listings.md#listing-types) of type `tool` with the game as its parent. ## build.yml (`spec: build`) | Key | Type | Required | Limit and notes | |-----|------|----------|-----------------| | `title` | string | yes | Up to 255 characters. Shown as the release title | | `type` | string | yes | Build type, usually `game`. `asset_type` is an old name for it and prints a warning | | `description` | string | yes | Up to 10,000 characters | | `version` | string | yes | Up to 32 characters, for example `1.2.0` | | `engine_version` | string | no | Blazium or Godot version the build was made with: `4.3`, `4.3.1` or `4.3.0-beta.2`. Used by [mod compatibility](../listings.md#works-with) | | `platforms` | list | no | Each item has `os` (required), `arch` (default `x86_64`) and `channel`. Each platform becomes its own build with its own `build_id` | | `os`, `arch`, `channel` | string | no | A single platform, instead of `platforms` | | `app` | map | no | `id` and `name` of the [app](#apps) the build belongs to. Default: the main app | | `video` | string | no | Trailer or demo URL: `http` or `https`, up to 255 characters | | `changelog` | list | no | Up to 100 items, each with `title` and `description` | | `symbols` | string | no | A `.sym` file, a folder of `.sym` files, or a `.zip`. Needs exactly one platform. See [Symbols](./symbols.md) | | `media.cover` | string | no | Image path. Replaces the cover | | `media.thumbnail` | string | no | Image path. Replaces the thumbnail | | `media.gallery` | list | no | Image paths added to the gallery. With `images`, at most 20 | | `images` | list | no | Older name for `media.gallery` | The `--os`, `--arch` and `--channel` flags of `chauffeur build` replace the file's platforms with one, which suits a CI matrix. `--engine-version` and `--symbols` override the file. Registering the same version, type, app, OS, arch and channel again updates that build: its title, description and changelog are replaced by the file's. ```yaml version: v1 spec: build asset: title: "1.2.0: Winter update" type: game description: "Snow levels, controller rebinding, and save fixes." version: 1.2.0 engine_version: "4.3" platforms: - os: windows arch: x86_64 channel: stable - os: linux arch: x86_64 channel: stable video: https://www.youtube.com/watch?v=example changelog: - title: "Snow levels" description: "Three new levels in the north." - title: "Fixed saves" description: "Saves no longer corrupt on exit." media: cover: art/cover.png thumbnail: art/thumbnail.png gallery: - art/shot1.png - art/shot2.png ``` ## addfiles.yml (`spec: addfiles`) | Key | Type | Required | Limit and notes | |-----|------|----------|-----------------| | `type` | string | yes | Build type, usually `game` | | `version` | string | yes | Up to 32 characters | | `os` | string | yes | See [platform values](#platform-values) | | `arch` | string | yes | See [platform values](#platform-values) | | `channel` | string | yes | See [platform values](#platform-values) | | `app` | map | no | As in build.yml | | `engine_version` | string | no | As in build.yml. Used only when `addfiles` creates the build | | `symbols` | string | no | Symbols to upload for this build after the files | | `files` | list | yes | Each item is `file: `. The files are zipped (up to 5 GB zipped) with their folders kept | If a build with the same version, type, app, OS, arch and channel exists, for example from `chauffeur build`, the files are added to it and its notes are kept. Otherwise `addfiles` creates the build, titled ` /`. ```yaml version: v1 spec: addfiles asset: type: game version: 1.2.0 os: windows arch: x86_64 channel: stable symbols: build/symbols files: - file: export/windows/MyGame.exe - file: export/windows/MyGame.pck ``` `chauffeur setfiles --files export/windows --os windows --arch x86_64 --version 1.2.0` writes this file with every file in the folder. # docs/cli/index.md # chauffeur CLI `chauffeur` is the Blazium Games upload tool. Source: [blazium-games/games_cli](https://github.com/blazium-games/games_cli). Everything that sends files to the store goes through it or the [upload API](../deploy.md#2b-upload-with-the-api): builds, per-platform files, Breakpad debug symbols and store page images. The [developer MCP server](../mcp/index.md) can list and delete these but never uploads them. The website can also upload store page images (cover, thumbnail and gallery) on the game's edit page. Scripted lobby packs are published with `chauffeur lobby publish`. `chauffeur lobby set` turns the lobby on, chooses relay or scripted, and switches TURN. See [Multiplayer](../multiplayer.md). Achievement, stat, funnel, and presence lists are uploaded with `chauffeur progress`. See [Progress](../progress.md). Bug reports for the same game are listed with `chauffeur bugs`, which also saves the screenshot and the full log. See [Bug reports](./bugs.md). Agents that ship a build use the `blazium-games-deploy` skill from `npm install @blazium-games/skills`. Store pages and deploy keys use `blazium-games-store-page` and `blazium-games-keys`. chauffeur authenticates with the game's [deploy key](./authentication.md), so it runs the same way on your machine and in CI. ## Install ```bash npm install -g @blazium-games/cli chauffeur --version ``` The package is `@blazium-games/cli`. The command is `chauffeur`. You can still download the zip for your platform. Each one contains the `chauffeur` binary and a `VERSION` file. | Platform | Archive | |----------|---------| | Windows x86_64 | `https://cdn.blazium.online/tools/chauffeur/windows-amd64/latest/archive/default` | | Linux x86_64 | `https://cdn.blazium.online/tools/chauffeur/linux-amd64/latest/archive/default` | | Linux arm64 | `https://cdn.blazium.online/tools/chauffeur/linux-arm64/latest/archive/default` | | macOS Apple silicon | `https://cdn.blazium.online/tools/chauffeur/darwin-arm64/latest/archive/default` | | macOS Intel | `https://cdn.blazium.online/tools/chauffeur/darwin-amd64/latest/archive/default` | To pin a version, replace `latest` with the version number from a `VERSION` file. Linux and macOS: ```bash curl -fsSL -o chauffeur.zip https://cdn.blazium.online/tools/chauffeur/linux-amd64/latest/archive/default unzip -o chauffeur.zip chauffeur && chmod +x chauffeur ./chauffeur --version ``` Windows (PowerShell): ```powershell Invoke-WebRequest -Uri https://cdn.blazium.online/tools/chauffeur/windows-amd64/latest/archive/default -OutFile chauffeur.zip Expand-Archive -Force chauffeur.zip . .\chauffeur.exe --version ``` On macOS, a binary downloaded with a browser may be quarantined. Remove the flag with `xattr -d com.apple.quarantine chauffeur`. ## Quickstart Get a deploy key from your game's edit page (**Deploy keys** tab) and export it, then: ```bash export BLAZIUM_ACCESS_TOKEN=... # access token; it stays on the Deploy keys tab export BLAZIUM_SECRET_KEY=... # secret; shown once, and it cannot be shown again chauffeur info # 1. check the key and see what the listing still needs chauffeur genbuild --version 1.0.0 # 2. write build.yml, then edit its title and description chauffeur build --asset build.yml --os windows --arch x86_64 # 3. register the build with its release notes chauffeur setfiles --files ./export/windows --os windows --arch x86_64 --version 1.0.0 # 4. write addfiles.yml chauffeur addfiles --asset addfiles.yml # 5. zip and upload the files to that build ``` Add release notes before step 3 with `chauffeur addchangelog --title "Launch" --description "First public build"`. You can skip steps 2 and 3: `addfiles` creates the build itself when none matches, titled after its version and platform. `build` and `addfiles` print the `build_id` as `BLAZIUM_GAMES_BUILD_ID`. Put it in your game's crash reporter settings (see [Crash reporting](../crash-reporting.md)) and upload the build's [debug symbols](./symbols.md). The game owner's email must be verified before any upload is accepted. ## Global flags | Flag | Meaning | |------|---------| | `--access` | Deploy key access token; overrides `BLAZIUM_ACCESS_TOKEN` | | `--secret-stdin` | Read the deploy key secret from the first line of stdin | | `--secret` | Deploy key secret. Visible to other processes, so chauffeur warns; prefer the environment or `--secret-stdin` | | `--url` | API base URL; overrides `BLAZIUM_API_URL` (default `https://api.blazium.online/api/v1`) | | `--upload` | Upload service base URL; overrides `BLAZIUM_UPLOAD_URL` (default `https://uploader.blazium.online/api/v1`) | | `--json` | Print the result, or the error, as one JSON object on stdout. Progress goes to stderr | | `--version` | Print the version | ## Exit codes | Code | Meaning | |------|---------| | `0` | Success | | `1` | Usage or validation error. Nothing was sent | | `2` | The API rejected the request. The message includes the error code and a hint | | `3` | Network error after retries | ## Next - [Authentication](./authentication.md): deploy keys and where chauffeur reads them from - [Configuration](./configuration.md): the `build.yml` and `addfiles.yml` schema - [Commands](./commands.md): every command and flag - [Uploads](./uploads.md), [Store images](./media.md), [Symbols](./symbols.md), [CI](./ci.md), [Troubleshooting](./troubleshooting.md) # docs/cli/media.md # Store images `chauffeur media` manages the store page images of the game that owns the deploy key. The website's Settings and Images tabs can also change them. ## Image rules | Rule | Value | |------|-------| | Formats | PNG, JPEG, GIF, WebP. The type is read from the file's contents, not its extension | | Thumbnail | 960x540 to 1920x1080, 16:9, up to 5 MB. 1280x720 recommended | | Cover | 1024x576 to 2048x1152, 16:9, up to 8 MB. 1024x576 recommended | | Screenshot | 1280x720 to 2048x1152, 16:9, up to 10 MB. 1920x1080 recommended | | Gallery | Up to 20 screenshots; up to 10 per `media add` | | Changes | Up to 60 image changes per game per hour | 16:9 means the width divided by the height is between 1.70 and 1.85. The account avatar is a separate upload: 256x256 to 512x512, square (0.95 to 1.05), up to 2 MB. chauffeur checks the format and size locally before uploading. A public listing needs a cover, a thumbnail and at least 4 gallery images to pass the [listing check](../listings.md#listing-check). ## Commands ```bash chauffeur media list # cover, thumbnail and gallery with uids chauffeur media cover art/cover.png # replace the cover chauffeur media thumbnail art/thumb.png # replace the thumbnail chauffeur media add shot1.png shot2.png # append to the gallery chauffeur media add hero.png --position 0 # insert first; the rest shift down chauffeur media move --to 2 # move one image chauffeur media order # set the whole order chauffeur media delete # remove a gallery image chauffeur media delete thumbnail # clear the thumbnail (not on public listings) ``` `media order` must list every gallery uid exactly once (`4154` otherwise). Positions start at 0. ## Replace, don't delete, on public listings A public listing can't clear its cover or thumbnail (`4153`). Upload a replacement with `media cover` or `media thumbnail` instead. Gallery images can be deleted, but a public listing with fewer than 4 fails the listing check. It then stays public for a grace period before becoming link-only. ## From build.yml `chauffeur build` can set images at the same time as a release: ```yaml asset: media: cover: art/cover.png thumbnail: art/thumbnail.png gallery: - art/shot1.png - art/shot2.png ``` The cover and thumbnail replace the current ones; gallery images are appended. ## Errors | Code | Meaning | |------|---------| | `4150` | Invalid request; `kind` must be `cover`, `thumbnail` or `gallery` | | `4151` | Not a PNG, JPEG, GIF or WebP, or outside that slot's size, shape or file size | | `4152` | The gallery already has 20 images; delete one first | | `4153` | A public listing needs its cover and thumbnail; replace them instead | | `4154` | The order doesn't list every gallery uid exactly once | | `4290` | Too many image changes this hour | # docs/cli/symbols.md # Symbols A crash dump from a release build only has memory addresses. Breakpad symbol files (`.sym`) map those addresses back to function names, source files and line numbers. Upload them for a build and every crash from that build is stackwalked with them. Symbols are private. Only the game's owner and admins can list or delete them: on the **Builds** tab (open **Symbols and bundle check** under a build) or with MCP `list_build_symbols` and `delete_build_symbols`. Uploading is only possible with chauffeur and the game's deploy key. ## 1. Build with debug information The binary you ship can be stripped, but you need the debug information from the same build to make symbols: - **Windows**: the `.pdb` written next to the `.exe` by an export template built with debug symbols. - **Linux and Android**: an unstripped binary, or the separate debug file (`.debug`) from `strip --only-keep-debug`. - **macOS and iOS**: the `.dSYM` bundle. For Blazium and Godot, use export templates built with debug symbols (for example `debug_symbols=yes`, and `separate_debug_symbols=yes` to keep them out of the shipped binary). Symbols must come from the exact binary you ship; a rebuild of the same source won't match. ## 2. Make .sym files Use `dump_syms`. Mozilla's version runs on every desktop OS and reads PDB, ELF and Mach-O files: ```bash cargo install dump_syms ``` ```bash # Windows (from the .pdb or the .exe next to it) dump_syms MyGame.pdb > symbols/MyGame.sym # Linux dump_syms MyGame.x86_64 > symbols/MyGame.sym # macOS dump_syms MyGame.app/Contents/MacOS/MyGame.dSYM > symbols/MyGame.sym ``` Each file must start with a Breakpad `MODULE` line, like `MODULE windows x86_64 3F2A...1 MyGame.pdb`. chauffeur checks this before uploading. ## 3. Upload After `chauffeur build` or `chauffeur addfiles` prints the `build_id`: ```bash chauffeur symbols --build-id "$BLAZIUM_GAMES_BUILD_ID" symbols/ ``` The path can be one `.sym` file, a folder (searched recursively for `.sym` files, which chauffeur zips for you), or a `.zip` of `.sym` files. You can also upload them in the same run as the build, with `--symbols symbols/` on `build` (single platform) or `addfiles`, or `symbols:` in the YAML file. MCP `upload_symbols_info` returns the exact command for a build, and the Builds tab shows it too. ## Limits | Limit | Value | |-------|-------| | One `.sym` file | 512 MB | | Files per upload | 200 | | Unzipped size per upload | 2 GB | | Upload size | 1 GB | | Uploads per game | 30 per hour | | Symbol OS | `windows`, `linux`, `mac`, `ios`, `android` (from the `MODULE` line) | Uploading a symbol file with the same module and debug id again replaces it. ## Errors | Code | Meaning | |------|---------| | `4038` / `4039` | The `build_id` is missing, or isn't a build of this deploy key's game | | `4043` | A file or the upload is over its size limit | | `4049` | Not a Breakpad `.sym` file (no `MODULE` line), an unsupported OS, or a `.zip` with something else inside | | `4290` | Too many symbol uploads this hour | ## Delete On the Builds tab, open **Symbols and bundle check** under the build and use **Delete** or **Delete all symbols**. Over MCP, `delete_build_symbols` removes one file when you pass a `symbol_uid`, or all of the build's files without one. # docs/cli/troubleshooting.md # Troubleshooting chauffeur prints the API's error code with a hint, for example: ```text API error [4041]: Invalid os hint: os, arch, channel, checksum or filename is invalid. os: windows, macos, linux, android, ios, web; ... ``` With `--json` the same information is in `code`, `error` and `hint`. ## Exit codes | Code | Meaning | What to do | |------|---------|------------| | `1` | Usage or validation error; nothing was sent | Fix the flag or YAML value named in the message | | `2` | The API rejected the request | Look up the code below | | `3` | Network error after retries | Check connectivity and proxies, then run it again | ## Error codes | Code | Cause | Fix | |------|-------|-----| | `4020` / `4021` | The access token or secret didn't reach the API | Set `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY` in the step that runs chauffeur | | `4022` / `4023` | The deploy key wasn't found, or was revoked by a newer key | Issue a new key and update your secrets | | `4025` | The deploy key was rejected: wrong, or replaced by a newer key | Check `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY`, or issue a new key and update your secrets | | `4026` | A build field is missing or too long | `version` up to 32 characters, `title` 255, `description` 10,000, `changelog` 100 items, `demo_url` an http(s) URL up to 255, `engine_version` like `4.3` | | `4037` | The upload form couldn't be read | Update chauffeur; the file must come after the form fields | | `4038` / `4039` | The build is missing or belongs to another game | Pass the `build_id` printed by `chauffeur build` for this game | | `4041` | Invalid `os`, `arch`, `channel`, checksum or file name | See [platform values](./configuration.md#platform-values); build files must be `.zip` | | `4043` | Too large | 5 GB per build file, 512 MB per symbol file, 1 GB per symbol upload | | `4044` | A chunk doesn't continue the upload, or the server couldn't write it | chauffeur resumes from the server's position on its own; if it keeps failing, run the command again | | `4045` | The upload session expired (6 hours) or wasn't found | chauffeur opens a new session and uploads the file again, up to 3 times; if it still fails, run the command again | | `4046` | Checksum mismatch | Make sure nothing writes to the files during the upload, then retry | | `4047` | Another chunk of the same upload is still in progress | Don't run the same upload twice at once; retry when the first finishes | | `4049` | Not a Breakpad `.sym` file, or a `.zip` with other files | See [Symbols](./symbols.md) | | `4096` | The game owner's email isn't verified | Verify it at [blazium.games/settings/verify](https://blazium.games/settings/verify) | | `4150` to `4154` | Store image problems | See [Store images](./media.md#errors) | | `4166` | A `builds list` filter is invalid | Use the values in [platform values](./configuration.md#platform-values) | | `4290` | Rate limited | Wait, then run it again. See [limits](./uploads.md#limits) | | `4291` | Too many open upload sessions (8) | Wait for one to finish or expire | | `5xx` | Server error | chauffeur retries chunks with backoff; if it still fails, try again later | ## Common problems **`the deploy key secret is missing`.** `BLAZIUM_SECRET_KEY` isn't set in this shell or CI step. In GitHub Actions, secrets aren't available to workflows from forks. **The release notes disappeared after `addfiles`.** Older versions of chauffeur registered the build again, which replaced its notes. Update chauffeur, and make sure `build.yml` and `addfiles.yml` use the same `version`, `type`, `os`, `arch` and `channel`. **`os "darwin" is not supported`.** Update chauffeur; `darwin`, `amd64` and `aarch64` are accepted as `macos`, `x86_64` and `arm64`. **Uploads through a proxy.** chauffeur honours `HTTPS_PROXY` and `NO_PROXY`. A proxy that buffers whole requests may time out on large chunks; exempt `uploader.blazium.online` if you can. **An upload failed while the upload service was being updated.** Chunked upload sessions survive restarts of the service. chauffeur retries failed chunks with backoff and carries on from where the server stopped, so a large upload usually finishes on its own. If it gave up, run the same command again. **A file stays `pending` or `scanning`.** Scans usually finish within minutes, longer for multi-GB files. Check the Builds tab or `chauffeur builds list`. An `infected` or `error` result removes the file and lists it under **Rejected uploads**. **macOS says the binary can't be opened.** Run `xattr -d com.apple.quarantine chauffeur`. **Windows SmartScreen warns about the binary.** Choose **More info** and **Run anyway**, or download it with PowerShell as shown in [Install](./index.md#install). # docs/cli/uploads.md # Uploads ## Single and chunked uploads `chauffeur addfiles` zips the listed files and computes the zip's SHA-256 checksum. Then: - **Up to 64 MB**: one streamed request. - **Over 64 MB**: an upload session, sent in 16 MB chunks. Either way chauffeur streams from disk, so memory use stays flat even for a 5 GB file. In a session, each chunk that fails because of a dropped connection, a rate limit (`429`) or a server error (`5xx`) is retried with exponential backoff, up to 5 tries. If the server says the chunk doesn't continue the upload (`409`), chauffeur resumes from the position the server reports. A session stays open for 6 hours; after that, run the command again. ## Limits | Limit | Value | |-------|-------| | Build file | `.zip` only, up to 5 GB | | Uploads per game | 60 per hour | | Chunks per game | 5,000 per hour | | Open upload sessions per game | 8 | | Symbol uploads per game | 30 per hour; see [Symbols](./symbols.md) for sizes | | Store images | See [Store images](./media.md) | Past a rate limit the API returns `4290` or `4291`. chauffeur retries within a chunk, then stops with exit code `2`; wait and run it again. ## Checksums chauffeur sends the checksum with the upload, and the server recomputes it from the bytes it received. A mismatch (`4046`) means the file changed during the upload or was corrupted on the way. chauffeur doesn't retry it, because sending the same bytes again won't help. ## After the upload 1. The file is stored privately and queued for a virus scan. Its state is `pending`, then `scanning`. 2. A `clean` file becomes downloadable, and the build's channel moves to it if it's newer. Players see a scan badge on the download button. 3. An `infected` file, or one whose scan fails with an `error`, is removed and listed under **Rejected uploads** on the Builds tab for 30 days. The Builds tab on the website, `chauffeur builds list`, and MCP `scan_status` all show the scan state. Every file also records how it was uploaded (the first characters of the deploy key, or the website) and its scan history. Anyone can read that record at `GET /api/v1/public/games/{game_uid}/files/{file_uid}/provenance`. The server also reads the zip's list of files, which powers the [bundle check](../listings.md#bundle-check). # docs/content-rules.md # Content rules These rules come from the [Terms of Service](https://blazium.games/terms-of-service#20-content-ratings-and-adult-content). This page explains how they work on the store. ## Content warnings Set every warning that applies on the **Listing** tab or with `update_game_taxonomy`: violence, gore, sexual, nudity, language, drugs, gambling, horror, flashing_lights. They show on the store page, and players can leave out listings with a warning with the **Content warnings** filter on [Browse](https://blazium.games/browse) (for example **Hide gore**) or `exclude_warnings` in [search](./listings.md#search). ## Adult content Tick **Adult content (sexual content or nudity)** on the **Settings** tab of the edit page, or with `adult: true` on `create_game` or `update_game`, if it contains sexual content or nudity. Add the matching content warnings too. Other mature themes only need their warnings. An adult listing: - Shows only to signed-in players who confirmed they are 18 or older and turned on adult content. Signed-out visitors get a 404 (`4004`); signed-in players who haven't opted in see a page that explains how to turn it on (`4104`, HTTP 403). - Is left out of search, recommendations, and the tools and mods rows of other games for everyone who hasn't opted in, and out of shelves, friends' activity, popular tags, sitemaps, and llms.txt for everyone. It is never indexed by search engines. See [SEO and indexing](./seo-and-indexing.md). - Shows an **18+** badge on its store page. You and your project's admins always see your own adult listings. Content that sexualizes minors, presents non-consensual sexual acts as real, or is otherwise illegal is never allowed, marked adult or not. We may change a listing's rating or warnings, or unlist it, if it is mislabeled. ### Turning on adult content as a player Open [Settings](https://blazium.games/settings#adult), find **Adult content**, tick **I am 18 or older, and adult content is legal where I live**, and click **Show adult content**. Without the confirmation the change is refused (`4108`). **Hide adult content** turns it off again. Over the API: `PUT /api/v1/private/settings/adult` with `{"show": true, "confirm_18": true}`. It returns `show_adult`, `adult_confirmed`, and `sees_adult`. ## Generative AI disclosure Disclose every part of a listing made with generative AI on the **Listing** tab (**Made with generative AI**) or with `ai_uses` on `update_game_taxonomy`: | Value | Store page label | |---|---| | `art` | Art | | `audio` | Music and sound | | `code` | Code | | `text` | Writing | | `voice` | Voices | | `runtime` | Generates content while you play | The store page lists them under **Generative AI**, and players filter by them with `ai_uses` in [search](./listings.md#search). Leaving the disclosure empty says you used no generative AI for those parts, so it must be honest and complete. It is separate from the [made-with label](./listings.md#made-with), which says who made the game. # docs/crash-reporting.md # Crash reporting Games send crashes to `https://api.blazium.online/api/v1/public/crashes`. Reports appear on your game's dashboard and through the MCP tools `list_game_crashes` and `get_crash`. Player-written bug tickets are separate: see [In-game bug reporter](./bug-reporter.md). Crash scopes do not list or update those tickets. Crash ingest needs no secret. It identifies the game with two headers: | Header | Value | |--------|-------| | `X-App-Id` | The game uid | | `X-Build-Id` | The `build_id` of the exact build that crashed (not a version string) | Get both from `get_deploy_info` (`auth.crash_headers`) or `list_game_builds`. Each version, OS, arch, and channel combination is its own build, so write the matching `build_id` into each exported binary. ## Blazium Engine Set these in Project Settings under `application/crash_reporter/`: | Setting | Value | |---------|-------| | `enabled` | `true` | | `upload_mode` | `InEngine`, `Sidecar`, or `Both` | | `endpoint` | `https://api.blazium.online/api/v1/public/crashes` | | `app_id` | The game uid | | `build_id` | The build UID | | `app_version` | The build version | | `build_channel` | `stable`, `beta`, and so on | | `require_user_consent` | `true` (recommended) | | `privacy_policy_url` | Your privacy policy | For the sidecar consent UI, place the [crash reporter](https://github.com/blazium-games/blazium_crash_reporter) binary next to the game executable. Nothing is uploaded until the player confirms. Never put secrets in Project Settings. ## Custom reporter Create the report: ```http POST https://api.blazium.online/api/v1/public/crashes X-App-Id: X-Build-Id: Content-Type: application/json { "has_dump": true, "has_log": true, "app_name": "My Game", "app_version": "1.0.0", "engine_version": "4.8", "os": "windows", "arch": "x86_64", "user_message": "It froze on level 3", "anonymous": true, "metadata": {} } ``` The `201` response contains the report `id` and an `uploads` object with a `dump` and/or `log` entry: | Field | Meaning | |-------|---------| | `url` | Single-use upload URL | | `method` | `PUT` | | `expires_at` | 24 hours after creation | | `max_bytes` | 64 MB | | `filename` | `dump.dmp` or `log.txt` | Upload each file with `PUT` to its `url`, as the raw body or a multipart `file` part. Each game has a daily limit on upload URLs. Past it, the report is still stored but `uploads` is empty. | Code | Meaning | |------|---------| | `4001` | Invalid JSON body | | `4010` | Missing `X-App-Id` or `X-Build-Id` | | `4030` | Unknown app id, or a `build_id` that does not belong to that app | | `4130` | `metadata` has more than 64 keys (`413`) | | `4290` | The game reached its daily crash report limit (`429`); try again tomorrow | ## Custom events ```http POST https://api.blazium.online/api/v1/public/events X-App-Id: X-Build-Id: Content-Type: application/json { "events": [ { "event": "level_complete", "anonymous": true, "device_uid": "" } ] } ``` Send up to 100 events per request; more returns `4130` (`413`). The response is `202`. Use a random per-install id, not a hardware identifier. ## Standard events Six event names have fixed meanings. Send them from every build and your listing gets a [launch health band](./listings.md#launch-health), and new games can appear on the [Unheard of shelf](./listings.md#shelves). | Event | When | Fields | |-------|------|--------| | `session_start` | The game process started | | | `boot_ok` | The first frame of the main menu or first scene rendered | `device_uid` (required), `ms` since start (optional, 0 to 600000) | | `first_input` | The player's first key, click or touch | `ms` since start (optional, 0 to 600000) | | `session_end` | The game is closing normally | `seconds` played this session (required, whole number 0 to 86400) | | `quit` | The player chose to quit | | | `crash` | Sent by the crash reporter, or on the next launch after an unclean exit | `device_uid` (required) | If any standard event in a request has a missing or out-of-range field, the whole request is refused with `4158` and the message names the event's index. A custom name such as `level_complete` is a registered funnel, recorded by the signed-in client, a server key, or the scripted lobby. Unknown names are refused on that route. See [Progress](./progress.md). A `crash` before a device's first `boot_ok` counts as a crash on boot. Health counts devices, so send the same random `device_uid` from every event of one install. A Blazium or Godot autoload can send them: ```gdscript extends Node const ENDPOINT := "https://api.blazium.online/api/v1/public/events" const APP_ID := "" const BUILD_ID := "" var _device_uid := "" var _started_ms := 0 var _input_sent := false func _ready() -> void: _started_ms = Time.get_ticks_msec() _device_uid = _load_device_uid() _send("session_start") await get_tree().process_frame _send("boot_ok", {"ms": _elapsed_ms()}) func _input(event: InputEvent) -> void: if _input_sent or not (event is InputEventKey or event is InputEventMouseButton or event is InputEventScreenTouch or event is InputEventJoypadButton): return _input_sent = true _send("first_input", {"ms": _elapsed_ms()}) func _notification(what: int) -> void: if what == NOTIFICATION_WM_CLOSE_REQUEST: _send("session_end", {"seconds": _session_seconds()}) func quit_game() -> void: _send("quit") _send("session_end", {"seconds": _session_seconds()}) get_tree().quit() func _elapsed_ms() -> int: return mini(Time.get_ticks_msec() - _started_ms, 600000) func _session_seconds() -> int: return mini((Time.get_ticks_msec() - _started_ms) / 1000, 86400) func _load_device_uid() -> String: var path := "user://device_uid" if FileAccess.file_exists(path): return FileAccess.get_file_as_string(path).strip_edges() var uid := Crypto.new().generate_random_bytes(16).hex_encode() FileAccess.open(path, FileAccess.WRITE).store_string(uid) return uid func _send(name: String, fields := {}) -> void: var ev := {"event": name, "anonymous": true, "device_uid": _device_uid} ev.merge(fields) var http := HTTPRequest.new() add_child(http) http.request_completed.connect(func(_r, _c, _h, _b): http.queue_free()) http.request(ENDPOINT, ["Content-Type: application/json", "X-App-Id: " + APP_ID, "X-Build-Id: " + BUILD_ID], HTTPClient.METHOD_POST, JSON.stringify({"events": [ev]})) ``` Set `BUILD_ID` for each export (see [CI](./cli/ci.md#crash-reporter-ids)). Requests sent while the window is closing may not finish; set `get_tree().auto_accept_quit = false` and quit after the request completes if you need every `session_end`. Ask players for consent where your privacy policy requires it. ## Symbols Reports with a minidump are stackwalked with the Breakpad symbols uploaded for their build. Without symbols, stacks only show addresses. Upload them with `chauffeur symbols`; see [Symbols](./cli/symbols.md). ## Crash webhooks Crash ingest stays open and still needs no secret. A separate per-game setting can notify your own receiver. It is off until you turn it on from the listing's **Crash webhooks** tab, or with `get_crash_reporter` and `set_crash_reporter`. `mcp:crash.read` can read the setting and the signing key. `mcp:crash.write` can change the webhooks and refresh the key, and it also covers the read routes. This key is not the bug reporter key. Refreshing one does not break the other. You can store up to five `https` URLs. `http` is allowed only for `localhost`. A Discord webhook URL gets an embed and no file. Every other URL gets JSON. The `signature` field is base64 HMAC-SHA1 of the JSON body before that field is added. `crash_id` is the idempotency key: a later delivery for the same crash can add a URL once that file exists. ```json { "game_uid": "game uid", "game_name": "My Game", "crash_id": "report id", "build_id": "build uid", "app_version": "1.0.0", "os": "windows", "arch": "x86_64", "has_dump": true, "has_log": true, "has_stack": false, "expires": 1760000000, "dump_url": "https://api.blazium.online/api/v1/games//crashes//dump?Expires=1760000000&Signature=...", "log_url": "https://api.blazium.online/api/v1/games//crashes//log?Expires=1760000000&Signature=..." } ``` A URL is included only for a file that is already stored. `dump_url`, `log_url`, and `stack_url` use the same signature as a private object: base64 HMAC-SHA1 of `GET\n\n\n{expires}\n/{path}`, with `path` like `games//crashes//log`. `GET` that URL to download the file. A bad or expired signature is rejected. If the file is not stored yet, the response is not found. A report with no dump and no log is delivered as soon as it is accepted. After a dump or log upload finishes, and again after the stack is stored, the same webhooks are called once more. Each URL is posted up to three times, and a 2xx stops the retries. Turning the setting off, or having no key or no webhooks, skips delivery. The report is still stored. ## Reading crashes With the MCP server connected, ask your agent to list recent crashes. It uses: - `list_crash_groups` for reports grouped by cause, most recently seen first (up to 100 groups), with counts per build - `list_game_crashes` for recent reports - `list_bug_tickets` for bug reports players filed, 50 a page (`next_page`), with a `crash_id` when they attached a dump or log - `get_bug_ticket`, `request_bug_screenshot` (a link, not the image), and `get_bug_log` (one page; follow `next_offset`) - `update_bug_ticket` to mark a player bug report `fixed`, `unidentified`, or `closed`, or reopen it with `open` - `get_crash` for metadata, the player's message, and the stack excerpt - `request_crash_download` with `kind` `stack`, `log`, or `dump` for a private link valid for 1 hour Reports with a minidump are stackwalked on the server, and grouped by their top stack frames. Until then they are grouped by the crash message, app version, and OS. A new report can take a few minutes to join a group. In Cursor, the `blazium-games-debug-crash` skill runs this whole flow and maps the stack to your code. # docs/creators/faq.md # Creator FAQ ## What does it cost? An account is free. A sale or a donation pays a fixed fee of $0.25 plus 8%, taken from the developer. Prices, donations, editions, and patron tiers are on [Pricing](./pricing.md). The fee table is on [Payments](../payments/index.md). ## Who handles tax? Stripe Tax is added for the buyer where Blazium Games is registered. Payout details, including the tax information Stripe asks for, are on [Accepting payments](../payments/index.md) and [Wallet and cash-out](../payments/wallet-and-cash-out.md). ## Who owns the project? You keep ownership of what you upload. The [terms](https://blazium.games/terms-of-service) are the agreement for using the platform. ## Are my files changed before download? Files are served as uploaded. Upload them with [chauffeur](../cli/index.md). The site does not accept build uploads in the browser. ## Can I give someone a copy without a purchase? Yes. [Download keys](../storefront/team-and-keys.md) and [redeem a key](../storefront/redeem-a-key.md) cover that. ## Can I embed the game? A browser build can be embedded. See [Embed](../storefront/embed.md) and [Play in the browser](../web-player.md). ## Can the page be adult? Adult pages stay hidden until a player opts in. The rules are in [Content rules](../content-rules.md). ## What do I see about a buyer? You see sales and download counts, not a buyer's card. [Download analytics](../download-analytics.md) and the dashboard analytics view are the reports. Payment records stay with the [wallet](../payments/wallet-and-cash-out.md). # docs/creators/pricing.md # Pricing An account is free. A project can be free, or it can have a fixed price. A free project can also accept an optional donation. The fee on a sale or a donation is $0.25 plus 8%, taken from the developer. Card fees and tax are shown to the buyer before they pay. Paying from a balance adds nothing extra. See [Payments](../payments/index.md) and [Selling](../payments/selling.md). There is no open revenue share, no pay-any-amount-above-a-minimum, and no separate price per file. ## Editions and bundles A listing can have editions: standard, deluxe, beta access, and a bundle of 1 to 10 of your own listings. Someone who already owns a cheaper edition can pay the difference. Details are on [Selling](../payments/selling.md). ## Patron tiers A page can have up to 12 patron tiers. A higher tier includes the lower tier's games, locked posts, and patron-only sales. Monthly tiers renew by card. A one-time tier is paid by card or from the balance. The fee is the same $0.25 plus 8%. A membership payment is not refundable. Access starts after the 12 hour payment check. The full rules are on [Patron memberships](../payments/patrons.md). Cash-out is USD through Stripe Connect, or USDC on Base or Solana from the wallet page. See [USDC](../payments/wallet-and-cash-out.md#usdc). # docs/cursor-plugin.md # Cursor plugin Blazium Games is a game publishing platform, with an infrastructure focus. The official Cursor plugin teaches an agent to do both. A token belongs to one server. It bundles: - The hosted [Blazium Games MCP server](./mcp/index.md) at `https://mcp.blazium.games/developer` (`https://mcp.blazium.games/mcp` still reaches it), and the [player server](./mcp/player.md) at `https://mcp.blazium.games/player`. Both connect with OAuth, so no key is stored in the plugin. - Skills that walk the agent through store pages, deploys, crash reporting, crash debugging, analytics, keys, playing, and purchases. The docs repo remains the guide and the plugin source: [github.com/blazium-games/games_docs](https://github.com/blazium-games/games_docs) (MIT). The versioned release is [github.com/blazium-games/games_skill](https://github.com/blazium-games/games_skill), published as `npm install @blazium-games/skills`. ## Install 1. Open **Cursor Settings > Plugins**. 2. Add `blazium-games/games_skill`. 3. Enable the **Blazium Games** plugin. 4. Ask the agent something like "Connect to Blazium Games and list my games". Cursor opens a browser for the Blazium Games sign-in and consent page the first time. If you only want the MCP server without skills, use [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=blazium-games&config=eyJ1cmwiOiJodHRwczovL21jcC5ibGF6aXVtLmdhbWVzL21jcCJ9) instead. ## Skills | Skill | What it does | |-------|--------------| | `blazium-games-get-started` | Connects the server, verifies the account, and routes to the right skill | | `blazium-games-store-page` | Creates and edits store pages | | `blazium-games-deploy` | Ships builds from CI or the CLI ([Deploy builds](./deploy.md)) | | `blazium-games-crash-reporting` | Wires crash reports and events into a game ([Crash reporting](./crash-reporting.md)) | | `blazium-games-debug-crash` | Triages crashes and maps them to your code | | `blazium-games-analytics` | Summarizes store page traffic | | `blazium-games-keys` | Inspects and rotates MCP and deploy keys ([Access and keys](./mcp/access-and-keys.md)) | | `blazium-games-player` | Acts for you as a player: recommendations, catalog search, reviews, bug reports, and friends ([Player MCP](./mcp/player.md)) | | `blazium-games-purchases` | Buys games and donates from your balance within your spending limits ([Agent purchases](./payments/agent-purchases.md)) | You only need to sign in to the server you use. The player server asks for its own consent the first time a player skill calls it. The skill index is [SKILL_TREE.md](https://github.com/blazium-games/games_docs/blob/master/SKILL_TREE.md). ## Using an API key instead of OAuth For environments where a browser sign-in is not possible, override the server in your own `~/.cursor/mcp.json`: ```json { "mcpServers": { "blazium-games": { "url": "https://mcp.blazium.games/developer", "headers": { "Authorization": "Bearer bgames_mcp_YOUR_KEY" } } } } ``` Create the key at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). Never commit it. That header is for a client config a person pastes. The agent does not set it. The agent calls `elevate_session`. Do not call the server with Python. ## Read-only use Tick **Read-only access** on the consent page to let the agent read analytics, crashes, and builds without being able to change pages or rotate keys. ## Troubleshooting | Problem | Fix | |---------|-----| | The agent says the server needs authentication | Open Cursor Settings > MCP and reconnect `blazium-games` | | `403` with code `4031` | The connection is read-only. Reconnect without **Read-only access** | | `403` with code `4073` | The connection's preset doesn't cover that tool (for example **CI** can't edit the store page). Reconnect with a broader preset | | `403` with code `4030` | The connection is bound to one project, and the tool is account-level or for another game. Reconnect and choose **Account** | | A result with `approval_required` | The action waits for the account owner. Open the emailed link, then ask the agent to retry | | Skills do not appear | Check the plugin is enabled in Cursor Settings > Plugins | # docs/deploy.md # Deploy builds A deploy has two steps: register a build (version, OS, arch, channel), then upload its files as a zip. Every build gets a `build_id` that crash reporters send as `X-Build-Id`. Uploads go through the [chauffeur CLI](./cli/index.md) or the upload API with the game's deploy key. The website and MCP can list, promote, and delete builds and symbols, but not upload them. ## 1. Get deploy keys A deploy key is two values for one project: an access token and a secret. chauffeur and CI need both. The access token is `BLAZIUM_ACCESS_TOKEN`, sent as `X-Access-Token`. It stays on the Deploy keys tab. The secret is `BLAZIUM_SECRET_KEY`, sent as `X-Secret-Key`. It is shown once. Copy it before you leave the page. It cannot be shown again. Get them from the game's edit page on [blazium.games](https://blazium.games), or ask an agent to call the MCP tool `request_deploy_key`. Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. Issuing them needs [developer mode](./developer-mode.md) (`4105`). :::warning Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. Update your CI values right away. ::: Store them as CI values, for example GitHub Actions secrets `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY`. Never commit them. `get_deploy_info` lists the short code only. It does not include the access token or the secret. It does return every URL below for your game, plus recent builds. The short code in the table is the start of the access token and is not enough to upload. ## 2a. Upload with chauffeur [Install chauffeur](./cli/index.md#install) with `npm install -g @blazium-games/cli`, or from the CDN zip. It reads `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY` from the environment (or `--access` and `--secret-stdin`). ```bash chauffeur genbuild --version 1.0.0 chauffeur addchangelog --title "Launch" --description "First public build" chauffeur build --asset build.yml --os windows --arch x86_64 chauffeur setfiles --version 1.0.0 --os windows --arch x86_64 --files ./export/windows chauffeur addfiles --asset addfiles.yml ``` - `genbuild` writes `build.yml`, and `setfiles` writes `addfiles.yml`. - `build` registers the build and prints its `build_id` as `BLAZIUM_GAMES_BUILD_ID`. The same version, type, OS, arch, and channel update the existing build. - `addfiles` reuses the matching build, zips the files, computes a SHA-256 checksum, and uploads them. Files over 64 MB go up in resumable 16 MB chunks. `build.yml`: ```yaml version: v1 spec: build asset: title: "1.0.0" type: "game" description: "First release" version: 1.0.0 engine_version: "4.3" platforms: - os: windows arch: x86_64 channel: stable changelog: - title: "Launch" description: "First public build" ``` Every command and field is in the [chauffeur CLI](./cli/index.md) section. ## Symbols and store images chauffeur also uploads the files that aren't builds. MCP can list and delete them but never uploads. Symbols only upload through chauffeur and the deploy key; store images can also be uploaded on the game's edit page on the website. ```bash chauffeur symbols --build-id "$BLAZIUM_GAMES_BUILD_ID" ./symbols # Breakpad .sym files chauffeur media cover art/cover.png chauffeur media thumbnail art/thumbnail.png chauffeur media add shots/*.png ``` See [Symbols](./cli/symbols.md) and [Store images](./cli/media.md). ## 2b. Upload with the API Register the build: ```http POST https://api.blazium.online/api/v1/tool/upload/build X-Access-Token: X-Secret-Key: Content-Type: application/json { "version": "1.0.0", "build_type": "game", "os": "windows", "arch": "x86_64", "channel": "stable", "title": "1.0.0", "description": "First release", "changelog_items": [{ "title": "Launch", "description": "First public build" }] } ``` The response includes `build_id`. Then upload the zip: ```http POST https://uploader.blazium.online/api/v1/tool/upload/files X-Access-Token: X-Secret-Key: Content-Type: multipart/form-data build_id=, os=windows, arch=x86_64, channel=stable, checksum=, file=@game.zip ``` - `file` must be a `.zip`, up to 5 GB. Folders inside the zip are kept as they are. - `os` is one of `windows`, `macos`, `linux`, `android`, `ios`, `web`, or `any`. Use `any` with `arch=universal` for files that work everywhere, such as a content pack in its own [app](./cli/configuration.md#apps) (`--app tracks --app-name "Track Pack" --os any`). - `arch` is one of `x86_64`, `x86`, `arm64`, `arm32`, `arm`, `universal`, `wasm32`, or `wasm`. - `channel` is lowercase letters, digits, `-`, and `_`, starting with a letter or digit, up to 32 characters. - `checksum` is the SHA-256 of the zip as 64 hex characters (a `sha256:` prefix is accepted). - Instead of `build_id`, you can send `build` plus `build_type` and `version`. - `app` (and optionally `app_name`) on the registration and the upload targets one [app](./cli/configuration.md#apps) of the project, such as a dedicated server. Leave it out for the main app. A `build_id` of another app is refused. - The game owner must have a verified email before files can be uploaded. ### Chunked uploads For large or unreliable connections, open a session first: ```http POST https://uploader.blazium.online/api/v1/tool/upload/sessions X-Access-Token: X-Secret-Key: Content-Type: application/x-www-form-urlencoded filename=game.zip&total_size=&checksum=&os=windows&arch=x86_64&channel=stable&build_id= ``` The `201` response has `session_id`, `expected_size`, `current_size`, and `expires_at` (6 hours). Then send the chunks in order to `/api/v1/tool/upload/files`, each as a multipart `file` part with `X-Upload-Session-ID: ` and `Content-Range: bytes -/`. Each chunk returns `202` with `current_size` until the last one, which finishes the upload like a single request. After a failed chunk, resume from the `current_size` in the error. Each game can have up to 8 open sessions. Sessions survive restarts of the upload service, so a chunk that fails while the service is being updated can be sent again once it's back. If a chunk gets `4045`, the session has expired or is gone: open a new session and upload from the start. A single request or chunk may take up to 5 minutes plus one second per 512 KB of its size (at most 3 hours) to arrive; use chunks on slow connections. | Code | Meaning | |------|---------| | `4020` / `4021` | Missing `X-Access-Token` or `X-Secret-Key` | | `4022` / `4023` | Deploy key not found, or revoked | | `4024` | Deploy key not found or invalid for this game (`401`) | | `4025` | The request isn't authenticated as a game (`401`) | | `4026` | Missing or too-long field when registering (`version` up to 32 characters, `title` up to 255, up to 100 changelog items) | | `4037` | Missing `file`, or a form that could not be read | | `4038` | Missing build identification | | `4039` | Build not found; register it first | | `4041` | Invalid `checksum`, `os`, `arch`, or `channel`, or the file is not a `.zip` | | `4043` | Larger than 5 GB, or larger than the chunk's `Content-Range` (`413`) | | `4044` | Missing or invalid `X-Upload-Session-ID` / `Content-Range`, or a chunk that does not continue the session or couldn't be written. When the error has `current_size`, resume from there (`400` or `409`) | | `4045` | Upload session not found or expired (`404`); open a new session | | `4046` | Checksum mismatch | | `4047` | Another chunk for the same session is still uploading (`409`) | | `4048` | The file record couldn't be created; try again (`500`) | | `5020` | A symbol file couldn't be stored; try again (`502`) | | `4096` | The game owner has not verified their email | | `4290` / `4291` | Too many uploads, chunks, or open sessions for this game (`429`) | ## Channels Each channel (`stable`, `beta`, `dev`, or your own lowercase name) points at one build, separately for each [app](./cli/configuration.md#apps) of the project. When an upload passes the virus scan, its channel moves to that build if it's newer. Players see the build each channel points at; `beta` only for players who joined the beta on the store page, and `dev` only for you and your game admins. On the **Builds** tab of your game you can promote a build to a channel, set an expiry, roll a channel back to its previous build, and see the history. Over MCP use `list_channels`, `promote_build`, and `rollback_channel`. Promoting to `stable` over MCP waits for your approval by email. A new or changed changelog on a stable build (an empty channel counts as stable) emails the owner and accepted admins. The store page shows that changelog as the patch note. A game reads the newest stable note that player has not acknowledged with `GET /api/v1/games/{game_uid}/patch/notices` and acknowledges it with `POST .../patch/notices/ack`, the same pull a fixed bug uses. Beta and identical re-uploads do not send the email. Every file records how it was uploaded (deploy key reference or website) and its scan history. Players see a short line under the scan badge, and `GET /api/v1/public/games/{game_uid}/files/{file_uid}/provenance` returns the full record. ## GitHub Actions ```yaml name: Deploy to Blazium Games on: push: tags: ["v*"] jobs: deploy: runs-on: ubuntu-latest env: BLAZIUM_ACCESS_TOKEN: ${{ secrets.BLAZIUM_ACCESS_TOKEN }} BLAZIUM_SECRET_KEY: ${{ secrets.BLAZIUM_SECRET_KEY }} steps: - uses: actions/checkout@v4 - name: Install chauffeur run: | curl -fsSL -o chauffeur.zip https://cdn.blazium.online/tools/chauffeur/linux-amd64/latest/archive/default unzip -o chauffeur.zip chauffeur && chmod +x chauffeur - name: Register build run: ./chauffeur build --asset build.yml --os linux --arch x86_64 # Export your game into ./export/linux here. - name: Upload files run: | ./chauffeur setfiles --version "${GITHUB_REF_NAME#v}" --os linux --arch x86_64 --files ./export/linux ./chauffeur addfiles --asset addfiles.yml ``` For a platform matrix, GitLab CI, and reading the `build_id` from `--json` output, see [CI](./cli/ci.md). ## What you upload is yours to answer for Only upload builds and assets you have the right to share. If someone files a paid copyright (DMCA) notice about your content, we email it to you and it appears under **Settings > Copyright notices**. Our staff review each notice, and if they decide a claim is valid, they may disable the content and suspend or ban the account. You can answer the claimant, send us evidence, or delete the build or listing yourself at any time. See [Copyright (DMCA) notices](./storefront/dmca.md#if-a-notice-names-your-content) and [section 17.1 of the Terms](https://blazium.games/terms-of-service#171-copyright-and-dmca-notices). ## Next Send the new `build_id` from your game's crash reporter. See [Crash reporting](./crash-reporting.md). # docs/developer-mode.md # Developer mode Every Blazium Games account can play, buy, review, and use the [player MCP](./mcp/player.md). Publishing needs **developer mode**, which you turn on once in your account settings by accepting the developer terms. ## Turn it on 1. Open [Settings](https://blazium.games/settings#developer) and find **Developer mode**. 2. Read the [developer terms](https://blazium.games/terms-of-service#19-developer-terms) and tick the box to accept them. 3. Click **Turn on developer mode**. The header menu then shows **Dashboard** and **Analytics**, and [New project](https://blazium.games/new) opens the project form. Without developer mode the menu shows **Publish your games** instead, which links to this setting. Accounts that already owned a project, helped run one as an admin, or held a developer MCP key on September 30, 2026 were switched on automatically. Settings asks them to accept the current terms with **Accept the new terms**, and shows **Turn off developer mode** only after that. ## What needs it | Action | Without developer mode | |---|---| | Creating a project (website, `create_game`, or `POST /api/v1/private/games`) | `4105` | | Accepting an invite to help run a project | Turns developer mode on when you accept the developer terms with the invite; `4106` without them | | Creating or rotating a project's deploy keys | `4105` | | [Importing from Steam](./steam-import.md) | `4105` | | Creating or rotating developer MCP keys, project MCP keys, and signing in to the [developer MCP server](./mcp/index.md) | `4105` | `4105` is HTTP 403 with `data.error` set to `developer_mode_required` and `data.developer_terms_version` set to the current terms version. ## Accepting an admin invite Helping run a project needs developer mode, so accepting an admin invite turns it on. If it is off, the invite on your [Dashboard](https://blazium.games/dashboard) shows an **I accept the developer terms** box that you tick before **Accept**. Through the API, send `{"accept_developer_terms": true}` with `PUT /api/v1/private/invite/{invite_uid}`; without it the answer is `4106` with `data.error` set to `developer_terms_required`. Declining never needs the terms. ## Turn it off Click **Turn off developer mode** in the same place. It is refused with `4107` while you own a project or help run one: transfer or delete your projects and leave the teams you help run first. Your earnings and past sales stay on your account. ## Terms versions The current developer terms are version `2026-09-30`. The version you accepted is stored with your account. When the terms change, Settings asks you to accept the new version with **Accept the new terms**. Turning developer mode on without accepting the current version returns `4106`. ## API `POST /api/v1/private/account/developer` with `{"enabled": true, "accept_terms": true}` turns it on, and `{"enabled": false}` turns it off. It returns `developer`, `developer_enabled_at`, `developer_terms_version` (what you accepted), and `current_developer_terms_version`. It only works with a website session; MCP tokens are refused. # docs/discovery.md # Discovery files Blazium Games is a game publishing platform, with an infrastructure focus. The files below tell crawlers, browsers, and agents where the public site, the docs, the APIs, and the MCP servers are. `llms.txt` is a curated map for agents. It is not a search-ranking file, and publishing it does not grant crawl rights. Google does not use it for ranking. Crawlers follow `robots.txt` and the sitemaps. Share titles for each public page are on [SEO and indexing](./seo-and-indexing.md). ## Crawl | URL | What it says | |---|---| | `https://blazium.games/robots.txt` | `User-agent: *` and `Allow: /`. Disallows the signed-in routes `/settings`, `/login`, `/signup`, `/setup`, `/logout`, `/password`, `/library`, `/friends`, `/redeem`, `/purchase`, `/approve`, `/dashboard`, `/edit`, and `/new`. Home, browse, the desktop app, support, the legal pages, `llms.txt`, `humans.txt`, and the sitemap stay allowed. | | `https://.blazium.games/robots.txt` | Allows the public developer site and disallows `//embed`. | | `https://blazium.games/sitemap.xml` | The platform's public pages (including `/blog` and each published post), every developer profile with an indexable listing, and every indexable store page. | | `https://blazium.games/blog` | The blog. Posts are also at `GET https://api.blazium.online/api/v1/public/articles` and `GET https://api.blazium.online/api/v1/public/articles/{slug}`, and in [the RSS file](https://cdn.blazium.online/articles/rss.xml). | | `https://.blazium.games/sitemap.xml` | That developer's profile, and their indexable store pages and press pages. | ## Trust `https://blazium.games/.well-known/security.txt` is the vulnerability contact for the publishing platform (RFC 9116): - Contact: `mailto:support@blazium.games` - Contact: [https://github.com/blazium-games/support/security/advisories/new](https://github.com/blazium-games/support/security/advisories/new) - Policy: [https://github.com/blazium-games/support/security/policy](https://github.com/blazium-games/support/security/policy) - Canonical: `https://blazium.games/.well-known/security.txt` - Preferred languages: `en` - **Expires: `2027-09-29T00:00:00.000Z`.** Renew this date before it passes. Clients are expected to ignore an expired file. The same contact is in the [security policy](https://github.com/blazium-games/support/blob/main/SECURITY.md). Developer sites do not serve this file. Also published: - [Privacy Policy](https://blazium.games/privacy-policy), [Terms of Service](https://blazium.games/terms-of-service), and [Permissions](https://blazium.games/permissions) - [GitHub](https://blazium.games/github-api-disclosure), [X](https://blazium.games/x-api-disclosure), and [Discord](https://blazium.games/discord-api-disclosure) API disclosures - [Subprocessors](https://blazium.games/subprocessors) - [Support](https://blazium.games/support) and [status.blazium.games](https://status.blazium.games/) - [humans.txt](https://blazium.games/humans.txt) ## Guidance for agents These files are maps. They do not replace `robots.txt` or the sitemaps. - `https://blazium.games/llms.txt` describes the platform, its APIs, the blog, and its MCP servers. The same connect and sign-in steps are at `https://mcp.blazium.games/llms.txt` and [https://docs.blazium.games/llms.txt](https://docs.blazium.games/llms.txt). The full guides are `https://blazium.games/llms-full.txt`, `https://mcp.blazium.games/llms-full.txt`, and [https://docs.blazium.games/llms-full.txt](https://docs.blazium.games/llms-full.txt). The blog is `https://blazium.games/blog`, the articles API is `https://api.blazium.online/api/v1/public/articles`, and the feed is `https://cdn.blazium.online/articles/rss.xml`. - `https://.blazium.games/llms.txt` lists that developer's indexable listings. - `https://.blazium.games//llms.txt` summarizes one indexable listing. - [https://docs.blazium.games/llms.txt](https://docs.blazium.games/llms.txt) is a short map of these docs, starting with the MCP steps. There is no training opt-out file. Public pages stay allowed for every user-agent. Naming training crawlers, or publishing a Content-Signal or a text-and-data-mining reservation, would be a separate decision. The public site does not serve a Markdown twin of every page. The docs map above is the Markdown entry point. ## Developer discovery `https://blazium.games/.well-known/api-catalog` is an [RFC 9727](https://www.rfc-editor.org/rfc/rfc9727) linkset (`application/linkset+json`). It links to these documents: - Docs: [https://docs.blazium.games/](https://docs.blazium.games/) - Status: [https://status.blazium.games/](https://status.blazium.games/) - [https://blazium.games/llms.txt](https://blazium.games/llms.txt) - Developer server card: [https://mcp.blazium.games/.well-known/mcp/server-card.json](https://mcp.blazium.games/.well-known/mcp/server-card.json) - Player server card: [https://mcp.blazium.games/.well-known/mcp/player-server-card.json](https://mcp.blazium.games/.well-known/mcp/player-server-card.json) - OAuth protected-resource metadata (RFC 9728) for [the developer server](https://mcp.blazium.games/.well-known/oauth-protected-resource/mcp) and [the player server](https://mcp.blazium.games/.well-known/oauth-protected-resource/player) - The public API's OpenAPI 3.1 description, as the `service-desc` of `https://api.blazium.online/api/v1/public/`: [JSON](https://api.blazium.online/api/v1/public/openapi.json) and [YAML](https://api.blazium.online/api/v1/public/openapi.yaml). Its `service-doc` is the [public API reference](./api-reference.md). - The [editor asset library](./editor-asset-library.md) repository URL: `https://api.blazium.online/api/v1/public/asset-library` - Public JSON: [search](https://api.blazium.online/api/v1/public/search), [articles](https://api.blazium.online/api/v1/public/articles), and [sitemap](https://api.blazium.online/api/v1/public/sitemap) - Blog RSS: [https://cdn.blazium.online/articles/rss.xml](https://cdn.blazium.online/articles/rss.xml) Indexable store pages publish `VideoGame` or `SoftwareApplication` JSON-LD. Profiles publish `ProfilePage` and `Person`. ## Files this site does not publish - **AsyncAPI.** The website's live updates are not a public interface. The public HTTP API has an [OpenAPI description](./api-reference.md). Signed-in account routes are left out of it; agents use the MCP servers, which publish server cards. - **ads.txt.** Blazium Games does not sell ad inventory. - **Apple or Android association files.** The desktop program people can download today is BlaziumLauncher for Windows, installed under the shared Blazium folder, not a mobile app. - **ai.txt, identity.json, an A2A agent card, or an empty agent card.** Agents call the MCP servers, and those servers already publish server cards. An empty card would claim a protocol this site does not serve. - **A training opt-out file.** See the guidance section above. # docs/download-analytics.md # Download analytics Blazium Games is a game publishing platform, with an infrastructure focus. Every download of one of your build files is recorded, whether it came from the website, the editor asset library, the API, or an agent. Attempts that were refused are recorded too. You see downloads on your project's **Analytics** page, on the account-wide [Analytics](https://blazium.games/analytics) page, and through the MCP tool `get_game_analytics`. Each covers the last 30 days. ## The downloads block Game and account analytics include a `downloads` object: | Field | Meaning | |---|---| | `total` | Downloads that went through. | | `unique_users` | Distinct signed-in accounts among them. | | `anonymous` | Downloads with no account (see [anonymous downloads](./anonymous-downloads.md)). | | `licenses_granted` | Downloads that added a free project to someone's library for the first time. | | `by_source` | `[{ "source", "count" }]`: where the download came from. | | `by_access` | `[{ "access", "count" }]`: how the downloader had access. | | `by_client` | `[{ "client", "count" }]`: the program that downloaded. | | `by_outcome` | `[{ "outcome", "count" }]`: every attempt, including refusals. | | `by_country` | `[{ "country", "count" }]`: two-letter country codes, where known. | | `daily` | `[{ "day", "count" }]`: downloads that went through, per UTC day. | Each entry in `per_game` on the account page also has `downloads`, the 30-day total for that project. Totals count only downloads that went through (`outcome` `ok`). Refusals appear only under `by_outcome`. ## Sources | `source` | Meaning | |---|---| | `website` | The store page: a signed-in download through the site, or a signed-out link when anonymous downloads are on. | | `asset_library` | The Godot or Blazium [editor asset library](./editor-asset-library.md). | | `api` | Any other direct call to the download API, for example a script or launcher. | | `mcp_player` | An agent using the player MCP server. | | `mcp_dev` | An agent using the developer MCP server. | A signed-out download counts as `website` only when the link carries `source=website` and the browser came from a blazium.games page. Otherwise it counts as `api`. Sources are for your reports only. They don't grant or refuse anything, and a determined caller can imitate one. ## Access | `access` | Meaning | |---|---| | `anonymous` | No account; anonymous downloads were on. | | `owner` | You or an admin of the project. | | `free` | A signed-in player downloading a free project. | | `purchase` | A player who bought it. | | `grant` | A player you gave it to. | | `key` | A player who redeemed a key or gift link. | | `bundle` | A player who got it in a bundle. | ## Clients | `client` | How it is recognized | |---|---| | `godot_editor` | User-Agent `GodotEngine/`. The version, such as `4.5.1`, is kept. | | `blazium_editor` | User-Agent `BlaziumEngine/`. | | `browser` | A browser User-Agent. | | `agent` | Agents and scripts that identify themselves, such as the Blazium MCP servers. | | `other` | Anything else, or no User-Agent. | ## Outcomes | `outcome` | Meaning | |---|---| | `ok` | The file link was handed out. | | `sign_in_required` | Signed out, and anonymous downloads were off or the project is paid. | | `payment_required` | Signed in, but they don't own the paid project. | | `scanning` | The file was still being virus-scanned. | | `unavailable` | The file link couldn't be created. | Unknown files aren't recorded. Neither are files the caller can't see, such as a private or adult listing or a channel they aren't in. ## What is recorded Each attempt stores the file, the build and channel, the account (or none), the source, client, access, and outcome, whether a license was granted, the country, and the host of the referring page (such as `godotengine.org`, never the full address). **The IP address is never stored.** The country is looked up from it when the request arrives, and only the country is kept. ### Country gaps A signed-in download on the website is requested by the site's own server for the visitor, so the address belongs to the server. Those downloads have no country. Downloads from the editor, the API, agents, and signed-out website links come straight from the downloader and do have a country. ## Through MCP `get_game_analytics` and the `blazium-games://games/{uid}/analytics` resource return the same payload as the project's analytics page, including `downloads` and `plays`. A token needs `mcp:read` or `mcp:analytics.read`. See the [MCP reference](./mcp/reference.md). ## Plays Browser plays are beside downloads. They are not added to download totals and they are not library play time. `plays` covers the last 30 days: total, unique players, anonymous plays, seconds the tab was visible, median session, and full versus demo. See [Browser player](./web-player.md). # docs/editor-asset-library.md # Editor asset library Blazium Games is a game publishing platform, with an infrastructure focus. Godot and Blazium already include an AssetLib tab. Point that tab at Blazium Games and it lists and installs packages with no extra plugin. In the editor, open **Editor Settings**, then **Asset Library**, and add this repository under `asset_library/available_urls`: `https://api.blazium.online/api/v1/public/asset-library` Give it a name such as **Blazium Games**. The editor requests `configure`, `asset`, and `asset/{id}` under that URL, then downloads the file when you choose **Download**. Blazium Hub and other tools can call the same routes. The old URL, `https://api.blazium.online/asset-library/api`, no longer answers. Replace it with the one above. The routes are also in the [OpenAPI description](./api-reference.md). ## What shows up The AssetLib tab lists addons. The project manager lists templates (`type=project`). | Category id | Category | Listings | |---|---|---| | `1` | Plugins | `plugin` | | `2` | Editor assets | `dev_asset` | | `3` | Tools | `tool` | | `4` | Templates | a plugin, editor asset, tool, or game asset whose zip contains `project.godot` | A package is listed when all of these are true: - it is public and not adult; - the owner has verified their email; - the stable channel has a zip that passed the virus scan; - it declares Godot or Blazium compatibility, or the build has an engine version, so the editor's version filter can include it. The editor sends its major.minor version and ignores the patch number. Paid packages are listed too. You buy them on the website, then download them in the editor while signed in. Games, applications, and mods stay on the store page. Publishing stays on the website and the upload tools. ## Browsing and downloading Browsing needs no account. Every row says what this caller needs before downloading: | Field | Meaning | |---|---| | `anonymous_download` | `true` when anyone can download the package without signing in. The developer turned on [anonymous downloads](./anonymous-downloads.md). | | `download_requires` | `none`, `sign_in`, or `purchase`, for this caller. | | `price_cents`, `currency` | The price. `0` is free. | Who can download what: | Caller | Free, anonymous downloads on | Free, anonymous downloads off | Paid | |---|---|---|---| | No token | Yes, with no license | `401`, code `4001` | `401`, code `4001` | | Signed in | Yes, and a free license the first time | Yes, and a free license the first time | Only if you own it; otherwise `402`, code `4023` | | Owner or admin | Yes | Yes | Yes | When a caller can't download yet, the package description starts with a note and a link to the store page. A `401` or `402` body also has `data.browse_url`. A paid package's error adds `game_uid`, `price_cents`, and `currency`. A signed-in caller also sees their own listings, including private ones, and adult listings if their account confirmed they are 18 or older and opted in. ## Signing in Send a player credential in the `Authorization` header: ```http Authorization: Bearer bgames_play_... ``` Either credential works: - **A player key** (starts with `bgames_play_`), created at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). - **A player OAuth access token** from `https://mcp.blazium.games/.well-known/oauth-authorization-server/player`, for the resource `https://mcp.blazium.games/player`. The credential needs the `player:read` scope. A token without it gets `403`, code `4031`. An invalid or expired token gets `401`. It is not treated as anonymous. The `BLAZIUM_GAMES` header is accepted as well. `configure` returns these details so a client can set up sign-in: ```json { "categories": [{ "id": "1", "name": "Plugins", "type": "0" }], "login_url": "https://blazium.games/login", "auth": { "type": "bearer", "header": "Authorization", "scope": "player:read", "keys_url": "https://blazium.games/settings/mcp", "authorization_server": "https://mcp.blazium.games/.well-known/oauth-authorization-server/player", "resource": "https://mcp.blazium.games/player", "signed_in": false } } ``` With a valid token, `signed_in` is `true` and `username` is set. The stock Godot editor does not send a token yet, so in the editor you see every package and can download those with `anonymous_download: true`. Buy or sign in on the website for the others. ## Routes Each route is a GET. A successful answer is the raw object the editor parses, with HTTP 200 and no envelope. Errors use the Blazium envelope: `{"success": false, "error": {"code": 4040, "message": "..."}}`. The editor shows any non-200 answer as a failed request. | Route | What it returns | |---|---| | `/api/v1/public/asset-library/configure` | Categories and the `auth` block above. `type=project` returns Templates. Anything else returns Plugins, Editor assets, and Tools. | | `/api/v1/public/asset-library/asset` | `{ "result", "page", "pages", "page_length", "total", "total_items" }`. `page` is 0-based. `total` and `total_items` are the same count. | | `/api/v1/public/asset-library/asset/{asset_id}` | One package. An unknown or hidden id returns `404`, code `4040`. | | `/api/v1/public/asset-library/asset/{asset_id}/download` | Redirects (`302`) to a file link that is valid for five minutes. The editor follows the redirect. | `asset_id` is numeric. In the JSON, `asset_id`, `author_id`, `category_id`, and `version` are decimal strings. A package has these fields: - `cost` is the license name, such as `MIT`, `CC0`, `CC-BY`, `CC-BY-SA`, `Source Available`, `Proprietary`, or `Unknown`. - `description` is the listing text with BBCode escaped (`[` is sent as `[lb]`), so listing text can't add links or formatting in the editor. - `download_url` is the download route. - `download_hash` is the zip's SHA-256 hex, or an empty string when the file has no sha256 checksum. - `browse_url` is the store page. The download's other answers are: - `401` or `402`, as described above; - `409`, code `4099`, while the build is still being scanned; - `503`, code `5030`, when the file link can't be signed. ### Search parameters The list accepts the editor's query: - `type`, `category`, `support`, `filter`, `user`, `cost`, `godot_version`; - `max_results`, from 1 to 500 (default 10); - `page` or `offset`; - `sort` (`updated`, `name`, `cost`, `rating`) and `reverse`. Blazium adds `price` (`free` or `paid`). Godot never sends it. Support values are `official`, `community`, and `testing`, joined with `+`. Packages are community listings. The editor checks Featured and Community by default (`support=official+community`), so they show. An unknown sort, support, category, or other filter value returns an empty `result` with HTTP 200, because the editor treats any other status as a failure. `filter` is up to 100 characters. ## Caching, limits, and CORS - **Cache:** answers without a token are `Cache-Control: private, max-age=60`, so a client may reuse them for a minute but shared caches don't keep them. The anonymous catalog refreshes at most once a minute, so a new or changed package can take a minute to appear. Answers with a token are `private, no-store`. Responses vary on `Authorization` and `BLAZIUM_GAMES`. - **Rate limits:** browsing allows 300 requests a minute per IP address. Downloads allow 60 a minute per IP address. Past either limit the answer is `429`. - **CORS:** any origin may call these routes (`Access-Control-Allow-Origin: *`). Credentials are never allowed. Sign-in is the header, never a cookie. ## Analytics Every download attempt is counted in the developer's [download analytics](./download-analytics.md) with the source `asset_library`. The client is read from the User-Agent: `GodotEngine/4.5.1` counts as the Godot editor 4.5.1, and `BlaziumEngine/...` as the Blazium editor. # docs/engines.md # Engines A Blazium game uses the engine module. A game on Godot, Unity, or Unreal uses the binding for that engine. All three are MIT licensed. macOS has no player build of the native library. An `sdk-*` tag publishes the full SDK drop and two player-library zips on that same tag. A `templates-*` tag publishes the engine host, not the player library. | Zip | Contents | | --- | --- | | `redistributable-win64.zip` | `blazium_api64.dll` and `blazium_api64.lib` | | `redistributable-linux64.zip` | `libblazium_api.so` | Unity and Unreal copy the library out of those zips. The Godot addon does not load it. ## Godot The addon is [blazium-games/games_plugin](https://github.com/blazium-games/games_plugin). Download `blazium_games-.zip` from a release, or copy `addons/blazium_games` from the repository. Enable the plugin and set the project setting `blazium/game/game_uid` to the project id. The addon signs in on the login websocket, then uses that session for the lobby and for peer connections. Sign-in and lobbies are described in [Multiplayer](./multiplayer.md). It talks to Blazium over HTTP. It does not ship the native library. `server_progress` is the only call that uses `await`. Every other call returns through a signal. `record_standard_events` posts `session_start`, `session_end`, `boot_ok`, `first_input`, `quit`, and `crash` in one request with zero times. It is not a hook for each of those moments. `transfer_item` is the player call. `socket_item`, `unsocket_item`, `set_item_stats`, and `use_item` fail on a player session. Those need the owner, an accepted admin, or a mint key. Unity and Unreal forward those four to the library, and the server still rejects a player session. Inside a Discord activity, the addon proxies login, lobby, and API. ## Unity The package is [blazium-games/games_unity](https://github.com/blazium-games/games_unity). The package name is `com.blazium.games`. Download `com.blazium.games-.tgz` and install it with Package Manager (**Add package from tarball**), or copy the package into the project as `Packages/com.blazium.games`. Package Manager can import the Client and Dedicated server samples. Put `blazium_api64.dll` or `libblazium_api.so` from the redistributable zip in `Assets/Plugins/x86_64`. Put `game.blaze` beside the built player. Add a `BlaziumTick` component to one object. It calls `RunCallbacks` from `Update`. Do not also call `RunCallbacks` every frame. Do not call `BlaziumApi.Init` and `BlaziumGameServer.Init` in the same process. The public `ReportBug` method always sends the in-game report. An empty build id and an empty screenshot path omit those parts. The screenshot path check lives in the engine host, not in the C# wrapper. This package does not proxy a Discord activity. ## Unreal The plugin is [blazium-games/games_unreal](https://github.com/blazium-games/games_unreal). Copy the `BlaziumGames` folder from `BlaziumGames-.zip` to `Plugins/BlaziumGames` and enable Blazium Games. Windows (`Win64`) and Linux are the supported targets. Put `blazium_api64.dll` or `libblazium_api.so` from the redistributable zip, and `game.blaze`, beside the game executable. `UBlaziumSubsystem` calls `RunCallbacks` while a session is open. Do not also call it every frame. Blueprint nodes are in the Blazium category. Do not call client init and dedicated-server init in the same process. `ReportBug` always sends the in-game report. An empty build id and an empty screenshot path omit those parts. The screenshot path check lives in the engine host, not in the plugin. This plugin does not proxy a Discord activity. ## game.blaze UTF-8 JSON beside the player executable. Unity and Unreal do not write this file. The Godot addon uses the project setting instead. ```json { "game_uid": "550e8400-e29b-41d4-a716-446655440000" } ``` `game_uid` is the project id on blazium.games. No other keys are allowed. The native library talks to the Blazium launcher on the player's machine. The Unity package and the Unreal plugin do not call `api.blazium.online`. Lobby, ICE, Steam ticket, and bug report calls return JSON. ## Bug reports The short call is `report_bug`. It sends the message, version, OS, architecture, and an optional log. The in-game call is `report_ingame_bug` on the engine and `ReportInGameBug` on the native library. Godot, Unity, and Unreal expose that in-game call as `report_bug` or `ReportBug` when a build id or screenshot path is set. That call sends `X-Build-Id`, the log, and the screenshot. The short call does not. A screenshot path has to stay under the game user directory (`user://` on Godot) and stops at 32 MiB. The service redacts the log before storage. See [Bug reporter](./bug-reporter.md). ## Shared calls Godot, Unity, and Unreal share ownership, achievement unlocks, stat writes, funnel events, a progress read of unlocks and stat values, `SetPresence` when the client may write presence, and the patch-note pull described in [Deploy builds](./deploy.md). The Godot addon also transfers an item. Unity and Unreal export the item calls and the server progress read. `record_standard_events` on all three is one batch with zero times, the same kind of call the native library makes. Inside a Discord activity, only the Blazium module and the Godot addon open the proxied login, lobby, and API addresses. Unity and Unreal do not. A Telegram Mini App uses the public hosts instead. See [Multiplayer](./multiplayer.md). ## Browser exports The player catalog accepts Godot and Blazium HTML5, Unreal 4.23, Unreal 5.8 and 5.9 WebGPU, Unity WebGL, and the named browser frameworks. Unreal 5.8 is the community WebGPU pack. Unreal 5.9 WebGPU is experimental and needs cross-origin isolation. Godot 4.6.1, 4.6.3, and 4.7.2 mini-game exports, plus Unity, Cocos, and Laya mini-game packs, are stored for TikTok, Douyin, or WeChat. They are not booted in the browser. See [Browser player](./web-player.md). # docs/faq.md # FAQ ## How do I find a game? Open [Browse](https://blazium.games/browse) and search, or start from the shelves on the home page. The [find a game](./storefront/find-a-game.md) guide covers filters and shelves. ## Where are the games I own? They are in your [library](https://blazium.games/library). See [Your library](./storefront/library.md). ## I paid and the game is not in my library Sign in with the same account you paid with. A card purchase can take a moment to show up. If it is still missing, use the [support page](https://blazium.games/support) and include the email on the account. Buying itself is described in [How buying works](./payments/buying.md). ## How do I report a page? Use the report link on the page, or the [report guide](./storefront/report.md). Copyright claims use the [DMCA](./storefront/dmca.md) form, which has its own fee. ## How do I delete my account? Account deletion is in [Settings](https://blazium.games/settings). What is kept and for how long is in the [privacy policy](https://blazium.games/privacy-policy). # docs/graphical_assets_guidelines.md # Graphical Assets Guidelines When listing your product on blazium.games, you provide a thumbnail, a cover and gallery screenshots. These are displayed in different places on blazium.games. :::info[Image rules] PNG, JPEG, GIF or WebP. The format is read from the file itself, not its name. Each slot has its own size. 16:9 means the width divided by the height is between 1.70 and 1.85. Square means that ratio is between 0.95 and 1.05. | Slot | Minimum | Maximum | Shape | File size | |------|---------|---------|-------|-----------| | Thumbnail | 960x540 | 1920x1080 | 16:9 | 5 MB | | Cover | 1024x576 | 2048x1152 | 16:9 | 8 MB | | Screenshot | 1280x720 | 2048x1152 | 16:9 | 10 MB | | Avatar | 256x256 | 512x512 | Square | 2 MB | A gallery holds 4 to 20 screenshots. chauffeur adds at most 10 at a time, and a game can change images 60 times an hour. Upload a thumbnail, cover and screenshots on the game's edit page, or with [`chauffeur media`](./cli/media.md) and the game's deploy key. The avatar is on the account settings page. ::: ## Thumbnail Image - **Size:** 1280x720 recommended, inside 960x540 to 1920x1080, 16:9, up to 5 MB. - **Usage:** Home page, browse page, profile cards and similar games. Every one of those frames is 16:9. - **Design:** For best results use the product's key art and logo. ![Example thumbnail: key art with the game logo](/img/graphical_assets_examples/thumbnail.png) ## Cover Image - **Size:** 1024x576 recommended, inside 1024x576 to 2048x1152, 16:9, up to 8 MB. - **Usage:** The store page sidebar, up to 400 px wide, and the press page at the content width. - **Design:** The product's logo should be easily legible **even at smaller sizes**. ![Example cover: the game logo on a dark background](/img/graphical_assets_examples/cover.png) ## Screenshots Images - **Size:** 1920x1080 recommended, inside 1280x720 to 2048x1152, 16:9, up to 10 MB. Scale 4K captures down to fit. - **Usage:** The store page viewer, up to 900 px wide, and the press gallery. A public listing needs at least 4. - **Design:** Screenshots should exclusively show the usage of the product (gameplay, tool or asset being used). ![Example screenshot: gameplay](/img/graphical_assets_examples/screenshot.png) ## Avatar - **Size:** 512x512 recommended, inside 256x256 to 512x512, square, up to 2 MB. - **Usage:** The account menu, the settings page (96 px) and the profile page (128 px). Shown cropped to a square. - **Design:** A face or a mark that stays recognizable at a small size. # docs/intro.md # Introduction This is the documentation for [Blazium Games](https://blazium.games). Blazium Games is a game publishing platform, with an infrastructure focus. ## The platform Players browse the catalog, keep a library, and use [BlaziumLauncher](./storefront/desktop-app.md) on Windows or Linux. Friend messages and each game's chat are IRC on `irc.blazium.online`; see [Chat](./chat/index.md). Publishers host a profile and a page for each project, with a press kit and lists of mods and tools. Upload builds with `npm install -g @blazium-games/cli` (`chauffeur`). The files crawlers and agents read — robots.txt, sitemaps, security.txt, the API catalog, and llms.txt — are listed in [Discovery files](./discovery.md). ## Start here - **[MCP](./mcp/index.md)**: connect Cursor, VS Code, Claude Code, or any MCP client so an AI agent can manage your store pages, builds, channels, analytics, crash reports, bug tickets, reviews, and game keys. - **[Player MCP](./mcp/player.md)**: let an agent act for you as a player: recommendations, catalog search, reviews, bug reports, friends, and purchases within your spending limits. - **[Cursor plugin](./cursor-plugin.md)**: the official plugin bundles the MCP server with skills for common workflows. - **[Deploy builds](./deploy.md)**: upload builds, symbols, and store images with the [chauffeur CLI](./cli/index.md), the API, or GitHub Actions. - **[Crash reporting](./crash-reporting.md)**: send crashes and events from your game. - **[In-game bug reporter](./bug-reporter.md)**: let players file a bug from the game, with a screenshot and a webhook. - **[Payments](./payments/index.md)**: sell games or take donations, buy games, top up your balance, cash out, refunds, and agent purchases. - **[Linked accounts and sign-in](./linked-accounts.md)**: link GitHub, X, or Discord, log in with them, and unlink them. - **[Multiplayer](./multiplayer.md)**: sign-in, lobbies, and peer connections for a game, and how to publish a scripted lobby. - **[Engines](./engines.md)**: Godot, Unity, and Unreal bindings for a game. - **[Progress](./progress.md)**: achievements, stats, funnel events, and rich presence, and which of the client, game server, private server, or scripted lobby may write them. - **[Anticheat](./anticheat.md)**: ask for anticheat on a game, what stays closed until an NDA and a contract are signed, and how a server and a client report. - **[Graphical assets guidelines](./graphical_assets_guidelines.md)**: image sizes for your store page. - **[Editor asset library](./editor-asset-library.md)**: paste one repository URL into Godot or Blazium so the AssetLib can list and install packages from Blazium Games. - **[Anonymous downloads](./anonymous-downloads.md)**: let anyone download a free project without an account, and what that gives up. - **[Download analytics](./download-analytics.md)**: where downloads come from, how players had access, and refused attempts. - **[Public API reference](./api-reference.md)**: the OpenAPI description, authentication, error codes, and rate limits of the public API. ## Help - Support: [blazium.games/support](https://blazium.games/support) or [support@blazium.games](mailto:support@blazium.games) - Bug reports: [blazium-games/support](https://github.com/blazium-games/support/issues) - Service status: [status.blazium.games](https://status.blazium.games) - Privacy: [privacy@blazium.games](mailto:privacy@blazium.games) - Community: [Discord](https://blazium.app/chat) - Docs and the Cursor plugin: [blazium-games/games_docs](https://github.com/blazium-games/games_docs) - Skills: [blazium-games/games_skill](https://github.com/blazium-games/games_skill) (`npm install @blazium-games/skills`) - Launcher: [blazium-games/games_launcher](https://github.com/blazium-games/games_launcher) - CLI: [blazium-games/games_cli](https://github.com/blazium-games/games_cli) (`npm install -g @blazium-games/cli`) - Support tracker: [blazium-games/support](https://github.com/blazium-games/support) # docs/inventory.md # Item inventory Each copy of an item is its own row with a stable id. A stack is only how plain copies of a stackable item are grouped. A unique item can be minted once, cannot be stackable, and stays unique after it is sold, transferred, or used. Platform types are melee, ranged, armor, jewelry, shield, consumable, material, blueprint, food, and drink. Steam's item, bundle, generator, and playtimegenerator types stay separate. ## Switches On the game's Steam tab, after Steam auth is on: - **Inventory** starts off. Turning it on cannot be undone. Existing items stay. - **Transfers** stays off until inventory is on. Turning it on cannot be undone. The website cannot move items. The game calls TransferItem. The API and the developer MCP refuse a later off. ## Editing The editor Items tab lists the name, icon, total minted, and total still in the wild. Definitions, icons, sets, schema, and mint keys are changed with chauffeur or the developer MCP. ```text chauffeur items create --itemdef 10 --name Relic --platform-type material --unique chauffeur items icon --itemdef 10 --file icon.png chauffeur items schema --mode sync chauffeur items give --itemdef 10 --quantity 1 --request give-1 --to player chauffeur mint-key create --name live ``` `schema --mode sync` pulls Steam definitions, lets Steam win on a shared itemdef id, then pushes. `overwrite` pushes and replaces the Steam set. `addon` pushes only definitions that are not on Steam yet. A failed call is stored and does not mark the definition synced. None of these modes move player items. Give takes one item and one quantity, for one handle or email or a list. An unknown recipient fails only that row. The same request id does not give twice. Give does not call Steam. ## Mint keys A mint key is 128 characters, named, and shown once. The stored value is a hash. It can mint, set instance stats, socket, unsocket, and use items for players of that game. It cannot edit definitions, sync or transfer to Steam, list, or sell, and it is not a progress key. A player session cannot do those things. The game owner or an accepted admin can, on routes that name the player. ## Market The Items section on a game page lists other players' listings, one page at a time. The lowest price is $0.03 and the highest is $100,000. At $0.03 the split is one cent for Blazium, one cent for the game, and one cent for the seller. Above that, Blazium keeps 5% and the game keeps 10%, and each of those two shares is at least one cent. A $10 sale pays Blazium $0.50, the game $1.00, and the seller $8.50. Games cannot change that. The buyer pays from their balance. There is no card charge from the Items section. Seller and game earnings settle from pending to available, then both cash out through the existing payout balance. A seller can cancel a listing that is still pending. Your Inventory page, next to Library, shows items from games you own and items you bought from games you do not own. Each game name links to that game. Grants on a game you do not own stay off that page until you buy one. Socketed items show their attachments and the added stats. Players cannot use, socket, or unsocket items from the website. ## Game calls The C SDK and the Godot plugin expose TransferItem. SocketItem, UnsocketItem, SetItemStats, and UseItem return an error and do not call the API. A player can move an item to Steam only: the game has inventory and transfers on, the player holds a license, they have logged in to that game at least once with the linked Steam account, and the definition is already on Steam. `to_platform` is refused. The same request id does not move twice. A failure leaves the item on Blazium Games. An attached item has to be unsocketed by the owner, an accepted admin, or a mint key before it can move or be listed. List commands take `--cursor` and print `next`. # docs/legal/chat-rules.md :::note Canonical version: https://blazium.games/chat-rules ::: # Chat Rules **Effective Date: October 9, 2026** These rules cover Blazium Games chat: the IRC network at `irc.blazium.online`, the chat on the website, and chat inside games and the Blazium Games app. They are part of the [Terms of Service](https://blazium.games/terms-of-service). If something isn't covered here, the Terms apply. ## 1. The short version - **Anything legal is allowed.** Talk about what you want, how you want. A game's developers can set stricter rules for their own game's channel. - **Nothing illegal is allowed.** No illegal content, links, trades, threats, or plans. - **Never children.** Grooming, sexual content involving minors, and any predatory contact with a child are never allowed. - **Chat is not logged.** We don't keep transcripts of what you say. Section 5 explains the few things we do keep. ## 2. What is not allowed - **Anything illegal** under United States law, including fraud, selling stolen accounts or payment details, distributing malware, and threats of violence. - **Harm to children.** Grooming, sexual content involving minors, asking a minor for images, personal details, or to move to another app, and any other predatory contact with a child. Child sexual abuse material is removed and reported as United States law requires. - **Doxxing.** Posting someone's private information, such as a home address, phone number, or real name they haven't shared, without their consent. - **Sharing access.** Posting or trading someone else's chat token, password, or account. - **Disrupting the network.** Flooding, running bots the channel didn't approve, evading a ban, or attacking other users or the servers. Each IP address can have up to 3 connections. - **Impersonating** our staff or another person. ## 3. What happens if you break these rules - A game's developers can ban you from their game's channel, or mute you for a while. - We can lock your account out of all chat, for a set time or indefinitely, or suspend the account. - Serious violations, and anything involving harm to a child, can lead to harsher action, up to closing your account and reporting to the authorities where the law requires it. Moderation decisions are ours, as described in section 17 of the [Terms of Service](https://blazium.games/terms-of-service#17-moderation-is-our-decision). ## 4. Your chat token - To use your own IRC client, create a chat token in [Settings > Chat](https://blazium.games/settings/chat) and use it as your password with SASL PLAIN. Your username is your Blazium Games username. - The token is secret. It is shown once, when you create it, and can't be shown again. We keep only a hash of it. - To get a new one, regenerate it. The old token stops working, and any client signed in with it is disconnected right away. Revoking the token does the same. - Don't share your token. Anyone who has it can chat as you. ## 5. What we keep Messages are not logged, and we don't keep chat transcripts. We do keep: - **Recent channel history in memory.** Each channel keeps its last 50 lines for up to one day in the chat servers' memory, so people who join can catch up. It is never written to disk and is gone when a server restarts. - **Blocked spam.** If spam filtering blocks a message, the server's log can record the blocked text and who sent it. - **Connection records.** The chat servers keep a size-capped operational log of connections (account name, IP address, and time). It contains no messages and is overwritten as it fills. - **Moderation records.** Channel bans, mutes, and chat locks, with who set them, the reason, and when they end. - **Your token.** A hash of your chat token, when you created it, and when it was last used. See the [Privacy Policy](https://blazium.games/privacy-policy) for how long account data is kept. ## 6. Reporting Use the report buttons on the Service, or email [support@blazium.games](mailto:support@blazium.games) with the channel, the usernames involved, and the time. Because chat isn't logged, a screenshot helps. If a child is in danger, contact your local authorities first. ## 7. Changes We may update these rules. The effective date at the top shows the current version. # docs/legal/discord-api-disclosure.md :::note Canonical version: https://blazium.games/discord-api-disclosure ::: # Discord API Disclosure **Effective Date: September 30, 2026** Blazium Games uses the Discord API only to link Discord to your account and let you log in with it. This page explains what we access and the commitments we make about it. ## What we access We request the `identify` and `email` scopes. With them we make one request, to `GET /users/@me`, and read: - your Discord user ID and username. Discord also returns your email address, display name, and avatar with your profile. We do not store the email, and we do not copy the display name or avatar. If Discord marks the email verified, we compare it during sign-in. An unverified or missing email is ignored. We do not request the `guilds`, `bot`, or messaging scopes. ## How we use it - **Account linking:** when you are signed in and link Discord at [Linked accounts](https://blazium.games/settings/connections), we attach your Discord user ID to your account. - **Sign-in:** we look for the account your Discord user ID is linked to. If it is linked, you confirm your password and then an authenticator code or an emailed code. If it is not linked and the verified email matches an account, that account's password links Discord. Otherwise you finish a new account and confirm the emailed code before Discord is linked. - **No pre-filling:** a verified email can be shown on the create form. We do not copy your Discord name or avatar, and we do not save the Discord email until you confirm the address you submit. That is the only use. We make one Discord API request per link or sign-in and none after that. ## Our commitments - We never store your Discord access token. It is used during sign-in or linking and then discarded. - We never join servers for you, add a bot, or read your servers or messages. - We never send messages on Discord for you. - We never store your Discord email address. A verified address is compared during sign-in and is not saved on its own. - We never use Discord data for advertising. - We never use Discord data to train AI or machine-learning models. - We never sell Discord data or share it with third parties, except the [subprocessors](./subprocessors.md) that host our service. - We only keep your Discord user ID and username, so the linked account can log in and the settings page can show which one is linked. - We will not ask for more scopes without updating this page first. We also use Discord for internal team communication; this never involves your Discord account. ## Revoking access and deleting data - Unlink Discord at [Linked accounts](https://blazium.games/settings/connections). After that, Discord can no longer be used to log in to your account. - Revoke Blazium Games at any time in Discord under **User Settings > Authorized Apps**. This does not unlink Discord here, so unlink it as well if you want to stop Discord sign-in. - To delete your account and the Discord link, email [privacy@blazium.games](mailto:privacy@blazium.games). We process deletion requests within 30 days. See the [Privacy Policy](https://blazium.games/privacy-policy#6-deleting-your-account) for what deletion covers. See also the [GitHub API disclosure](./github-api-disclosure.md), the [X API disclosure](./x-api-disclosure.md), [Permissions & Scopes](./permissions.md), and the [Linked accounts and sign-in](../linked-accounts.md) guide. ## Contact Questions about this disclosure: [privacy@blazium.games](mailto:privacy@blazium.games). # docs/legal/github-api-disclosure.md :::note Canonical version: https://blazium.games/github-api-disclosure ::: # GitHub API Disclosure **Effective Date: September 30, 2026** Blazium Games uses the GitHub API only to link GitHub to your account and let you log in with it. This page explains what we access and the commitments we make about it. ## What we access We request the `read:user` and `user:email` scopes. With them we read: - your GitHub user ID and login; - your primary email address. A verified address is compared with existing accounts during sign-in and can be shown on the create form. We do not store it on its own. If GitHub does not report a verified email, you type an email instead. GitHub also returns your name and avatar with your profile. We ignore them. ## How we use it - **Account linking:** when you are signed in and link GitHub at [Linked accounts](https://blazium.games/settings/connections), we attach your GitHub user ID to your account. - **Sign-in:** we look for the account your GitHub user ID is linked to. If it is linked, you confirm your password and then an authenticator code or an emailed code. If it is not linked and the verified email matches an account, that account's password links GitHub. Otherwise you finish a new account, confirm the emailed code, and then set up an authenticator app or confirm another emailed code. The new account is created only after that inbox code matches. - **No pre-filling:** a verified email can be shown on the create form. We do not copy your GitHub name or avatar, and we do not save the GitHub email until you confirm the address you submit. That is the only use. We do not call the GitHub API again after sign-in or linking. ## Our commitments - We never store your GitHub access token. It is used during sign-in and then discarded. - We never write to your repositories or act on GitHub for you. - We never use GitHub data for advertising. - We never use GitHub data to train AI or machine-learning models. - We never sell GitHub data or share it with third parties, except the [subprocessors](./subprocessors.md) that host our service. - We only keep your GitHub user ID and login, so the linked account can log in and the settings page can show which one is linked. ## Revoking access and deleting data - Unlink GitHub at [Linked accounts](https://blazium.games/settings/connections). After that, GitHub can no longer be used to log in to your account. - Revoke Blazium Games at any time under [GitHub > Settings > Applications > Authorized OAuth Apps](https://github.com/settings/applications). This does not unlink GitHub here, so unlink it as well if you want to stop GitHub sign-in. - To delete your account and the GitHub link, email [privacy@blazium.games](mailto:privacy@blazium.games). We process deletion requests within 30 days. See the [Privacy Policy](https://blazium.games/privacy-policy#6-deleting-your-account) for what deletion covers. See also the [X API disclosure](./x-api-disclosure.md), the [Discord API disclosure](./discord-api-disclosure.md), [Permissions & Scopes](./permissions.md), and the [Linked accounts and sign-in](../linked-accounts.md) guide. ## Contact Questions about this disclosure: [privacy@blazium.games](mailto:privacy@blazium.games). # docs/legal/index.md # Legal and privacy Blazium Games is operated by Divine Games, Inc. The canonical versions of these pages live on blazium.games. The copies here are for reference while you work with the docs, the MCP server, or the Cursor plugin. | Page | What it covers | | --- | --- | | [Privacy Policy](https://blazium.games/privacy-policy) | What is collected (including payment data and what chat keeps), the 1-year analytics retention, cookies, and account deletion. | | [Terms of Service](./terms-of-service.md) | The terms for using Blazium Games, including payments, fees, taxes, the account balance, cash-outs and payout timing, refunds (donations are not refundable), agent purchases and payouts, and copyright (DMCA) notices, which are filed only through a paid form, forwarded to the uploader, and reviewed by our staff. The designated DMCA agent is registered with the United States Copyright Office as DMCA-1085117. | | [Permissions & Scopes](./permissions.md) | GitHub, X and Discord sign-in and linking scopes, Steam linking, MCP scopes, agent spending limits, agent payouts, keys (including Steam auth keys and Steamworks Web API keys), and cookies, plus how scopes behave for developers. | | [GitHub API disclosure](./github-api-disclosure.md) | What is read from GitHub and the commitments made about it. | | [X API disclosure](./x-api-disclosure.md) | What is read from X and the commitments made about it. | | [Discord API disclosure](./discord-api-disclosure.md) | What is read from Discord and the commitments made about it. | | [Steam API disclosure](./steam-api-disclosure.md) | What is read from Steam for linking, game imports, and Steam auth verification, and the commitments made about it. | | [Chat Rules](./chat-rules.md) | What is and isn't allowed in chat (anything legal; nothing illegal; never any harm to children), the penalties up to a chat lock or suspension, chat tokens for IRC clients, and what chat keeps. Chat is not logged. | | [Subprocessors](./subprocessors.md) | Third-party services that process data for Blazium Games, including Stripe and Coinbase for payments. | For how to link, log in with, and unlink GitHub, X, and Discord, and how to link Steam, see the [Linked accounts and sign-in](../linked-accounts.md) guide. ## When these pages change Each page has a version date. You accept the Terms of Service and Privacy Policy when you sign up. When either changes, you are asked to accept the new version the next time you sign in, after your second sign-in step, with a short summary of what changed and a link to the full text. You can't use your account on the website until you accept or log out, though connected agents and MCP keys keep working. The other pages here don't need acceptance. See [Account security and sign-in](../account-security.md#after-you-sign-in). ## Contacts - Privacy questions and account deletion: [privacy@blazium.games](mailto:privacy@blazium.games). Deletion requests are processed within 30 days. - Copyright and DMCA notices: only through the paid form at [blazium.games/dmca](https://blazium.games/dmca) ($100, plus $100 per uploader account, not refundable). Email to [dmca@blazium.games](mailto:dmca@blazium.games) gets an automatic reply with a link to the form. See [Copyright (DMCA) notices](../storefront/dmca.md) and [section 17.1 of the Terms](https://blazium.games/terms-of-service#171-copyright-and-dmca-notices). - Everything else: [support@blazium.games](mailto:support@blazium.games), or see [Support](https://blazium.games/support). For how payments work in practice, see [Payments](../payments/index.md). # docs/legal/permissions.md :::note Canonical version: https://blazium.games/permissions ::: # Permissions & Scopes **Effective Date: November 3, 2026** This page lists every permission Blazium Games asks for, why we need it, and what we will never do with it. It sits alongside our [Privacy Policy](https://blazium.games/privacy-policy), [Subprocessors](./subprocessors.md), and the API disclosures for [GitHub](./github-api-disclosure.md), [X](./x-api-disclosure.md), [Discord](./discord-api-disclosure.md), and [Steam](./steam-api-disclosure.md). For step-by-step instructions, see the [Linked accounts and sign-in](../linked-accounts.md) guide. ## Linked accounts and sign-in You can link GitHub, X, and Discord from [Linked accounts](https://blazium.games/settings/connections) and then use any of them to log in. - Signing in with GitHub, X, or Discord always continues on Blazium Games. A provider proof alone does not log you in. - If the service is already linked, you enter your password, then an authenticator code if you have set one up, or an emailed code if you have not. You can send another emailed code 30 seconds after the last one. A remembered browser does not skip this step. - If it is not linked and a verified GitHub or Discord email matches an existing account, you enter that account's password. A match links the service. A wrong password links nothing and creates nothing. - If it is not linked and there is no matching verified email, you set a username, email, and password, confirm a code sent to that inbox, then set up an authenticator app or skip it and confirm another emailed code. X does not provide an email, so that path always starts with the email you type. The account is created only after the inbox code matches. - Linking while you are already signed in, at Linked accounts, only attaches the service. It does not create an account. - Once you unlink an account, it can no longer be used to log in. - If your account has no password, you must keep at least one account linked. ## GitHub Scopes requested: `read:user` and `user:email`. ### Why we need it - To link GitHub to your account and let you log in with it. - We read your GitHub user ID, login, and your primary email address. A verified email is compared with existing accounts during sign-in and can be shown on the create form. We do not store it on its own. If GitHub does not report a verified email, you type an email instead. Sign-in and linking still continue. ### What we store - Your GitHub user ID and login, so we can recognize the linked account and show which one is linked. - The GitHub access token is used once during sign-in or linking and is never stored. ### We will never - Write to your repositories, issues, or any other GitHub data. - Act on GitHub on your behalf. - Ask for more scopes without updating this page first. Details: [GitHub API disclosure](./github-api-disclosure.md). ## X Scopes requested: `users.read` and `tweet.read`. X requires `tweet.read` alongside `users.read` to read your profile; we do not read your posts. ### Why we need it - To link X to your account and let you log in with it. - We make one request to X's `/2/users/me` and read your X user ID and username. X also returns your display name, which we ignore. ### What we store - Your X user ID and username. Nothing else. - The X access token is used once during sign-in or linking and is never stored. We do not request offline access, so we get no refresh token. ### We will never - Post, like, repost, follow, or send messages on X for you. - Read your posts, timeline, or direct messages. - Ask for more scopes without updating this page first. Details: [X API disclosure](./x-api-disclosure.md). ## Discord Scopes requested: `identify` and `email`. ### Why we need it - To link Discord to your account and let you log in with it. - We make one request to Discord's `/users/@me` and read your Discord user ID and username. If Discord marks your email verified, we compare it during sign-in and do not store it on its own. An unverified or missing email is ignored. ### What we store - Your Discord user ID and username. Nothing else. - Discord includes your email address, display name, and avatar in its reply. We do not store the email, and we do not copy the display name or avatar. A verified email is compared during sign-in only. - The Discord access token is used once during sign-in or linking and is never stored. ### We will never - Join servers, read your servers or messages, or send messages for you. - Ask for more scopes without updating this page first. Details: [Discord API disclosure](./discord-api-disclosure.md). ## Steam Steam sign-in uses OpenID 2.0, which has no scopes and gives us no access token. ### Why we need it - To link Steam to your account, so games that use Steam auth verification can tell their servers which Blazium Games account you are. Steam cannot be used to log in here. - Steam returns your Steam ID, and we ask Steam to confirm the reply is genuine. We may then read your public Steam name. ### What we store - Your Steam ID and public Steam name. Nothing else. ### We will never - Read your Steam library or friends list. - Read your Steam inventory, or change it, except to grant an item you asked to move to Steam for a game whose developer turned transfers on. Details: [Steam API disclosure](./steam-api-disclosure.md). ## MCP access (OAuth) AI tools such as Cursor, VS Code, and Claude Code connect to one of two Blazium Games MCP servers. The developer server at `https://mcp.blazium.games/developer` manages your games. `https://mcp.blazium.games/mcp` still reaches that server. The player server at `https://mcp.blazium.games/player` acts for you as a player. When you approve a tool, it gets a token for one server only, with one or more of that server's scopes. A token never holds scopes for both servers, and neither server accepts the other's tokens or keys. | Scope | Server | Allows | | --- | --- | --- | | `mcp:read` | Developer | Reading your games, builds, analytics, crash reports, setup details, balance, and library. | | `mcp:write` | Developer | Creating and updating game pages, setting prices, issuing deploy keys, and (until October 28, 2026) buying from your balance within the limits you set, in addition to everything `mcp:read` allows. | | `mcp:catalog.write` | Developer | Changing game pages (text, taxonomy, similar titles, dependencies, engine compatibility, license kind, images, admins) and replying to player reviews. Reads of your profile and games are always included. | | `mcp:build.write` | Developer | Managing builds and release channels, and reading deploy info and scan status. | | `mcp:crash.read` | Developer | Reading crash reports and crash groups, running crash analysis, and reading the crash webhook setting and that game's signing key. | | `mcp:crash.write` | Developer | Changing crash webhooks and refreshing that game's signing key. Also covers the crash read routes. | | `mcp:bugs.read` | Developer | Reading player bug tickets and the in-game bug reporter settings, including that game's signing key. | | `mcp:bugs.write` | Developer | Updating bug tickets and changing the in-game bug reporter. | | `mcp:steam.manage` | Developer | Setting a game's Steam app id, Web API key, and ticket secret, and turning Steam auth on or off. The Web API key and ticket secret can be replaced but are never shown back. | | `mcp:analytics.read` | Developer | Reading visitor analytics and custom events. | | `mcp:keys.manage` | Developer | Listing and rotating deploy keys and MCP keys. | | `mcp:money` | Developer | Pricing, sales, game keys and gift links, wallet, library, and downloads. | | `mcp:anticheat` | Developer | Requesting anticheat for a game you own, and, after an NDA and a contract are signed, reading that game's anticheat reports and managing its server keys. Not included in `mcp:read` or `mcp:write`. | | `player:read` | Player | Reading your account, balance, wallet history, quotes, library, approvals, download links, the builds you can see, your reviews, recommendations, and your friends and what they're playing. | | `player:write` | Player | Verifying your email, recording play time, confirming an approval with the code you give the tool, joining or leaving a game's beta, writing or deleting your reviews, "more/less like this" feedback, filing bug reports, sending and answering friend requests, setting your presence and activity sharing, and redeeming game keys. | | `player:buy` | Player | Topping up and buying games or donating from your balance within the limits you set. Granted only if you tick **Allow purchases**. | ### Why we need it - So your AI tool can manage your store pages and read your game's data without you pasting passwords. ### How it is limited - The consent screen has a **Read-only access** option. Tick it and the tool only gets `mcp:read` (or `player:read`); any attempt to change data is refused. - On the developer server you can pick a narrower preset on the consent screen (store page, CI, crash triage, bugs, Steam, keys, money, anticheat, or read-only), so the tool only gets the scopes that job needs. Anticheat is its own preset. Full access does not include it. See [Anticheat](../anticheat.md). - On the player server the tool can't buy unless you tick **Allow purchases**. - Over MCP, rotating or creating MCP and deploy keys, deleting a deploy key, promoting a build to stable, deleting a game or build, creating more than 100 game keys at once, and adding a project admin wait until you approve them by the emailed link or code, even with full access. - A token is either for your whole account or for a single game (project). A project token is refused (error 4030) for any other game and for account-level actions: your profile, balance, wallet, library, account analytics, MCP keys, creating games, and buying. - Access tokens last 1 hour. Refresh tokens last 30 days from when you approved the tool. Each refresh issues a new refresh token and the old one stops working; if an old one is used again, the whole chain is revoked and the tool has to ask you again. All of them stop working if your account is deleted. - Every request made with an MCP key or token is recorded in an audit log (key, game, method, and path). ### We will never - Accept a read-only token for a change. - Share your keys or tokens with third parties. ## Agent spending AI tools connected through MCP can buy games and send donations for you, but only if you allow it. ### How it is limited - Every agent starts on **Ask me each time**: each purchase or donation waits until you approve it by the emailed link or code. Each MCP API key and each OAuth-connected app is a separate agent with its own setting. - At [blazium.games/settings/mcp](https://blazium.games/settings/mcp) you can let an agent spend on its own: unlimited, or up to a monthly, yearly, or one-time limit (up to $1,000, UTC periods). Anything beyond the limit waits for your approval. Agents cannot change their own limits. - An approval covers one purchase, for the amount shown, and expires after 30 minutes. - The limit counts each purchase's total, including tax. Refunded purchases stop counting. - Buying needs a player token with `player:buy`. Read-only and single-game (project) tokens can never buy (error 4030). A developer token gets error 4034. - Agents pay only from your account balance, never by card. They cannot request refunds. - Your email must be verified before agents can buy. - Each agent purchase is recorded with the agent that made it, and shows in your wallet transactions and library. ### We will never - Let an agent charge your card. - Let an agent spend beyond the limit you set without your approval. - Let an agent send your earnings anywhere except the payout account on your own account. ## Agent payouts An agent can send you to Balance. A cash-out always waits until you approve it, including a player key. - Wallet access means a player token with `player:buy`, or a developer token with `mcp:write` or `mcp:money`. Read-only and single-game (project) tokens cannot. - `start_payout_setup` and `get_payout_dashboard_link` return the Balance page. You open Stripe from Set up payouts with Stripe. Identity, tax, and bank details are entered on Stripe only after you open that page, and they never pass through the agent or us. - An agent can ask to cash out available earnings of $25 or more. The cash-out fee is 8% + $0.25, 7% + $0.25, or 6% + $0.25, from the best plan that account owns. You approve each cash-out, including when the agent used a player key. The transfer goes only to the Express account on that same account. - We email you after every cash-out an agent makes, with the amount and the agent's name. - Your email must be verified before agents can set up payouts or cash out. - Payouts are processed on weekdays from 8:00am to 5:00pm Pacific. - To stop an agent, revoke its key or disconnect it at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). ## Keys - **MCP keys** (account keys and project keys) are shown once when you create them and are stored only as a hash. You can rotate them at [blazium.games/settings/mcp](https://blazium.games/settings/mcp) or on a game's MCP tab; rotating invalidates the previous key. - **Player keys** (starting `bgames_play_`) work only on the player server. They are shown once, stored only as a hash, and rotated at [blazium.games/settings/mcp](https://blazium.games/settings/mcp) separately from MCP keys. - **Deploy keys** are two values for one project: an access token and a secret. chauffeur and CI need both. The access token stays on the Deploy keys tab. The secret is shown once. Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. - **Steamworks Web API keys** that developers enter to import a game from Steam are used for that import and discarded. With Steam auth verification on, the key is stored encrypted, never shown again, and never available to AI agents. - **Steam auth keys** (128 characters) sign a game's Steam session tokens and let its servers call Blazium Games. They are stored encrypted, can be shown to the game's owner and admins on its Steam tab, and are never available to AI agents. Making a new one revokes every session token. ## Cookies Sign-in cookies are always on because the site does not work without them. They are HTTPS-only, hidden from page scripts, and `SameSite=Lax`, so other sites can't make signed-in requests with them. Cookies whose names start with `__Host-` belong to the exact host that set them: no other blazium.games site, including people's profile and project sites, can read or replace them. Analytics cookies are only set if you accept them in the cookie banner. | Cookie | Purpose | Lifetime | Needs consent | | --- | --- | --- | --- | | `__Host-BG_T` | Your signed-in session on blazium.games. | 7 days | No | | `__Host-BG_UD` | Your display name, username, and avatar for the header. | 7 days | No | | `__Host-BG_STORE` | A separate session for store pages on other blazium.games hosts. It can buy and use your library, but cannot change account settings. It is handed over through a one-time code that works once, for 60 seconds. | 7 days | No | | `__Host-BG_CSRF` | A random value that every form on the site must echo back, so another site cannot submit forms as you. | 7 days | No | | `__Host-BG_DEV` | Remembers a browser that verified an emailed sign-in code, for email-and-password sign-in when no authenticator app is set up. Survives logout. It does not skip an authenticator code. | 30 days | No | | `__Host-BG_NEXT` | Returns you to the page you came from after logging in with GitHub, X, or Discord. | 15 minutes | No | | `__Host-BG_STATE` | Ties a GitHub, X, or Discord sign-in, or a Steam link, to the browser that started it. | 15 minutes | No | | `__Host-BG_SETUP` | Finishes setup for an email account that has not completed it. | 15 minutes | No | | `__Host-BG_ENROLL` | Carries a sign-in until you finish your password and a second step. | 15 minutes | No | | `__Host-BG_FACTOR` | Finishes authenticator setup, then shows recovery codes once. | 15 minutes | No | | `BG_IN` | Tells other blazium.games hosts that you are signed in, so store pages know to fetch their own session. It is set for the whole blazium.games domain and holds no credential. | 7 days | No | | `BG_CONSENT` | Remembers your cookie banner choice. | 1 year | No | | `__Host-BG_MCP` | On mcp.blazium.games only: a pass that lets you approve an AI agent's access. It can only read your account and project list, is signed by the MCP server, and is not your blazium.games session. Signing out of blazium.games ends it. | 7 days | No | | `_ga`, `_ga_*` | Google Analytics. | Up to 2 years (set by Google) | Yes | Game pages also keep a visit session ID in your browser's session storage. It is cleared when you close the tab. You can change your choice at any time with **Cookie settings** in the blazium.games footer. Declining removes the Google Analytics cookies. ## Revoking access - **Linked accounts:** unlink GitHub, X, or Discord at [blazium.games/settings/connections](https://blazium.games/settings/connections). An unlinked account can no longer log in. If you have no password, the last linked account cannot be removed until you set one or link another. - Removing Blazium Games in the other service's settings does not unlink it here. Unlink it at [blazium.games/settings/connections](https://blazium.games/settings/connections) to stop it logging in. - **GitHub:** remove Blazium Games under [GitHub > Settings > Applications > Authorized OAuth Apps](https://github.com/settings/applications). - **X:** remove Blazium Games under [X > Settings > Security and account access > Apps and sessions](https://x.com/settings/connected_apps). - **Discord:** remove Blazium Games under Discord **User Settings > Authorized Apps**. - **Steam:** OpenID gives Blazium Games no ongoing access, so there is nothing to remove on Steam. Unlink it at [blazium.games/settings/connections](https://blazium.games/settings/connections). - **Agent spending:** set any agent back to **Ask me each time** at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). - **MCP keys and tokens:** rotate keys at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). OAuth access tokens expire after 1 hour and refresh tokens after 30 days; all of them stop working when your account is deleted. - **Everything:** email [privacy@blazium.games](mailto:privacy@blazium.games) to delete your account. See the [Privacy Policy](https://blazium.games/privacy-policy#6-deleting-your-account). ## For developers: how scopes behave These are the responses your MCP client, script, or CI job will see. | Situation | HTTP status | Error code | Message | | --- | --- | --- | --- | | A token without `mcp:write` makes anything other than a `GET` or `HEAD` request (for example `create_game`, `update_game`, `request_deploy_key`, `request_mcp_key`) | 403 | 4031 | This token is read-only | | A project token is used for a different game | 403 | 4030 | This token is limited to one project | | The game's owner turned off MCP access for admins, and an admin's token is used on it | 403 | 4080 | The project owner has turned off MCP access for admins | | A project token tries to buy | 403 | 4212 | This token can't make purchases | | A player token without `player:buy` tries to top up, buy, set up payouts, or cash out | 403 | 4212 | This token can't make purchases or cash out; reconnect and allow purchases | | A player token is used outside the player routes | 403 | 4033 | Player tokens cannot use this route | | A developer token is used on a player route | 403 | 4033 | Player routes need a player token | | A token holds both developer and player scopes | 403 | 4032 | This token mixes developer and player scopes | | A token's narrower developer scopes don't cover the route | 403 | 4073 | This token's scopes don't cover this route | | An agent purchase needs your approval (no limit set, or over the limit) | 202 | 4214 | Approval required; the response includes the approval | | An agent rotates or creates a key, promotes to stable, or deletes a game or build | 202 | 4214 | Approval required; the response includes the approval | | You denied the agent's request | 403 | 4215 | The account owner denied this request | | The agent sent a wrong or expired approval code | 400 | 4216 | Wrong or expired code | | An agent tries to pay by card | 403 | 4082 | Agents pay from the balance | | An MCP token is used to change agent limits | 403 | 4083 or 4081 | Only available on blazium.games | | The account's email is not verified and it tries to buy, download, set up payouts, or cash out | 403 | 4096 | Verify your email first | | The token expired, or the account was deleted | 401 | 4003 or 4007 | Invalid or expired authentication token, or User account not found | - Account MCP keys and website sessions carry both scopes. OAuth tokens carry what the user approved. - The MCP tools that only read (`get_game`, `list_games`, `get_game_analytics`, `list_game_crashes`, `get_deploy_info`, and so on) work with a read-only token. - `request_mcp_key` and `list_mcp_keys` need an account-level token, not a project token. ### Deploy keys - A deploy key is two values for one project: an access token and a secret. chauffeur and CI need both. The access token is `BLAZIUM_ACCESS_TOKEN`, sent as `X-Access-Token`. It stays on the Deploy keys tab. The secret is `BLAZIUM_SECRET_KEY`, sent as `X-Secret-Key`. It is shown once. Copy it before you leave the page. It cannot be shown again. - `request_deploy_key` replaces the previous key and returns both values once, after the project owner approves. The access token can be copied later from the Deploy keys tab. The secret cannot. Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. - Deploy keys can register builds, upload build files and debug symbols, upload store images, read the game's basic details (`chauffeur info`), and list that game's bug reports and download their screenshot and log (`chauffeur bugs`). They cannot edit the store page text or settings, read analytics or crash dumps, or change a ticket's status. - See [Deploy builds](../deploy.md) and [Access and keys](../mcp/access-and-keys.md). # docs/legal/steam-api-disclosure.md :::note Canonical version: https://blazium.games/steam-api-disclosure ::: # Steam API Disclosure **Effective Date: October 15, 2026** Blazium Games uses Steam in four ways: to link a Steam account to yours, to import a game's Steam store page for its developer, to check Steam sign-ins for games whose developers turn on Steam auth verification, and, when that developer has also turned on inventory transfers, to move item definitions and the items a player asks to move. This page explains what we access in each case and the commitments we make about it. ## Linking Steam Steam sign-in uses OpenID 2.0. It has no scopes and gives us no access token. - When you link Steam at [Linked accounts](https://blazium.games/settings/connections), Steam sends you back to us with your Steam ID. We ask Steam to confirm the reply is genuine before we use it. - We may then read your public Steam name with the Steam Web API's `GetPlayerSummaries`. - We keep your Steam ID and that name. Steam cannot be used to log in to Blazium Games. ## Importing a game (developers) A developer can copy a game's Steam store page into a listing. They give us the app ID and their Steamworks Web API key. - We check with Steam that the key belongs to a publisher of that app (`GetPartnerAppListForWebAPIKey`). - We read the public store page (`appdetails`), its tags (`IStoreBrowseService/GetItems` and `IStoreService/GetTagList`), and its images from Steam's image servers. - The key is used for that import and discarded, unless the developer turns on Steam auth verification. ## Steam auth verification (players) A developer can turn on Steam auth verification for their game. The game then sends us a Steam session ticket when you play. - We send the ticket to Steam with the developer's key (`AuthenticateUserTicket`). Steam returns your Steam ID, the owner's Steam ID if the game is borrowed through Family Sharing, and whether the account has a VAC or publisher ban. - We ask Steam whether your account owns the game (`CheckAppOwnership`). - If the account owns the game and has no publisher ban, we return a session token to the game, valid for 1 hour. - We keep a session record: your Steam ID, the owner's Steam ID, your Blazium Games account if you linked Steam, when the token expires, whether it was revoked, and your IP address. The record is deleted 30 days after the token expires. The ticket itself is not stored. - The developer's servers can check the token and ask whether a Steam ID owns the game. They see your Steam ID, whether you own the game, whether Steam reports a VAC ban, and your Blazium Games user ID if you linked Steam. ## Item inventory (players) A developer who has turned on Steam auth verification can also turn on inventory for that game, and then turn on transfers. Both switches stay on. - Inventory keeps each item on Blazium Games. We do not read your Steam inventory for that. - A transfer to Steam runs only when you ask, for an item you own, after you have a license and have logged in to that game at least once with the linked Steam account. The item's definition must already be on Steam. The call is Steam's `IInventoryService/AddItem`. Items are not moved back onto Blazium Games. - A schema sync, overwrite, or addon updates item definitions. It does not move the items you hold. - We do not read your Steam library, friends list, or messages. ## Our commitments - We never store Steam session tickets. - We never read your Steam library, friends, or messages. - We read or change a Steam item inventory only for a game whose developer turned transfers on, and only for an item that game asked to move. - We store a developer's Steamworks Web API key only while Steam auth verification is on, encrypted, and never show it again or make it available to AI agents. - We never use Steam data for advertising. - We never use Steam data to train AI or machine-learning models. - We never sell Steam data or share it with third parties, except the developer of the game you played as described above and the [subprocessors](./subprocessors.md) that host our service. ## Revoking access and deleting data - Unlink Steam at [Linked accounts](https://blazium.games/settings/connections). Games then no longer learn your Blazium Games account from Steam. - OpenID gives us no ongoing access, so there is nothing to remove in your Steam settings. - A game's developer can revoke its session tokens at any time, and turning off Steam auth verification revokes them all. - To delete your account and the Steam link, email [privacy@blazium.games](mailto:privacy@blazium.games). We process deletion requests within 30 days, and Steam game sessions stop naming your account. See the [Privacy Policy](https://blazium.games/privacy-policy#6-deleting-your-account) for what deletion covers. See also the [GitHub API disclosure](./github-api-disclosure.md), the [X API disclosure](./x-api-disclosure.md), the [Discord API disclosure](./discord-api-disclosure.md), [Permissions & Scopes](./permissions.md), and the [Steam import](../steam-import.md) and [Steam auth verification](../steam-auth.md) guides. ## Contact Questions about this disclosure: [privacy@blazium.games](mailto:privacy@blazium.games). Steam and the Steam logo are trademarks of Valve Corporation. Blazium Games is not affiliated with Valve. # docs/legal/subprocessors.md :::note Canonical version: https://blazium.games/subprocessors ::: # Subprocessors **Effective Date: October 8, 2026** These are the third-party services that process data on behalf of Divine Games, Inc., which operates Blazium Games. We will update this page before adding a new subprocessor. | Subprocessor | What it does for us | Data involved | Location | | --- | --- | --- | --- | | DigitalOcean | Cloud hosting, databases, file storage, and content delivery. | All account, game, analytics, and crash data; uploaded files and builds. | United States | | GitHub | GitHub Actions for our CI, and GitHub Pages for this documentation. Signing in with GitHub is covered below. | Source code and build logs. | United States | | Google Analytics | Site usage statistics. **Only runs if you accept analytics cookies.** | Pages visited, device and browser details, approximate location. | United States | | Google STUN server | Part of the browser fingerprint used for visit analytics. **Only contacted if you accept analytics cookies.** | Your IP address, as seen by Google's server. | United States | | Stripe | Card payments (Checkout), sales tax calculation (Stripe Tax), refunds, disputes, USDC payment records, and payouts to developers through Stripe Connect. | Email address, display name, an internal account ID, billing address, payment details (entered on Stripe's pages, never sent to us), purchase and top-up amounts, and for developers the identity, tax, and bank details Stripe Connect collects. For balance purchases with no billing address, your IP address is used to estimate tax. | United States | | Coinbase (Developer Platform) | Checks and settles USDC top-ups made with x402. | The signed payment from your wallet, including your wallet address, the amount, and the network. | United States | | Valve (Steam Web API) | Checks Steam session tickets and game ownership for games that turn on Steam auth verification, confirms the Steam sign-in when you link Steam, and supplies the public store page when a developer imports a game. | The Steam session ticket a game sends, Steam IDs, the app ID, and the developer's Steamworks Web API key. | United States | | Discord | Internal team communication and operational notifications. | Limited details from support messages, crash reports, and account or payment events. | United States | ## What we run ourselves These are not subprocessors, because we operate them on our own servers: - **Game sign-in, lobbies, and peer connections:** these run on our own servers. DigitalOcean hosts the machines. No extra company sits in that path. - **Mail:** our own mail service handles mail to and from @blazium.games. - **Virus scanning:** uploaded files are scanned with an open-source malware scanner. - **Country lookup:** we turn IP addresses into countries with a local copy of the MaxMind GeoLite2 database. No IP address is sent to MaxMind. This product includes GeoLite2 data created by MaxMind, available from [maxmind.com](https://www.maxmind.com). - **Logs:** request and error logs are written by our own services. - **Fonts:** the Nunito typeface is a file we serve from blazium.games. Loading a page does not contact a font host. ## Accounts you connect are not subprocessors When you link GitHub, X, Discord, or Steam at [Linked accounts](https://blazium.games/settings/connections), or log in with one of them, that service is acting for you, not for us. What it does with your data is covered by its own privacy policy. We keep only the account's user ID and username. See our [GitHub API disclosure](./github-api-disclosure.md), [X API disclosure](./x-api-disclosure.md), [Discord API disclosure](./discord-api-disclosure.md), and [Steam API disclosure](./steam-api-disclosure.md) for what each service returns. See [Permissions & Scopes](./permissions.md) for the exact scopes we request from each one. ## Contact Questions about subprocessors: [privacy@blazium.games](mailto:privacy@blazium.games). # docs/legal/terms-of-service.md :::note Canonical version: https://blazium.games/terms-of-service ::: # Terms of Service **Effective Date: November 4, 2026** These Terms of Service ("Terms") are a contract between you and Divine Games, Inc., a California corporation that runs its business from Arizona ("Divine Games," "we," "us," or "our"). Divine Games operates Blazium Games at Blazium.games (the "Service"). The Service is a game publishing platform, with an infrastructure focus, for independent creators to upload, distribute, share, and sell digital content such as games, assets, tools, music, and other creative works (collectively, "Content"). Creators decide whether their Content is free or paid. By creating an account, listing, buying, donating, uploading, downloading, or otherwise using the Service, you agree to these Terms. If you do not agree, do not use the Service. ## 1. The Service in Plain Language - **A publishing platform.** Creators list and sell Content, and players buy, download, and donate. A sale is between the buyer and the Creator. We are not the seller of a Creator's Content; we take the payment, deliver the files, and keep a disclosed fee. - **A balance.** Money you add, and money Creators earn, is recorded in a balance on your account. You can spend it on the Service, and Creators can cash out their earnings, subject to the holds, fees, and checks in sections 9 and 10. We are not a bank. - **United States law.** These Terms are governed only by the law of the United States and the State of Arizona (section 5). Courts, regulators, and other authorities outside the United States have no role in this contract. ## 2. Eligibility - You must be at least 13 years old to use the Service as a downloader or viewer ("User"). - To upload or distribute Content ("Creator"), you must be at least 18 years old or have the legal capacity to enter into contracts. - To buy Content, add money to your account, or cash out, you must be at least 18 years old or have permission from a parent or guardian who accepts these Terms for you. - The Service is not intended for children under 13, and no one under 13 may use it. ## 3. Accounts - You must create an account to access certain features, such as uploading, buying, or downloading Content. - You must verify your email address before you can publish Content, upload builds, buy Content, or download files. - **A person or a company holds every account.** An AI system is not a party to these Terms and cannot own an account. You may use a script, tool, or AI agent to sign up or act on your account, but you are the account holder and you are bound by everything it does, including purchases, listings, uploads, donations, and messages (see section 13). - Do not use an AI agent or any other means to evade a ban, create accounts you are not allowed to hold, misstate your age or identity, or hide who controls an account. We may ask for proof that a person controls an account, and close it if none is given. - You are responsible for keeping your credentials, keys, and tokens confidential and for all activity under your account. - You agree to provide accurate information and notify us of any unauthorized use. - You must accept these Terms and the [Privacy Policy](https://blazium.games/privacy-policy) when you create an account. We record which version you accepted and when. - After you sign in, you finish any account setup you left incomplete, and you either set up an authenticator app or choose to skip it. We record that choice; you can set one up later in [Settings](https://blazium.games/settings/authenticator). ## 4. Where You Use the Service From - The Service is offered from the United States and is run under United States law. Access from outside the United States is allowed as a convenience that we may withdraw at any time. - We do not tailor the Service to the laws of other countries. We do not block Content, geoblock, or change these Terms because the law of another country asks for it. - If you use the Service from a place whose laws conflict with United States law or with these Terms, that conflict is yours to resolve. You are responsible for making sure your use is lawful where you are. ## 5. Governing Law, Venue, and Legal Process ### 5.1 United States law only These Terms, the Service, and any dispute arising out of or relating to them are governed by the laws of the United States and the State of Arizona, without regard to conflict-of-law rules that would point anywhere else. The United Nations Convention on Contracts for the International Sale of Goods does not apply. ### 5.2 Venue Disputes go exclusively to the state courts in Maricopa County, Arizona, or the United States District Court for the District of Arizona, except where United States law requires a different federal forum. You consent to that venue and to personal jurisdiction there. ### 5.3 Authorities outside the United States We decline requests from governments, courts, regulators, law enforcement, data-protection authorities, and private litigants outside the United States, including informal demands, preservation letters, and civil process issued outside the United States. We will not produce user data, identify a user, remove Content, or change the Service because an authority outside the United States asked. To the extent United States law allows, a judgment or order from outside the United States cannot be enforced against us through these Terms. ### 5.4 Your information needs a United States court order We do not reveal user, account, or balance information to anyone outside the Service unless a federal or state court of the United States has ordered the disclosure and the order has been properly served. A subpoena, letter, portal request, preservation demand, or phone call is not enough, and neither is an order from a court outside the United States. We may object to an order, ask to narrow it, or seek a protective order before producing anything. The only exception is a report a United States statute requires us to make, such as a report of child sexual abuse material (section 17). ### 5.5 Inquiries - We do not answer unsolicited inquiries about Users, including researcher requests, identity requests from other Users, and informal contacts from government agencies. We do not confirm or deny that a person has an account. - Media and press outreach is accepted only at [support@blazium.games](mailto:support@blazium.games), and only after we have validated the sender's credentials. Outreach that arrives any other way, or without credentials we have validated, is ignored. No reply means no. ### 5.6 Sanctions and United States compliance We may refuse service, block a transaction, or close an account to comply with United States sanctions, export-control, and anti-money-laundering laws, including the Office of Foreign Assets Control sanctions lists. ## 6. Creator Content and Ownership - Creators retain full ownership of their uploaded Content. These Terms do not transfer it to us, to a buyer, or to any other User. - By uploading Content, you grant us a worldwide, non-exclusive, royalty-free, sublicensable license to host, reproduce, transcode, cache, display, distribute, and promote the Content in connection with the Service. The license lasts while the Content is on the Service and for any copies United States law requires us to keep. - You represent and warrant that you have the right to distribute your Content, that it does not infringe third-party rights, that it is not unlawful, and that it complies with these Terms. You remain liable to rights holders for what you upload and sell (see section 25). - You are solely responsible for providing support for your Content, if any. - **Storage.** We host your files as-is. We do not promise a particular uptime, region, or retention period, so keep your own copies. - **Unlisting.** You can unlist or remove your Content at any time. Unlisting stops new sales but does not revoke licenses already granted (section 7). ## 7. User Licenses - When you download Content, the Creator grants you a non-exclusive, personal license to use the Content as permitted by the Creator's settings (e.g., for personal use, modification if allowed). - For paid Content, you receive the license when your payment is complete. - You may not redistribute or commercially exploit downloaded Content unless explicitly permitted by the Creator. - Licenses are perpetual for downloaded Content, even if the Content is later removed from the Service. A license to paid Content ends if the purchase is refunded or the payment is reversed by a chargeback. - Files can only be downloaded while your account exists, the Content is still on the Service (public, or unlisted but reachable by link), and, for paid Content, while you hold a license. If the Creator makes the Content private or deletes it, you keep your license and any copies you already downloaded, but we no longer deliver the files. - **Game keys.** Creators can make single-use keys and gift links for their Content. Redeeming one gives you the same license as a purchase, without payment. Each key works once. Keys are not for sale: you may not sell or trade them, and we may revoke licenses from keys that were stolen, resold, or obtained by abuse. ## 8. Payments and Fees - **Prices.** Creators set the price of paid Content, from $0.99 to $500 USD. Creators of free Content can accept donations from $1 to $500 USD. All prices are in US dollars. - **What buyers pay.** The price, plus any sales tax, plus a card processing fee shown at checkout when paying by card. Paying from your account balance adds no processing fee. - **What Creators receive.** For each sale or donation we keep a sale fee of $0.25 plus 8% of the price. The rest is credited to the Creator's balance. - **Donations.** A donation is a voluntary gift to a Creator, not a purchase, and it is not refundable (section 11). If a "donation" is really payment for something, it is a sale and must be treated as one. - **Payment processing.** Card payments, tax calculation, and payouts are handled by Stripe. USDC top-ups are settled through Coinbase's x402 facilitator and Stripe. Your use of these payment methods is also subject to their terms. - Buyers are responsible for reading the listing, including the license, supported platforms, and engine compatibility. - We may change fees with at least 30 days' notice. Changes do not apply to purchases made before they take effect. ## 9. Account Balance Your account can hold money in three parts: - **Credit:** money you add by card or USDC ($5 to $500 per top-up), and refunds of purchases paid from your balance. Credit can be spent on Content on the Service. It **cannot be withdrawn or cashed out**, and it is not refundable except where the law requires. - **Pending:** a Creator's earnings from sales that can still be refunded. - **Available:** a Creator's earnings from sales past the refund window. Available earnings can be spent or cashed out. - **Not a bank.** Your balance is a record of amounts we owe you or that you can spend on the Service. It is not a bank account or deposit, it does not earn interest, and it is not insured by the FDIC, the NCUA, or any government agency. We are not a bank, trust company, or credit union. - **Corrections and holds.** We may correct balance errors, and we may hold or reverse amounts linked to fraud, chargebacks, sanctions screening, or a breach of these Terms. Held amounts cannot be spent or cashed out. - **Negative balances.** You authorize us to debit your balance for refunds, chargebacks, and the fees tied to them. If that leaves your balance below zero, you owe the difference, and we may recover it from later earnings and refuse cash-outs until it is paid. - We may limit who can add money or cash out, for example by country or payment method, to comply with United States law. ## 10. Cash-Outs - Blazium is the marketplace. The buyer pays Blazium. Blazium keeps $0.25 + 8% of the price. The rest is the creator's earnings. A game sale, a donation, and a patron charge credit the creator's balance and can be cashed out. A Premium or Business subscription is charged to the subscriber and is not transferred to an Express account. A top-up becomes credit and cannot be cashed out. USDC cash-out does not use Stripe. - Creators can cash out available earnings of $25 USD or more. The transfer goes only to the Express account on that same account. Stripe is available for United States accounts. - To cash out you must complete Stripe's identity verification and tax information checks. You are responsible for supplying accurate information, such as your legal name, address, and tax forms. Stripe may refuse or delay payouts under its own rules, and we may hold cash-outs until verification is complete. - Each cash-out costs 8% + $0.25 when every game you own is Free, 7% + $0.25 when the best plan you own is Premium, or 6% + $0.25 when the best plan you own is Business. The remaining amount is transferred to your Express account and then paid to your bank. Identity, tax, and bank details are entered on Stripe's hosted onboarding. The Express dashboard is where you see the payout to your bank. Blazium pays Stripe's processing fees and is responsible for a negative balance. A refund or dispute stays on Blazium's balance. Stripe does not reverse a transfer that was already sent. - **Timing.** Payouts are processed on weekdays from 8:00am to 5:00pm Pacific. Verification holds, tax-form holds, and Stripe's own reviews can add time after a payout is sent. - If a transfer fails or is reversed, the amount and fee are returned to your available balance. - We may refuse, delay, or reverse a cash-out that looks fraudulent, fails sanctions screening, or would leave your balance short of pending refunds and fees. - **Through an AI agent.** An agent can send you to Balance. You open Stripe from Set up payouts with Stripe on that page (section 13). Money is only ever sent to the Express account on your own account, and identity, tax, and bank details are entered by you on Stripe's own pages. ## 11. Refunds and Chargebacks - A purchase can be refunded until **7 days** have passed or you have played the game for **2 hours**, whichever comes first. - **Donations are not refundable**, except where the law requires a refund or we reverse a donation tied to fraud. A chargeback on a donation is handled as described below. - Content you got from a game key or gift link was not bought, so there is nothing to refund. - To ask for a refund, email [support@blazium.games](mailto:support@blazium.games) from your account email. We may also refund outside this window at our discretion, for example for a broken build. - A refund credits your Blazium account with the price plus tax, minus the platform fee. The card processing fee and the platform fee are not returned. Nothing is sent to a card, a bank, or a USDC address. Getting money out is a payout you request. - A refund of a purchase is credited to your account balance, which cannot be cashed out. - When a purchase is refunded, the license is revoked and the Creator's earnings from that sale are taken back. The platform fee is not returned. - If you dispute a card payment with your bank (a chargeback), the license is revoked while the dispute is open and the Creator's earnings from that sale are held. We may suspend accounts that file chargebacks in bad faith. - Nothing in these Terms limits refund rights you have under the law where you live. ## 12. Taxes - **Sales tax.** We calculate and collect sales tax, VAT, or similar taxes on purchases where we are required to, based on your billing address or location. Donations and balance top-ups are not taxed. - **Everything else is yours.** You are responsible for working out whether what you earn, receive, spend, or cash out is taxable, and for reporting and paying those taxes, including income and self-employment tax, keeping your own records, and any receipts your buyers or donors need. We do not give tax advice, and a balance credit, donation, or cash-out is not a statement about how it is taxed. - If United States law requires us or Stripe to collect a tax form, withhold, or file an information return before a payout can be sent, we may do that and hold the cash-out until you supply what is needed. That does not move your tax obligations to us. You will reimburse any tax, penalty, or cost assessed because your information was missing or wrong. ## 13. Purchases and Actions by AI Agents - You can let AI tools connected through our MCP server act for you. Anything an agent does on your account is done by you. - An agent can only buy if you granted it the `player:buy` permission on the player server (developer tokens for your whole account can also buy until October 28, 2026). By default each agent's purchase waits until you approve it by emailed link or code. - At [MCP settings](https://blazium.games/settings/mcp) you can let an agent spend on its own: without a limit, or up to a monthly, yearly, or one-time limit of up to $1,000 (UTC periods). Anything beyond that still needs your approval. Agents can only pay from your account balance, never by card, and cannot change their own limits. - An agent with access to your wallet (the `player:buy` permission on the player server, or `mcp:write` or `mcp:money` on the developer server) can send you to Balance. `start_payout_setup` and `get_payout_dashboard_link` return that page. You open Stripe from Set up payouts with Stripe. A cash-out always waits until you approve it, whether the agent used a developer key or a player key. The cash-out fee is 8% + $0.25, 7% + $0.25, or 6% + $0.25, from the best plan that account owns. The transfer goes only to the Express account on that same account, and we email you after every cash-out an agent makes. Only give that access to agents you trust, and revoke their keys at [MCP settings](https://blazium.games/settings/mcp) if something looks wrong. - Purchases an agent makes within the limits you set, or that you approve, are purchases made by you. The refund rules in section 11 apply to them the same way. ## 14. User-Generated Content (UGC) - The Service allows comments, reviews, forums, profiles, and chat ("UGC"). - You retain ownership of your UGC but grant us a perpetual, worldwide, non-exclusive license to use, display, and moderate it. - UGC must not be harmful, illegal, infringing, or violate community guidelines (e.g., spam, or harassment). ## 15. Prohibited Conduct You agree not to: - Upload malicious code, viruses, or harmful content. - Impersonate others or infringe intellectual property. - Use the Service for illegal purposes, including money laundering or buying with stolen payment methods. - Attempt to hack, reverse engineer, or interfere with the Service, or attempt to hack or socially engineer us or another User. - Run bots or botnets against the Service or its Users. - Remove access to downloaded Content from users without justification. - Manipulate sales, refunds, or balances, for example by buying your own Content or filing false chargebacks. We may remove Content, suspend accounts, or terminate access for violations. ## 16. Community Guidelines and Reports - Be respectful. No harassment, threats, or disruptive behavior. - Chat follows the [Chat Rules](https://blazium.games/chat-rules). Breaking them can lock your account out of chat, suspend it, or lead to harsher action. - You can report Content, Users, and reviews with the report buttons on the Service. Reports are input to our own decisions; filing one does not oblige us to act on it or to explain what we decided. - We may moderate and remove offending content or accounts at our discretion. ## 17. Moderation Is Our Decision - **No third-party takedowns or bans.** We do not remove Content, ban a User, or delete an account because someone outside the Service demands it. That includes other Users, rights holders, companies, foreign governments, and foreign courts. A demand, a report, or a public campaign is not an order we have agreed to follow. The one process we run for outside complainants is the paid copyright notice in section 17.1, and even then our staff decide what happens. - **Our discretion.** Whether to limit an account or the visibility of Content is our decision alone. We may delist an item from search or shelves, restrict a feature, limit distribution, or leave material as posted, for our own reasons. We do not owe anyone an explanation or an appeal. - **Refusing a demand is not a guarantee.** Declining a third party's demand does not mean we consider your Content non-infringing or lawful, and it does not make us responsible for it. - **Child sexual abuse material.** Content that is child sexual abuse material under United States law is never accepted, is not a discretion call, and is removed and reported as United States law requires. - **Media accounts.** We may remove a media, press, or news account, or an account held out as one, that we determine is being used in a scheme against the Service or its Users, such as fabricated credentials, coordinated harassment, impersonating us, or collecting User information under the cover of reporting. ### 17.1 Copyright and DMCA Notices - **Only through the DMCA page.** We accept copyright notices, including notices under the Digital Millennium Copyright Act, only through the paid form at [blazium.games/dmca](https://blazium.games/dmca). Notices sent by email, post, phone, or any other way are not filed and are not acted on. If you email a notice to [dmca@blazium.games](mailto:dmca@blazium.games), you get an automatic reply with a link to the form, filled in with your email address and any links from your message. - **Registered agent.** Our designated agent for notices under the Digital Millennium Copyright Act is registered with the United States Copyright Office as DMCA-1085117. The agent is reached only through the form at blazium.games/dmca. - **The filing fee.** Filing costs $100, plus $100 for each uploader account the links in the notice belong to. The form shows the total before you pay, and the notice is filed only once the fee is paid. The fee covers reviewing and verifying the claim. The notice work is performed when the fee is paid. **The fee is not refundable**, whether the claim is accepted, rejected, resolved, closed, or withdrawn. A refund or chargeback started in Stripe is noted on the claim. The claim stays open, and the fee is not returned. - **What a notice must include.** The links to the Content on the Service, a description of the work you say is infringed, your name, postal address, phone number, and email address, a statement of good faith belief that the use is not authorized, a statement under penalty of perjury that the notice is accurate and that you own or are authorized to act for the owner of the right, and your signature. - **We forward notices to the uploader.** After the fee is paid, we forward the notice, including the sender's name, company, and email address, to each uploader named in it. Uploaders can also see it in their account settings and through our developer tools for AI agents. Our staff alone see the sender's postal address and phone number. We keep the sender's IP address and browser information to prevent fraud and abuse. We do not give the sender the uploader's identity or contact details; that needs a United States court order (section 5.4). - **Staff review.** Our staff review each paid notice and may ask the sender or the uploader for more information. Whether a claim is valid, and what to do about it, is our decision alone (section 17). If we decide a claim is valid, we may disable or remove the Content named in it, and we may suspend or ban the account that uploaded it. If we decide a claim is not valid, we close it and leave the Content as posted. Filing a notice does not mean the Content will be removed, and we do not owe the sender or the uploader an explanation or an appeal. - **Records are preserved during a claim.** While a claim is open, we keep a record of each named listing and file as it was when the notice was filed, even if the uploader changes or deletes it. - **The uploader's part.** If a notice names your Content, you may answer the sender directly, send us anything relevant to the review by emailing [dmca@blazium.games](mailto:dmca@blazium.games) with the claim reference in the subject, and delete a listing or any of its builds yourself at any time. You are responsible for your Content and remain liable to rights holders for it (sections 6 and 25). - **Not legal advice.** Forwarding a notice or deciding a claim is not legal advice and not an admission by us, the sender, or the uploader that Content does or does not infringe. We do not process formal counter-notices. Action on an account is decided claim by claim; we do not run a fixed repeat-infringer policy. ## 18. Seizure of Assets for Abuse - **When.** We may seize and forfeit balances, earnings, listings, files, licenses, and other assets on the Service from an account used for nefarious purposes: botnets, money laundering or moving proceeds of crime, fraud, funding with stolen payment methods, attempts to hack the Service or another User, and social engineering of us or a User. We act on information we can document as proof, such as logs, payment traces, device or network patterns, listings, messages, chargeback data, and information from a payment partner. We decide whether it is enough; we do not need a third-party demand, a report, or a hearing. - **Related accounts.** A seizure covers the account used and accounts we link to it by payment method, payout destination, device, recovery address, operator, or pattern of transfers, including accounts created to get around a seizure. - **What transfers to us.** Available, held, and pending balances; cash-outs not yet completed or still recallable; sale proceeds and donations tied to the activity; the account's listings, files, and unsold Content on the Service; licenses and delivery rights the account holds on the Service; and the username and storefront used in the activity. You assign these interests to us when you use the Service, effective on our determination. Licenses that good-faith buyers already hold are not taken back from them. - **After a seizure.** We may hold, cash out, apply the value to losses and costs (chargebacks, refunds to Users who were harmed, investigation, and payment-partner fees), delete, or keep the seized property, and refuse further cash-outs from the seized or related accounts. - Seizure is a contract remedy for abuse of the Service and does not limit any other remedy. If United States law requires us to freeze, report, or turn over the property, we may do that instead. ## 19. Developer Terms Version 2026-09-30. These terms apply in addition to the rest of these Terms when you turn on developer mode. - **Developer mode.** Creating projects, joining a project team as an admin, deploy keys, and developer MCP keys need developer mode, which you turn on in your [account settings](https://blazium.games/settings) by accepting these developer terms. Playing, buying, and reviewing do not need it. When these developer terms change, we ask you to accept the new version; until you do, we may limit developer features. - **Your projects.** You are responsible for every project you own or help run, including its builds, store page, prices, and support. You may only upload builds and media you have the right to distribute. - **Honest listings.** Your store page, taxonomy, content warnings, adult rating, "made with" label, and generative-AI disclosure (section 21) must be accurate and kept up to date. Mods, plugins, and tools must name the game they are for, and you must have the right to distribute them for that game. - **Turning it off.** You can turn off developer mode after you transfer or delete your projects and leave the project teams you help run. Your earnings and past sales records are kept. - **Enforcement.** We may unlist projects, turn off developer mode, or suspend accounts that break these developer terms. ## 20. Content Ratings and Adult Content - Creators must mark a listing as **adult** if it contains sexual content or nudity, and add the matching content warnings. Other mature themes, such as violence, gore, drugs, gambling, or horror, need their content warnings. - Adult listings are only shown to logged-in Users who confirmed they are **18 or older** and turned on adult content in their settings. They are left out of search engines, sitemaps, and public shelves. - By turning on adult content you confirm you are 18 or older and that viewing it is legal where you live. You can turn it off at any time. - Content that sexualizes minors, depicts non-consensual sexual acts as real, or is otherwise illegal is never allowed, whether marked adult or not. We remove it and may report it to the authorities. - We may change a listing's rating or content warnings, or unlist it, if it is mislabeled. ## 21. Generative AI Disclosure - Creators must disclose where generative AI was used to make a listing (art, music and sound, code, writing, voices) and whether the game generates content with AI while it runs. The disclosure is shown on the store page and used by search filters. - The disclosure must be honest and complete. Leaving it empty means you used no generative AI for those parts. - You remain responsible for having the rights to everything in your Content, including anything made with generative AI. ## 22. Player Tags - Users who own a game and played it for at least one hour can suggest up to five tags for it. A tag shows on the store page once three Users suggest it. - Tags must describe the game. Abusive, misleading, or spam tags break section 15 and may be removed. Creators can hide player tags from their store page. ## 23. Disclaimers THE SERVICE, INCLUDING BALANCES AND CASH-OUTS, IS PROVIDED "AS IS" AND "AS AVAILABLE." TO THE FULLEST EXTENT UNITED STATES LAW ALLOWS, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT CONTENT IS LEGAL WHERE YOU LIVE, THAT FILES ARE FREE OF HARMFUL CODE, THAT STORED FILES WILL NOT BE LOST, OR THAT A CASH-OUT WILL CLEAR. We are not responsible for the quality or availability of Creator Content, or for disputes between Users and Creators. ## 24. Limitation of Liability TO THE FULLEST EXTENT UNITED STATES LAW ALLOWS, WE AND OUR DIRECTORS, OFFICERS, EMPLOYEES, AND AGENTS ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, DATA, OR GOODWILL, ARISING OUT OF THESE TERMS OR THE SERVICE, EVEN IF ADVISED OF THE POSSIBILITY. OUR TOTAL LIABILITY FOR ANY CLAIM ARISING OUT OF THESE TERMS OR THE SERVICE WILL NOT EXCEED THE GREATER OF (A) THE FEES YOU PAID US IN THE THREE MONTHS BEFORE THE CLAIM OR (B) ONE HUNDRED U.S. DOLLARS (US $100). This limit does not apply to liability that United States law does not allow to be limited, and it does not reduce amounts in your balance that we owe you under these Terms. ## 25. Indemnity You will defend and indemnify us and our directors, officers, employees, and agents against any claim, loss, or expense (including reasonable attorneys' fees) arising out of your Content, listings, donations, balance activity, taxes, use of an AI or other agent, breach of these Terms, or violation of law, including any claim by a tax authority, an authority outside the United States, or a person relying on foreign law that we should have collected, reported, or stopped something you did. ## 26. Termination - You may stop using the Service and close your account at any time. - We may terminate or suspend your access for violations of these Terms or under sections 17, 17.1, and 18. We do not close accounts just because a third party asked; a paid copyright notice is reviewed and decided by our staff (section 17.1). - Upon termination, your right to use the Service ends, but licenses to previously downloaded Content persist, except licenses revoked under section 11. - If your account is closed, contact [support@blazium.games](mailto:support@blazium.games) to cash out any available earnings to a verified payout account, less fees, pending refunds, and chargeback reserves, unless United States law requires us to hold them. Credit is not paid out in cash. - Sections that by their nature should survive, including governing law, venue, legal process, balance reconciliation, licenses already granted, disclaimers, limitation of liability, and indemnity, survive the end of your use. ## 27. Changes to Terms - We may update these Terms. The effective date at the top shows the current version. - When these Terms or the Privacy Policy change, we show you what changed the next time you sign in and ask you to accept the new version before you continue. Until you accept, you can still view your account, sign out, or ask us to delete it. - Significant changes will also be announced via email or in-Service notice. ## 28. General - **Entire agreement.** These Terms and the policies linked from them are the entire agreement between you and us about the Service. - **Severability.** If a court in the venue above holds a provision unenforceable, the rest stays in effect. - **No waiver.** Not enforcing a provision is not a waiver of it. - **Assignment.** You may not assign these Terms. We may assign them in connection with a merger, acquisition, or sale of assets. - **Force majeure.** We are not liable for failures caused by events outside our reasonable control. - **Language.** English controls if a translation conflicts. ## 29. Contact Blazium Games is operated by Divine Games, Inc., a California corporation that runs its business from Arizona. If you have any questions or concerns about these Terms, please contact us at [support@blazium.games](mailto:support@blazium.games). # docs/legal/x-api-disclosure.md :::note Canonical version: https://blazium.games/x-api-disclosure ::: # X API Disclosure **Effective Date: September 30, 2026** Blazium Games uses the X API only to link X to your account and let you log in with it. This page explains what we access and the commitments we make about it. ## What we access We request the `users.read` and `tweet.read` scopes. X requires `tweet.read` alongside `users.read` to read your profile; we do not read your posts. With them we make one request, to `GET /2/users/me`, and read: - your X user ID and username. X also returns your display name with your profile. We ignore it. We do not request `offline.access`, so X gives us no refresh token. ## How we use it - **Account linking:** when you are signed in and link X at [Linked accounts](https://blazium.games/settings/connections), we attach your X user ID to your account. - **Sign-in:** we look for the account your X user ID is linked to. If it is linked, you confirm your password and then an authenticator code or an emailed code. X does not provide an email, so a new sign-in asks you to choose a username, email, and password and confirm that inbox before the account is created and X is linked. - **No pre-filling:** we do not copy your X name, username, or avatar. You type the email yourself. That is the only use. We make one X API request per link or sign-in and none after that. ## Our commitments - We never store your X access token. It is used during sign-in or linking and then discarded. - We never post, like, repost, follow, or send direct messages on X for you. - We never read your posts, timeline, bookmarks, or direct messages. - We never use X data for advertising. - We never use X data to train AI or machine-learning models. - We never sell X data or share it with third parties, except the [subprocessors](./subprocessors.md) that host our service. - We only keep your X user ID and username, so the linked account can log in and the settings page can show which one is linked. - We will not ask for more scopes without updating this page first. ## Revoking access and deleting data - Unlink X at [Linked accounts](https://blazium.games/settings/connections). After that, X can no longer be used to log in to your account. - Revoke Blazium Games at any time under [X > Settings > Security and account access > Apps and sessions](https://x.com/settings/connected_apps). This does not unlink X here, so unlink it as well if you want to stop X sign-in. - To delete your account and the X link, email [privacy@blazium.games](mailto:privacy@blazium.games). We process deletion requests within 30 days. See the [Privacy Policy](https://blazium.games/privacy-policy#6-deleting-your-account) for what deletion covers. See also the [GitHub API disclosure](./github-api-disclosure.md), the [Discord API disclosure](./discord-api-disclosure.md), [Permissions & Scopes](./permissions.md), and the [Linked accounts and sign-in](../linked-accounts.md) guide. ## Contact Questions about this disclosure: [privacy@blazium.games](mailto:privacy@blazium.games). # docs/linked-accounts.md # Linked accounts and sign-in You can link GitHub, X, and Discord to your Blazium Games account and then use any of them to log in. Linking is managed at [Settings > Linked accounts](https://blazium.games/settings/connections). ## Before you start - Signing in with GitHub, X, or Discord does not open a session by itself. You finish with your Blazium Games password and a second step. - If that service is already linked, you enter your password. With an authenticator app set up, you enter its current code (a recovery code works once). Without one, we email a code immediately, and you can send another 30 seconds later. - If it is not linked, and GitHub or Discord gives a verified email that already belongs to an account, you enter that account's password. A match links the service, then you do the second step. A wrong password links nothing and creates nothing. - If it is not linked and there is no matching verified email, you choose a username, email, and password, confirm a code sent to that inbox, then set up an authenticator app or skip it and confirm another emailed code. The account and the link are created only after the inbox code matches. X does not provide an email, so that path always starts with the email you type. - Each GitHub, X, or Discord account can be linked to only one Blazium Games account. - Linking from Settings, while you are already signed in, only attaches the service. It does not create an account. ## Link an account 1. Log in to [blazium.games](https://blazium.games). 2. Open **Settings > Linked accounts** (also in the header menu as **Linked accounts**). 3. Click **Link** next to GitHub, X, or Discord. 4. Approve Blazium Games on the other service. 5. You return to Linked accounts with "*Name* account linked." The row now shows **Linked as @username** and the date. A provider marked **Not available** can't be linked. ## Log in with a linked account 1. On the [Log in](https://blazium.games/login) page, or in the header when you are logged out, click **GitHub**, **X**, or **Discord**. 2. Approve Blazium Games on the other service if it asks. 3. Enter your Blazium Games password. If the service is not linked yet and its verified email matches an account, that password links it. Otherwise you set a username, email, and password and confirm the code we email. 4. If an authenticator app is set up, enter its current code. If you skip setup, or none is recorded, enter the code we email. You can ask for another code 30 seconds after the last one. A browser that has verified an emailed code is remembered for 30 days for email-and-password sign-in when no authenticator app is set up. It does not skip the password, an authenticator code, or the second step of a GitHub, X, or Discord sign-in. Authenticator setup, recovery codes, and what happens after sign-in are in [Account security and sign-in](./account-security.md). A verified email from GitHub or Discord can be shown on the create form and is compared with existing accounts. It is not saved on its own, and we do not copy your name or avatar. X does not provide an email. ## Unlink an account 1. Open **Settings > Linked accounts**. 2. Click **Unlink** next to the account. Once unlinked, that account can no longer be used to log in. If your Blazium Games account has no password, you cannot unlink the last linked account. [Set a password](https://blazium.games/settings/password) or link another account first. ## Steam You can also link Steam at **Settings > Linked accounts**. Steam can't be used to log in to Blazium Games. Linking it lets games that use [Steam auth verification](./steam-auth.md) tell their servers which Blazium Games account you are. 1. Click **Link** next to Steam. 2. Sign in on Steam's page and confirm. 3. You return to Linked accounts with "Steam account linked." The row shows your Steam name. Steam sign-in uses OpenID, so Blazium Games gets your Steam ID and no access token. We may read your public Steam name. Click **Unlink** to remove it; games then no longer learn your Blazium Games account from Steam. See the [Steam API disclosure](./legal/steam-api-disclosure.md). ## Revoke access on the other service You can remove Blazium Games from the other service at any time: - **GitHub:** [Settings > Applications > Authorized OAuth Apps](https://github.com/settings/applications) - **X:** [Settings > Security and account access > Apps and sessions](https://x.com/settings/connected_apps) - **Discord:** **User Settings > Authorized Apps** Revoking there does not unlink the account here. Unlink it at [Linked accounts](https://blazium.games/settings/connections) as well if you want to stop it logging in. ## What we store For each linked account we keep its user ID and username, so it can log in and the settings page can show which one is linked. A verified email from GitHub or Discord is compared while you sign in and is not saved on its own. X does not provide an email. We never store access tokens, and we do not copy your name or avatar. The details for each service: - [GitHub API disclosure](./legal/github-api-disclosure.md) - [X API disclosure](./legal/x-api-disclosure.md) - [Discord API disclosure](./legal/discord-api-disclosure.md) - [Steam API disclosure](./legal/steam-api-disclosure.md) - [Permissions & Scopes](./legal/permissions.md) for the exact scopes we request Deleting your Blazium Games account unlinks all of them. See the [Privacy Policy](https://blazium.games/privacy-policy#6-deleting-your-account). ## Troubleshooting | Message | What it means | What to do | | --- | --- | --- | | Confirm your password, or choose a username, email, and password | The service is not linked yet. A verified GitHub or Discord email that matches an account asks for that password. Anything else, including X, asks you to finish a new account. | Enter the matching password, or complete the new account and the emailed code. | | This *Name* account is linked to another Blazium Games user | The account is already linked to a different Blazium Games account. | Log in to that other account and unlink it there, then try again. | | Set a password or link another account before unlinking *Name* | It is the only way to log in to an account with no password. | Set a password at [Settings > Password](https://blazium.games/settings/password), or link another account, then unlink. | | Missing or invalid OAuth state | The link or login took longer than 15 minutes, or the page was reused or opened in another browser. | Start again from the Link or login button. | | Could not verify the *Name* account | The other service did not confirm who you are. This is usually temporary on their side. | Try again later. If it keeps happening, email [support@blazium.games](mailto:support@blazium.games). | | Linking was cancelled, or Sign-in was cancelled | You declined on the other service's approval screen. Nothing was linked or signed in. | Click **Link** or the login button again. | | The provider did not return a code | The other service sent you back without finishing. | Start again from the Link or login button. | # docs/listings.md # Listings and search A public listing has to describe the game well enough for players and agents to find it and to know what they are installing. You fill in the taxonomy on the **Listing** tab of the edit page (or with the `update_game_taxonomy` MCP tool), and the listing check tells you what is still missing. Creating listings needs [developer mode](./developer-mode.md). Adult content and the generative AI disclosure follow the [content rules](./content-rules.md), and [SEO and indexing](./seo-and-indexing.md) covers what search engines see. ## Listing types Pick the type on the **Settings** tab of the edit page, or pass `asset_type` to `create_game` or `update_game`. | Type | What it is | Parent game | |---|---|---| | `game` | A game | None | | `application` | Standalone software, such as a launcher or music tool | Optional | | `tool` | A tool or utility for one game, such as a level editor or save manager | Required to go public | | `mod` | Changes a game's content | Required to go public | | `plugin` | Extends a game or engine without changing its content | Required to go public | | `game_asset` | Art, audio or other content for making games | None | | `dev_asset` | Code, shaders, plugins for engines and other development assets | None | | `rom` | A standalone title, published and shown with games | None | ## Visibility Every new project starts as a draft. Change it on the **Settings** tab, or pass `visibility` to `create_game` or `update_game`. | Visibility | Who can open the store page | |---|---| | `draft` | You and the project's admins who accepted their invite | | `owner` | Only you. Admins still see the project in their dashboard and can edit it | | `invisible` | Anyone with the link. It stays out of search, browse and the sitemap | | `public` | Everyone. It needs the [listing check](#listing-check) to pass | Draft and owner pages show a notice saying who can see them, ask search engines not to index them, and can't be bought. Everyone else gets "not found", the same answer as for a page that doesn't exist. ## Parent games, tools, mods and plugins Tools, mods and plugins name the game they are for; applications may. The parent is either a game, an application or a ROM on Blazium Games, or an external game with a name and an `https://` link. Set it on the **Settings** tab, or with `parent` on `create_game` and `update_game` (`{"game": "uid-or-vanity"}` or `{"external_name": "...", "external_url": "https://..."}`). A parent that isn't a game, an application or a ROM, the listing itself, an external parent without an https link, or another developer's listing that isn't public returns `4233`. Changing the type to one without a parent drops it. A game, application or ROM that still has a public child can't be deleted, removed with its owner's account, or changed into a tool, mod or plugin (`4233`). When the listing check hides that parent, its public children are hidden at the same time. The parent's store page shows public children in two rows, each item marked **From the developer** (the parent's owner or admins) or **Community**; the full lists split them into **From the developer** and **From the community**: - **Tools and utilities**: tools and applications. The full list is at `//tools`. - **Mods and plugins**: mods and plugins. The full list is at `//mods`. The child's page links back under **For**. `GET https://api.blazium.online/api/v1/public/games/{uid}/children?kind=mods` (or `tools`, or empty for both) lists children with `same_creator`, and the listing's `has_mods` and `has_tools` say whether there are any. The player MCP `list_game_addons` tool reads the same list. ### Mod settings Mods and plugins can add install details, shown on their store page under **Install**: an `install_path` relative to the game folder (for example `mods/my-mod`, no absolute paths or `..`), a `loader` slug such as `bepinex`, and markdown `instructions` up to 8000 characters. Fill them in on the **Mod settings** tab or with the `set_mod_settings` MCP tool. Invalid values return `4234`. ## Taxonomy | Field | Values | |---|---| | `genres` | Up to 3 of: action, adventure, arcade, card, casual, fighting, horror, idle, management, platformer, puzzle, racing, rhythm, roguelike, rpg, sandbox, shooter, simulation, sports, stealth, strategy, survival, tower-defense, visual-novel, educational, tool, utility, other | | `tags` | 3 to 20 free lowercase slugs up to 32 characters, for example `co-op` or `pixel-art`. Spaces and underscores become dashes | | `tone` | Optional. Up to 3 of: cozy, dark, funny, relaxing, tense, wholesome, weird, serious, chaotic. This is the vibe of the game, used by browse and search. It is not required to go public | | `inputs` | keyboard_mouse, gamepad, touch, vr, motion | | `content_warnings` | violence, gore, sexual, nudity, language, drugs, gambling, horror, flashing_lights | | `engines` | Up to 5 engine slugs, for example `blazium` or `godot` | | `session_bucket` | How long one sitting usually lasts: `15m`, `30m`, `1h`, `3h`, or `endless` | | `net` | `offline`, `local`, `online`, or `local_online` | | `players_min`, `players_max` | 1 when multiplayer is off. When multiplayer is on, each is 1 to 64 and the maximum is at least the minimum | | `authorship` | `human`, `human_agent`, or `agent_heavy`. See [Made with](#made-with) | | `authorship_credit` | Optional credit line, up to 120 characters | | `ai_uses` | Parts made with generative AI: art, audio, code, text, voice, runtime. See [Generative AI disclosure](./content-rules.md#generative-ai-disclosure) | A value outside these lists returns `4071`. The tags field on the Listing tab suggests popular tags as you type. `GET https://api.blazium.online/api/v1/public/tags/popular?prefix=co&limit=20` returns the most used tags on public, non-adult listings (up to 50), with a count for each. ## Community tags Players who own a game and have played it for at least an hour can suggest up to 5 tags for it, from the store page or with the player MCP `suggest_tag` tool. A tag appears under **Players say** on the store page once 3 players suggest it, up to 10 tags, most suggested first. With no public tags, the page says "You can add tags to this." Tags you already set yourself aren't repeated. The item market is omitted until inventory is on and the game has an item definition. You can hide any suggested tag on the **Player tags** tab of the edit page or with the `hide_community_tag` MCP tool, and show it again later. Hiding keeps the votes. Search matches community tags along with your own. Playtime comes from the play-time heartbeat of the launcher and the game. It will move to playtime verified by the Blazium SDK once that ships. ## Made with The **Made with** field says who made the game, shown as a label on the store page and in search results: | Value | Label | |---|---| | `human` | Made by people | | `human_agent` | People with AI agents | | `agent_heavy` | Mostly AI agents | It is optional and never affects ranking. `authorship_credit` adds a short plain-text credit, for example "Art by Sam, code with Cursor". Players can filter search by it. ## Listing check Changing a page to `public` runs the listing check. If anything in the errors column is missing, the change is refused with HTTP 422, code `4225`, and the full report under `data.lint`. Warnings never block. | Check | Applies to | Level | |---|---|---| | At least 3 tags | all | error | | At least 1 genre, a session length, a player count, a network mode, and at least 1 input | games and ROMs | error | | At least 1 engine | mods, plugins, game assets, dev assets | error | | A parent game. On a public page the parent is public, and is a game, an application or a ROM | tools, mods, plugins | error | | A sexual or nudity content warning | adult pages | error | | At least 4 gallery images | all | error | | A cover image (1024x576 to 2048x1152, 16:9) and a thumbnail (960x540 to 1920x1080, 16:9) | all | error | | At least one build that passed the virus scan | all | error | | A tagline of at least 50 characters | all | error | | A description of at least 50 characters | all | error | | Similar titles | all | warning | Run it any time from the Listing tab, with `GET /api/v1/private/games/{uid}/lint`, or with the `validate_listing` tool. Pages that were already public on September 28, 2026 have a 30-day grace period. When it ends, a page that still fails the check is switched to `invisible` (reachable by link, left out of search). While a page is public, a save that would leave it failing the listing check is refused. That includes a taxonomy edit that fixes one field and clears another, deleting a gallery image that would leave fewer than 4, and deleting the last build that passed the virus scan. ## Similar titles List up to 10 public games, applications, or ROMs that players of yours would also like, most similar first. They show on your store page and feed recommendations. A title that isn't public, or your own game, returns `4072`. ## Other stores If the game is also sold elsewhere, link its pages there and the store page lists them under **Also on**. Add them on the **Links** tab of the edit page (**Other stores**), or with the `get_store_links` and `set_store_links` MCP tools. Saving replaces every link; leave a store empty to remove it. Each link must be an `https://` link on that store's own site, one per store: | Store | `platform` | Links on | |---|---|---| | Steam | `steam` | store.steampowered.com | | GOG | `gog` | gog.com | | Epic Games Store | `epic` | store.epicgames.com | | itch.io | `itch` | a game page on a creator subdomain, such as `you.itch.io/game` | | Humble Store | `humble` | humblebundle.com | | Microsoft Store | `microsoft` | xbox.com, apps.microsoft.com, or a microsoft.com store or product page | | PlayStation Store | `playstation` | store.playstation.com | | Nintendo eShop | `nintendo` | www or store on nintendo.com and Nintendo's regional sites | | App Store | `apple` | apps.apple.com | | Google Play | `google_play` | play.google.com | | Game Jolt | `gamejolt` | gamejolt.com | A link on another site, an `http://` link, a second link for the same store, or a link over 255 characters returns `4238`. Links are kept without the part after `#`. `GET /api/v1/private/games/{uid}/store-links` returns the links and every supported store with its allowed hosts; `PUT` the same path with `{"store_links": [{"platform": "steam", "url": "https://..."}]}` to replace them (an empty list clears them). Public listings return them as `store_links`, each with `platform`, `label`, and `url`. ## Dependencies, compatibility and license These are set over the developer MCP (`declare_dependency`, `declare_engine_compat`, `declare_license`; see the [reference](./mcp/reference.md#dependencies-compatibility-and-license)). - **Dependencies** link your listing to other public listings: it `uses` an asset pack or plugin, `supports` a game or tool (for mods and plugins), or was `made_with` a tool. Your page shows them under **Uses**, and the other listing shows yours under **Used by**. Up to 50 links. - **Engine compatibility** lists up to 10 engine version ranges, each with an optional renderer and platform. A `max_version` of `4.3` covers `4.3.x`. The store page shows them as **Works with**. - **License kind** is one of `cc0`, `cc-by`, `cc-by-sa`, `paid`, `source-available`, or `proprietary`, shown as **License**. ## Works with A mod that `supports` a game is checked against that game's current builds. The check compares the mod's engine compatibility ranges with each build's `engine_version` (set with `chauffeur build --engine-version` or `engine_version` in build.yml), per platform. | Status | Meaning | |---|---| | `compatible` | The build's engine version is inside one of the mod's ranges | | `incompatible` | The mod has ranges for this engine and platform, and none cover the build | | `unknown` | The build has no engine version, or the mod has no range for this engine or platform | A game's overall status is the worst across its platforms. The mod's store page shows it for each supported game's stable build, and `GET /api/v1/public/games/{uid}` returns it as `mod_compat`. The mod's developers can see the stable and beta builds per platform with the MCP `mod_compat` tool or `GET /api/v1/private/games/{uid}/mod-compat`. ## Bundle check Every uploaded build records a SHA-256 for each file inside its zip. The bundle check compares the files of 1 KB or more in one of your builds against the files of asset packs (game and dev assets) on the store, so you can confirm you have the right to ship what you bundled. It never blocks anything and players never see it. | Status | Meaning | |---|---| | `owned` | The pack is yours | | `licensed` | You bought a license for it, or it is `cc0` | | `attribution` | It is `cc-by` or `cc-by-sa`: credit the author | | `unlicensed` | No license on record. Buy one, or remove the files | Open **Symbols and bundle check** under a build on the Builds tab, or use the MCP `bundle_check` tool. Each match lists up to 5 of your file paths. ## Launch health Games that send the [standard events](./crash-reporting.md#standard-events) get a launch health band for each build, recomputed regularly from recent launches: | Band | Store label | Rule | |---|---|---| | `excellent` | Launches reliably | At least 98% of devices sent `boot_ok`, and at most 1% crashed before it | | `healthy` | Launches well | At least 93% `boot_ok`, at most 3% crash on boot | | `mixed` | Mixed launch reports | At least 80% `boot_ok`, at most 10% crash on boot | | `problematic` | Launch problems reported | Below mixed | | `unrated` | Not enough launch data | Not enough devices have launched it yet | The store page and search show the band of the newest stable build. The Builds tab shows every build's band and device count; the MCP `get_build_health` tool also returns the raw counts and median session length. ## Shelves The home page is built from shelves. Every shelf only takes public listings with a clean stable download (for the player's OS when one is given) from a verified owner, and never shows adult listings. Shelves without their own order change order daily. | Shelf | What qualifies | Order | |---|---|---| | `featured` (Featured) | Games and ROMs with a thumbnail and a newest stable build rated `excellent` or `healthy` | Daily | | `new` (New releases) | Games, applications, and ROMs published in the last 30 days | Newest first | | `recently_updated` (Recently updated) | Games, applications, and ROMs | Newest clean stable upload first | | `made_with_blazium` (Made with Blazium) | Games, applications, and ROMs that list the Blazium engine in [Made with](#made-with) | Daily | | `in_development` (In development) | Games and ROMs with the status `development` or `prototype` | Daily | | `browser_playable` (Play in your browser) | Games and ROMs with a clean stable `web` build | Daily | | `community` (From the community) | Games, applications, and ROMs with reviews in the last 90 days or [community tags](#community-tags) | Most reviews and tags first | | `tools_and_assets` (Tools, mods & assets) | Tools, mods, plugins, game assets and dev assets | Daily | | `tonight` (Something for tonight) | Games and ROMs with a 15-minute session length and a newest stable build rated `excellent` or `healthy` | Daily | | `unheard_of` (Unheard of) | Games, applications, and ROMs published in the last 60 days that pass the listing check and haven't been played on many devices yet. A listing shows for a limited time after its first `boot_ok` | Daily | `GET https://api.blazium.online/api/v1/public/shelves/{shelf}?os=windows&limit=12` returns a shelf without sign-in, and the player MCP `get_shelf` tool reads it. `limit` is 1 to 24 (default 12). An unknown shelf is a `404`, and a `limit` outside 1 to 24 is a `400`. Each listing on a shelf has its `uid`, `name`, `asset_type`, `status`, `tagline`, `vanity_name`, `thumbnail`, `price_cents`, `session_bucket`, `authorship`, launch `health`, the developer's `username` and `creator_avatar`, and two play fields: `has_browser_build` (a clean stable `web` build) and `has_downloads` (a clean stable build for any other platform). ## Build scans Every uploaded file is virus-scanned before it can be downloaded. The scan state shows on the store page next to each download, with the file's SHA-256 checksum, and on the Builds tab of the edit page. | State | Meaning | |---|---| | `clean` | Passed the scan and can be downloaded | | `scanning` | Waiting for or in the scan | | `infected` | The scanner found a threat; the file was removed | | `error` | The scan failed; the file was removed. Upload it again | The Builds tab also lists files removed in the last 30 days because their scan didn't pass, with the scanner's findings. Only clean files count as a platform in search, and agents can only install clean files. ## Search `GET https://api.blazium.online/api/v1/public/search` needs no sign-in. The [Browse](https://blazium.games/browse) page and the player MCP `search_catalog` tool use it. List filters take several values, comma-separated or with the parameter repeated. A listing matches a filter if it has any of its values, and it has to match every filter you give. The `exclude_` filters leave out listings that have any of their values, and win over the matching include. Unknown values are ignored. On [Browse](https://blazium.games/browse) each filter is a group of checkboxes: tick values to show only listings with any of them, or tick **hide** to leave them out. Content warnings only have **hide**. | Parameter | Notes | |---|---| | `q` (or `search`) | Free text across name, tagline, and description | | `asset_type` (or `type`) | List of `game`, `application`, `tool`, `mod`, `plugin`, `game_asset`, `dev_asset`, `rom` | | `genres`, `tags`, `tone` | Lists. `tags` also matches community tags | | `ai_uses` | List. Only listings that disclose generative AI for any of them | | `session_bucket`, `net`, `authorship` | Lists. `authorship` is `human`, `human_agent`, or `agent_heavy`; it filters only and never changes ranking | | `os` | List. Only games with a clean build for any of these platforms | | `exclude_types`, `exclude_genres`, `exclude_tone`, `exclude_tags` | Lists. `exclude_tags` also checks community tags | | `exclude_warnings` | List of content warnings | | `exclude_ai_uses` | List. Leaves out listings that disclose generative AI for any of them | | `players` | Only games that support this many players | | `arch` | With `os`, only builds for this architecture | | `engine` | Listings made with this engine (`engines`) or declaring compatibility with it | | `engine_version`, `renderer` | Only listings whose declared compatibility covers this version or renderer | | `license` | One license kind | | `sort` | `relevance` (default, best match): listings with launch problems last, then the best text and tag match, then newest. `newest` or `updated` sort by date. Any other value means `relevance` | | `page`, `page_size` | `page_size` is 1 to 50, default 20 | Each result also has `creator_avatar` and the same `has_browser_build` and `has_downloads` play fields as [shelves](#shelves). Adult listings are left out unless the signed-in player turned on adult content (see [Content rules](./content-rules.md#adult-content)). Each result has the listing fields, `engines`, `license_kind`, `authorship`, `adult`, `content_warnings`, `ai_uses`, `health` (the launch health band), `scan` (the best scan state across the game's files), `platforms` (clean builds only), `score`, and `matched_tags`. `GET /api/v1/public/games/{uid}` returns one listing with its taxonomy, made-with fields, `ai_uses`, `community_tags`, `adult`, `indexable`, `parent`, `has_mods` and `has_tools`, launch health, editions (`skus`), license kind, engine compatibility, dependencies (`relations.uses` and `relations.used_by`), `mod_compat` for mods, `mod_settings` for mods and plugins, `store_links` (see [Other stores](#other-stores)), files, scan states, checksums, similar titles, and newest changelog. `GET /api/v1/public/games/{uid}/relations` returns just the dependencies, license kind, and compatibility. # docs/mcp/access-and-keys.md # Access and keys ## Access scope Account access (an account key, or OAuth with **Account**) reaches every project you own or administer. Project access (your project key, or OAuth with one project) reaches only that project: - `list_games` and `blazium-games://games` return only that project. - Account-only tools return `403` with code `4030`: `get_profile`, `get_setup`, `list_mcp_keys`, `request_mcp_key`, `create_game`, `get_account`, `request_email_code`, `verify_email`, `set_timezone`, `get_approval`, `confirm_approval`, and the `blazium-games://me` resource. - Everything else for that project works: page details and updates, analytics, crashes, bug tickets, reviews, builds, channels, deploy info, key pools, and `request_deploy_key`. Calls for any other game return `4030`. - Approvals requested with a project token are approved from the owner's email, since the token can't call `get_approval` or `confirm_approval`. ## Read, write, and narrower scopes OAuth tokens carry `mcp:read` and `mcp:write`, or narrower scopes per area: `mcp:catalog.write`, `mcp:build.write`, `mcp:crash.read`, `mcp:crash.write`, `mcp:analytics.read`, `mcp:bugs.read`, `mcp:bugs.write`, `mcp:steam.manage`, `mcp:keys.manage`, `mcp:money`, and `mcp:anticheat`. The consent page offers presets for them (**Store page**, **CI**, **Crash triage**, **Bugs**, **Steam**, **Keys**, **Money**, **Anticheat**, **Read-only**, **Full access**); see [Scopes](./reference.md#scopes). **Full access** does not include `mcp:anticheat`. Anticheat tools need that scope on their own, and only after the game's NDA and contract are signed. See [Anticheat](../anticheat.md). - A token without any write scope (for example when you tick **Read-only access**) can only read. Any change returns `403` with code `4031` "This token is read-only". - A call outside the token's scopes, such as `update_game` with a **CI** token, returns `4073`. API keys and website sessions have every scope. ## Approvals Over MCP, rotating an account or deploy key, deleting a deploy key, creating more than 100 game keys at once, adding a project admin, promoting to `stable`, and deleting a game or build wait for the account owner, even with full access. The call returns an `approval` whose `confirm_url` the owner opens (they also get an email with the link and a 6-digit code). Once approved, the agent repeats the call with the same `idempotency_key`. See [Approvals for risky actions](./reference.md#approvals-for-risky-actions). ## Project keys and admins - There is no shared project key. Each owner and admin creates their own key for a project, so every action is traced to a person. - Creating a project key replaces only your own previous key for that project. Other admins' keys are never shown or affected. - Removing an admin from a project revokes their key for it. - The project owner can turn off MCP access for admins from the project's MCP tab. That immediately revokes the admins' keys for that project and blocks all of their MCP access to it: account keys, project keys, and OAuth. Admins keep normal website access, and the owner's own access is not affected. The switch can only be changed from the website. - Every MCP call is audit-logged with the user, the key or OAuth grant, and the project. ## Keys and rotation - Rotating on [blazium.games/settings/mcp](https://blazium.games/settings/mcp), or calling `request_mcp_key`, issues a new account key and revokes all previous account keys. Project keys are not affected. - MCP keys and player keys are shown once. Only their short codes are listed afterwards. - `get_deploy_info` lists the short code only. It does not include the access token or the secret. The short code is the start of the access token and is not enough to upload. - `request_deploy_key` replaces the previous key and returns both values once, after the project owner approves. The access token is `BLAZIUM_ACCESS_TOKEN`, sent as `X-Access-Token`. It can be copied later from the Deploy keys tab. The secret is `BLAZIUM_SECRET_KEY`, sent as `X-Secret-Key`. It cannot be shown again. Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. Before rotating, find every place the old key is used (MCP client configs, CI secrets) so you can update them right away. # docs/mcp/approvals.md # Approvals Some agent actions need your approval before they happen. ## How it works today When an agent asks for an action that needs your approval, the tool returns `approval_required` with an approval id and a confirm link, and we email you. You approve or decline from that email. The agent checks with `get_approval` and tries the call again once you approve. Actions that need your approval include: - purchases past your agent spending limit - donations and pledges - developer-server cash-outs and payout address changes - rotating or deleting deploy and MCP keys - promoting a build to stable - deleting a game or build - granting a large batch of keys - adding an admin - a few others See the [MCP reference](./reference.md) for each tool. Your agent spending limit (ask every time, unlimited, or a budget up to $1,000) is set on the website only. An agent can't change it. ## Planned: approval prompts in your AI client :::note Planned, not live These approval prompts are planned and not live yet. Details may change. ::: - **Every website action available to your agent.** We plan to let your agent do every step on blazium.games that you can do yourself, through the MCP servers. - **Prompts in your AI client.** When a step needs you, your AI client will ask you directly, using MCP [input-required tool results](https://modelcontextprotocol.io/specification/2026-07-28/server/tools#input-required-tool-results). You'll answer **Yes**, **No**, **Always yes**, or **Always no**. - **Standing choices.** Always yes and Always no are remembered for that agent and action. You'll be able to see, change, and remove them in your settings. - **Spend limit and email approval stay.** Past your spending limit, you'll still approve each purchase, even with Always yes. Clients that don't support prompts will keep using email approval. - **Always ask.** Cash-out, payout address changes, key changes (rotating or deleting deploy and MCP keys), adding an admin, and deleting a game ask every time, with no Always yes. A standing choice is for that agent key and lasts until you change or remove it. Spend limit and developer mode stay on the website. # docs/mcp/index.md # MCP for Blazium Games Blazium Games is a game publishing platform, with an infrastructure focus. The developer MCP server lets AI agents create and update pages for those projects, ship and promote builds, fill in press kits, link pages on other stores, read analytics, crash reports, reviews, bug tickets, and copyright notices, moderate game chat, manage game keys, set up payouts and cash out earnings, and issue deploy credentials. Version 1.23.0 has 217 developer tools and 100 player tools. A project can register sign-in applications with list_oauth_apps and the create, update, rotate, and delete tools. Buying, wallet, and library are only on the player server. A developer token that purchases or tops up gets `4034`. No token is required to connect. Call `initialize`, then `prompts/get` for `setup_account` or `sign_in`. The prompt list, tool list, and resource list are readable with no token. A call that needs an account names that prompt, or `elevate_session` when a key already exists. Do not set Authorization and do not call the server with Python. The developer server turns developer mode on when the human has agreed to the developer terms. The player server leaves the account a player. An existing player turns developer mode on later with `enable_developer_mode` on the developer server. Builds, images, and symbol files stay on the chauffeur CLI. MCP never uploads files. Signing in to the developer server and creating developer, project or deploy keys need [developer mode](../developer-mode.md) on your account; without it they return `4105`. The player server works for every account. | | | |---|---| | Protocol | MCP 2026-07-28, Streamable HTTP | | Endpoint | `https://mcp.blazium.games/developer` | | Auth | No token to connect. The connection is logged in only after sign-in succeeds, or after `elevate_session`. OAuth 2.1 with PKCE still works when the client opens the consent page | `https://mcp.blazium.games/mcp` still reaches this same server. Manage access at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). Want an agent to buy, top up, or download games for you as a player? Use the separate [player server](./player.md) at `https://mcp.blazium.games/player`. :::tip Using Cursor? Install the [Blazium Games Cursor plugin](../cursor-plugin.md). It adds this server plus skills that walk the agent through store pages, deploys, and crash debugging. ::: ## Sign up and sign in Call `initialize` with no token. `tools/list`, `prompts/list`, `prompts/get`, `resources/list`, and `resources/templates/list` are readable with no token. Then follow one prompt: - `setup_account` for a new person. Call `create_account`, then `confirm_account` with the email code. - `sign_in` for a person who already has an account. Call `login`, then `confirm_account` when the answer is `otp_required`. `create_account` shows Continue or Generate only when the call has no password. Generate shows a 20-character password. `login` never offers Generate. A password already on either call skips the form. The checkbox "Do not return this password. I will copy it." keeps it out of the agent result. Do not invent a password. When `create_account` or `set_timezone` has no timezone, the person gets Enter a timezone or Use this machine. A timezone already on the call skips that form. Use this machine is the only time the agent may send the machine's IANA zone. If the account still has none after sign-in, call `set_timezone` before `create_game`. Send `accept_legal` and `accept_developer_terms` only after the human agrees. On this server both turn developer mode on. An existing address gets the same answer and is not revealed. The connection becomes logged in only after sign-in succeeds. A wrong password, a code still required, or a rejected code leaves it logged out. `confirm_account` elevates once the code is accepted and returns this server's first `bgames_mcp_` key once. It does not return the website session. A later call does not rotate a key that already exists. A later connection calls `elevate_session`. Do not set Authorization and do not call the server with Python. An authenticator challenge, and choosing or skipping an authenticator, stay on the website. Website signup at [blazium.games/signup](https://blazium.games/signup) still works. OAuth consent, below, still works when the client opens the website. ## Option A: OAuth, no token (recommended) Add the server URL only. Your client discovers the authorization server, opens a Blazium Games sign-in and consent page, and completes PKCE on its own. - [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=blazium-games&config=eyJ1cmwiOiJodHRwczovL21jcC5ibGF6aXVtLmdhbWVzL21jcCJ9) - [Add to VS Code](vscode:mcp/install?%7B%22name%22%3A%22blazium-games%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.blazium.games%2Fmcp%22%7D) Cursor `mcp.json`: ```json { "mcpServers": { "blazium-games": { "url": "https://mcp.blazium.games/developer" } } } ``` Claude Code: ```bash claude mcp add --transport http blazium-games https://mcp.blazium.games/developer ``` On the consent screen you choose what the client may manage: - **Account**: every project you own or administer. - **A single project**: only that project. Account-level tools (profile, account, keys, setup, creating games, payments) return `403` with code `4030`. - **What it may do**: a preset such as **Store page**, **CI**, **Crash triage**, **Keys**, **Money**, **Read-only**, or **Full access**. See [Scopes](./reference.md#scopes). Read-only write calls return `403` with code `4031`. Access renews automatically for 30 days from when you approved it, then the client asks you to sign in again. Each renewal replaces the refresh token; if an old one is ever used again, the whole chain is revoked and the client has to ask you again. ## Option B: API key - **Account key**: create one at [blazium.games/settings/mcp](https://blazium.games/settings/mcp). It covers every project you own or administer. - **Your key for one project**: create one from the project's edit page, MCP tab. It only controls that project. Cursor `mcp.json` with a key: ```json { "mcpServers": { "blazium-games": { "url": "https://mcp.blazium.games/developer", "headers": { "Authorization": "Bearer bgames_mcp_YOUR_KEY" } } } } ``` A pasted client config may contain `Authorization: Bearer bgames_mcp_...`. The agent does not set that header. It calls `elevate_session` with the saved key. Do not call the server with Python. Never commit a key. Keep it in your client's config or a secret store. ## Next - [Access and keys](./access-and-keys.md): what account and project access can do, admins, and rotation - [OAuth and discovery](./oauth.md): OAuth details for client authors - [Reference](./reference.md): every tool, prompt, and resource - [Player MCP](./player.md): the player server, its scopes, and player keys - [Versioning](./versioning.md): what can change and how much notice you get - [Deploy builds](../deploy.md) and [Crash reporting](../crash-reporting.md) # docs/mcp/oauth.md # OAuth and discovery This page is for MCP client authors. If you use Cursor, VS Code, or Claude Code, the [Connect](./index.md) page is all you need. ## OAuth details - PKCE `S256` is required, and the `code_verifier` must be 43 to 128 unreserved characters (RFC 7636). `resource` is optional; when sent it must be `https://mcp.blazium.games/developer`, `https://mcp.blazium.games/mcp`, or `https://mcp.blazium.games` (or `https://mcp.blazium.games/player` for the player server) (RFC 8707). - Access tokens last one hour. The token response includes a refresh token, rotated on every use, so clients renew without asking you to sign in again. Rotation keeps the original 30-day expiry: after 30 days the user signs in again. - Each refresh token works once. Presenting a spent one revokes every token from that sign-in, so a stolen refresh token stops working as soon as either party uses it. - Authorization codes work once and expire after 10 minutes. - The consent page is protected against cross-site requests: Allow and Deny only work from the page itself. - Scopes: `mcp:read`, `mcp:write`, and the narrower `mcp:catalog.write`, `mcp:build.write`, `mcp:crash.read`, `mcp:crash.write`, `mcp:analytics.read`, `mcp:bugs.read`, `mcp:bugs.write`, `mcp:steam.manage`, `mcp:keys.manage`, `mcp:money`, and `mcp:anticheat` (see [Scopes](./reference.md#scopes)). `mcp:read mcp:write` is granted when the client asks for none, unless the user ticks **Read-only access** or picks a preset on the consent page. That default does not include `mcp:anticheat`. The **Anticheat** preset grants only `mcp:anticheat`. The player server uses `player:read`, `player:write`, and `player:buy`, and has no anticheat scope. - Authorization responses include `iss` (RFC 9207). Errors and Deny are sent back to the client as `error=...` (RFC 6749). - Dynamic Client Registration (RFC 7591) at `https://mcp.blazium.games/oauth/register` accepts https redirects, loopback `http://127.0.0.1` and `http://localhost` on any port, and app schemes such as `cursor://` and `vscode://` (RFC 8252). Public clients use `none`; confidential clients may use `client_secret_post` or `client_secret_basic`. - Client ID Metadata Documents (an https `client_id`) are supported; only the document's `redirect_uris` are accepted. - Loopback redirect URIs also work without registering a client. - Unauthenticated `/mcp` calls return `401` with `WWW-Authenticate` naming the resource metadata and scopes; a rejected token adds `error="invalid_token"`. ## Discovery Clients and agents can find the server without any configuration: - MCP server card: [`https://mcp.blazium.games/.well-known/mcp/server-card.json`](https://mcp.blazium.games/.well-known/mcp/server-card.json) (also `https://mcp.blazium.games/.well-known/mcp.json`, and redirected from `https://blazium.games/.well-known/mcp.json`). - Protected resource metadata (RFC 9728): `https://mcp.blazium.games/.well-known/oauth-protected-resource/mcp`. - Authorization server metadata (RFC 8414): `https://mcp.blazium.games/.well-known/oauth-authorization-server` (also `/.well-known/openid-configuration`). The path-suffixed forms `/.well-known/oauth-authorization-server/mcp` and `/player` also work; as RFC 8414 requires, they report the suffixed URL as `issuer` and set `authorization_response_iss_parameter_supported` to `false`. - Player server: `https://mcp.blazium.games/.well-known/mcp/player-server-card.json`, `https://mcp.blazium.games/.well-known/oauth-protected-resource/player`, and `https://mcp.blazium.games/.well-known/oauth-authorization-server/player`. - [llms.txt](https://blazium.games/llms.txt) lists the server for AI agents. The server card is generated from the running server, so it always matches the [reference](./reference.md). # docs/mcp/player.md # Player MCP The player server acts for you as a player. It can recommend games and say why, search the catalog, review games you own and report bugs, see your account, wallet, and library, top up your balance, buy games and donate within the spending limit you set, set up payouts and cash out your earnings, fetch download links, and hand installs and launches to the Blazium launcher. It cannot touch game pages, builds, crash reports, analytics, or keys; those are on the [developer server](./index.md). No token is required to connect. Call `initialize`, then `prompts/get` for `setup_account` or `sign_in`. The prompt list, tool list, and resource list are readable with no token. A call that needs an account names that prompt, or `elevate_session` when a key already exists. Do not set Authorization and do not call the server with Python. `accept_legal` is sent only after the person agrees. The account stays a player. Developer mode is turned on only when the account is created on the developer server, or later with `enable_developer_mode` there. Builds, images, and symbol files are uploaded with the chauffeur CLI, not from either MCP server. | | Developer server | Player server | |---|---|---| | URL | `https://mcp.blazium.games/developer` (`/mcp` still reaches it) | `https://mcp.blazium.games/player` | | Scopes | `mcp:read`, `mcp:write` | `player:read`, `player:write`, `player:buy` | | API key prefix | `bgames_mcp_` | `bgames_play_` | | Server card | `/.well-known/mcp/server-card.json` | `/.well-known/mcp/player-server-card.json` | A token belongs to exactly one server. A developer key or token is refused by `/player`, and a player key or token is refused by `/mcp`. A token can't hold both `mcp:*` and `player:*` scopes (`4032`). ## Sign up and sign in Call `initialize` with no token. `tools/list`, `prompts/list`, `prompts/get`, `resources/list`, and `resources/templates/list` are readable with no token. Then follow one prompt: - `setup_account` for a new person. Call `create_account`, then `confirm_account` with the email code. - `sign_in` for a person who already has an account. Call `login`, then `confirm_account` when the answer is `otp_required`. `create_account` shows Continue or Generate only when the call has no password. Generate shows a 20-character password. `login` never offers Generate. A password already on either call skips the form. The checkbox "Do not return this password. I will copy it." keeps it out of the agent result. When `create_account` or `set_timezone` has no timezone, the person gets Enter a timezone or Use this machine. Use this machine is the only time the agent may send the machine's IANA zone. Send `accept_legal` only after the person agrees. The account stays a player. An existing address gets the same answer and is not revealed. The connection becomes logged in only after sign-in succeeds. `confirm_account` returns this server's first `bgames_play_` key once and does not return the website session. A later call does not rotate a key that already exists. A later connection calls `elevate_session`. Do not set Authorization and do not call the server with Python. Developer mode is turned on only on the developer server. An authenticator challenge, and choosing or skipping an authenticator, stay on the website. Website signup at [blazium.games/signup](https://blazium.games/signup) still works. OAuth consent, below, still works when the client opens the website. ## Connect with OAuth (recommended) Add the server to your client with no token: ```json { "mcpServers": { "blazium-games-player": { "url": "https://mcp.blazium.games/player" } } } ``` Your client discovers OAuth from `https://mcp.blazium.games/.well-known/oauth-protected-resource/player` (authorization server metadata at `/.well-known/oauth-authorization-server/player`) and opens the Blazium Games consent page, which lists what the player tools can do. There is no project picker. Tick **Allow purchases** only if the agent should buy for you; without it the token has `player:read player:write` and every purchase call returns `4212`. Tick **Read-only access** to grant `player:read` only. ## Connect with a player key Create a player key at [blazium.games/settings/mcp](https://blazium.games/settings/mcp) under **Player MCP**. Untick **Allow purchases** to create a key without `player:buy`. The key is shown once. A pasted client config may contain `Authorization: Bearer bgames_play_...`. The agent does not set that header. It calls `elevate_session`. Rotating revokes all your player keys and leaves your developer keys alone. ## Scopes | Scope | Allows | |---|---| | `player:read` | Account, wallet, ledger, payment options, top-up status, quotes, purchase status, library, download links, approvals, agent policy, the files you can see for a game, recommendations, your review, friends and what they're playing, chat token status | | `player:write` | Email verification, play time, confirming an approval with the emailed code, joining or leaving a beta, reviews, tag suggestions, taste feedback, bug reports, friend requests, presence and activity sharing, chat sign-in and chat tokens | | `player:buy` | Card and x402 top-ups, `purchase_game`, `donate_to_game`, payout setup and `cash_out` | A route outside this list returns `4033`. A missing `player:buy` returns `4212`; any other missing scope returns `4031`. ## Spending limits and approval Purchases always come from your stored balance. Set a limit per agent at [blazium.games/settings/mcp](https://blazium.games/settings/mcp): ask every time, unlimited, monthly, yearly, or a one-time budget. Anything beyond the limit waits for you to approve it by email link or code. See [Agent purchases](../payments/agent-purchases.md). ## Payouts and cash-out With `player:buy` an agent can send you to Balance and ask to cash out. `start_payout_setup` and `get_payout_dashboard_link` return that page. You open Stripe from Set up payouts with Stripe, and identity, tax, and bank details are entered on Stripe only after that. A cash-out waits for you, including a player key. The fee is the account's rate from `get_wallet` (8%, 7%, or 6%, plus $0.25). Money only goes to the Express account on that same account, we email you after each agent cash-out, and payouts are processed on weekdays from 8:00am to 5:00pm Pacific. See [Agent payouts](../payments/wallet-and-cash-out.md#agent-payouts). ## Tools | Tool | Inputs | Scope | Notes | |------|--------|-------|-------| | `get_account` | none | read | Email verification, timezone, balances, what the account may do, and the website sign-in steps still open (`legal_acceptance_required`, `legal_changes`, `setup_required`, `authenticator`, `gate`) | | `create_account` | `email`, optional `password`, `username`, `timezone`, `accept_legal` | none | Creates an account. Continue or Generate only when password is omitted. Enter a timezone or Use this machine when timezone is omitted | | `login` | `email`, optional `password` | none | The person types the password. Generate is not offered. The connection is elevated only when sign-in succeeds. `otp_required` means call `confirm_account` | | `confirm_account` | `email`, `code` | none | Exchanges the email code, elevates this connection, and returns this server's first `bgames_play_` key once. A later call does not rotate an existing key | | `elevate_session` | `key` | none | Signs this connection in with a saved `bgames_play_` key. No Authorization header | | `request_email_code` | none | write | Emails a verification code to you | | `verify_email` | `code` | write | Verifies your email with the code | | `set_timezone` | `timezone` | write | Sets your IANA timezone, replacing the saved one. The agent uses your zone, not the machine it is running on | | `get_security_status` | none | read | Whether an authenticator app protects your account, and how many recovery codes are left | | `skip_authenticator` | none | write | Records that you chose not to set up an authenticator. An agent calls this only when you asked. Later sign-in uses `confirm_account` with the email code | | `get_wallet` | none | read | Credit, pending, and available balances, fee and refund rules, payout status, and recent cash-outs | | `list_wallet_transactions` | `limit` (1-200), `before` | read | Ledger entries, newest first | | `get_payment_options` | none | read | Card top-up and x402 USDC networks with fees | | `create_top_up_link` | `amount_cents` | buy | Card Checkout link for you to add balance | | `create_x402_top_up` | `amount_cents`, `network` | buy | x402 payment requirements for a USDC top-up | | `pay_with_x402` | `top_up_id`, `payment_payload` | buy | Submits the signed x402 payment | | `quote_purchase` | `uid`, `kind`, `amount_cents`, `sku` | read | Price, tax, and total. The agent shows you the total first. `sku` is an edition uid or slug from `get_game_details`; empty quotes the cheapest edition, and owners of a cheaper edition are quoted the upgrade price | | `purchase_game` | `uid`, `confirm_total_cents`, `idempotency_key`, `sku` | buy | Buys a license (or an edition upgrade) from your balance, with the same `sku` as the quote. Beyond the limit it returns `approval_required` | | `donate_to_game` | `uid`, `amount_cents`, `confirm_total_cents`, `idempotency_key` | buy | Donates to a free game from your balance | | `get_approval` | `approval_id` | read | `pending`, `approved`, `denied`, `expired`, or `used` | | `confirm_approval` | `approval_id`, `code` | write | Approves with the 6-digit code you read to the agent. accepted and already_approved mean retry once. already_completed means it finished. Do not request another code. | | `get_library` | none | read | Games you own, with refund windows and play time | | `get_download_link` | `file_id` | read | 5-minute signed URL for a Windows, Linux, or content-pack file. A web build is hosted and is not downloaded. | | `get_agent_policy` | none | read | This agent's limit mode, limit, and spend in the period | | `start_payout_setup` | none | buy | Returns the Balance page. You open Stripe from Set up payouts with Stripe | | `get_payout_dashboard_link` | none | buy | Returns the Balance page, where you open the Express dashboard | | `cash_out` | `amount_cents` | buy | Cashes out available earnings ($25 minimum) to your own Express account and waits for your approval; you're emailed after each one | | `get_patron_status` | `developer` (optional) | read | Your patron memberships. No card data | | `search_catalog` | `q`, `asset_type`, `genres`, `tags`, `tone`, `ai_uses`, `exclude_types`, `exclude_genres`, `exclude_tone`, `exclude_tags`, `exclude_warnings`, `exclude_ai_uses`, `session_bucket`, `net`, `players`, `os`, `arch`, `engine`, `engine_version`, `renderer`, `license`, `authorship`, `sort`, `page`, `page_size` | read | Public games, tools, mods, and assets with a score, scan state, platforms, made-with label, content warnings, AI disclosure, launch-health band, and a short reason for each match. Several values in one filter match any of them (comma-separate `asset_type`, `session_bucket`, `net`, `os`, and `authorship`); the `exclude_` filters leave out listings with any of their values. `sort` is `relevance` (default, best match), `newest`, or `updated`. Adult listings appear only if you turned on adult content. See [Listings and search](../listings.md#search) | | `list_articles` | `limit` (1-50, default 20), `query` | read | Newest published blog posts. `query` matches the title or description. Returns slug, title, description, date, and URL. Does not post or delete comments | | `get_article` | `slug` | read | One published blog post, including the markdown body | | `list_game_addons` | `uid`, `kind` (`mods`, `tools`, or empty for both), `limit` (1-100) | read | Mods and plugins, or tools and applications, made for a game. `same_creator` marks the ones from the game's own developer | | `suggest_tag` | `uid`, `tag`, `remove` | write | Suggests a tag for a game you own and have played for at least an hour (`4237` before that); `remove` withdraws it. Up to 5 per game. Without `tag` it returns your suggestions and whether you may suggest. See [Community tags](../listings.md#community-tags) | | `get_shelf` | `kind`, `os`, `limit` (1-24, default 12) | read | A home page shelf of listings with a clean download for `os`: `featured`, `new`, `recently_updated`, `made_with_blazium`, `in_development`, `browser_playable`, `community`, `tools_and_assets`, `tonight` (short sessions with a healthy build), or `unheard_of` (recent listings few people have found). Each listing says whether it plays in the browser (`has_browser_build`) or downloads (`has_downloads`). Shelves without their own order rotate daily. See [Shelves](../listings.md#shelves) | | `get_game_details` | `uid` | read | Description, taxonomy, price, editions (`skus`), made-with label, launch health, license kind, engine compatibility, what it uses and what uses it, files with scan state and checksum, similar titles, `store_links` to its pages on other stores, and whether you own it | | `install_build` | `uid`, `build_id`, `os`, `arch`, `channel` | read | Checks your license and the virus scan, then returns the file checksum, a 5-minute `download_url`, and a `blazium://install/` link for the launcher. Uses the channel you follow unless you pass `stable` or `beta`. Refuses any file that isn't `clean` | | `launch_game` | `uid` | read | Returns the `blazium://game/` link that opens the game in the launcher, and whether you own it and a clean build exists | | `set_channel` | `uid`, `channel` (`stable` or `beta`) | write | Joins or leaves a game's beta. Beta builds then show up in `get_game_details` and `install_build` | | `why_should_i_trust_this` | `uid` | read | The developer, how each current file was uploaded, its scan history and checksum, and anything worth a second look (a file that isn't clean, no scan history, a beta build). It never calls a file safe; a clean scan only means no known malware was found | | `recommend` | `intent`, `minutes`, `party_size`, `like_uid`, `os`, `arch`, `asset_type`, `include_owned`, `limit` (1-10) | read | Games for right now, each with the `reasons` it was picked and any `cautions`. See [Recommendations](#recommendations) | | `why_this` | `uid`, `intent`, `minutes`, `party_size`, `like_uid`, `os`, `arch` | read | One game scored against the same inputs: reasons, cautions, and the `blockers` that keep it out of `recommend` | | `write_review` | `uid`, `enjoyed`, `quality` (1-5), `would_play_with_friends`, `text`, `delete` | write | Creates or updates your review of a game you own. One review per game; `delete` removes it | | `taste_feedback` | `uid`, `more_like`, `clear` | write | More (`true`) or less (`false`) like this game in `recommend`. `clear` removes it | | `report_bug` | `uid`, `message`, `build_id`, `os`, `arch`, `include_dump`, `include_log` | write | Files a bug ticket with the developers. `include_dump` and `include_log` return one-time upload URLs (`PUT`, 24 hours) | | `games_friends_play` | `live_only` | read | What your friends are playing now, then what they played in the last 14 days, with store links. See [Friends](#friends) | | `list_friends` | none | read | Friends with their presence (playing, online, offline) and pending requests with their `request_uid` | | `remove_friend` | `username` | write | Removes a friend | | `get_presence` | none | read | What you are playing, and whether that is shared | | `set_presence_sharing` | `share` | write | Shows or hides what you are playing | | `get_inventory` | optional `cursor` | read | Items you hold. Page with `cursor` from the previous `next` | | `list_listings` | none | read | Your marketplace listings | | `create_listing` | `uid`, `price_cents`, and `item_ids` or `itemdef_id` with `count` | write | Lists items for sale | | `cancel_listing` | `listing_id` | write | Cancels one of your listings | | `send_friend_request` | `username` | write | Sends a friend request. If that person already asked you, it accepts theirs | | `respond_friend_request` | `request_uid`, `accept` | write | Accepts or declines an incoming request | | `get_chat_connection` | none | write | Chat host, TLS port 6697, the browser websocket, and a SASL PLAIN sign-in token that works for 10 minutes, so the agent can join chat itself. See [Chat](#chat) | | `get_chat_token_status` | none | read | Whether you have a chat token for IRC clients (prefix and created and last used times, never the token), whether your account is locked out of chat, and the settings for a client | | `request_chat_token` | `confirm` | write | Creates or replaces your IRC client chat token and returns it once. Replacing it disconnects every client signed in with the old one | | `revoke_chat_token` | `confirm` | write | Revokes your chat token and disconnects every client signed in with it | | `redeem_key` | `code` | write | Redeems a game key (`XXXXX-XXXXX-XXXXX-XXXXX`) or a gift link (the whole link or the code at its end) and adds the game to your library. If you already own it, the key stays unused (`4084`) | Games list the channels you can join in `get_game_details` (`channels`). A beta download link for a game whose beta you haven't joined returns `4074`. `install_build` and `launch_game` never install or run anything on the server or your machine; the agent gives you the `blazium://` link, or your client opens it, and BlaziumLauncher does the rest. `blazium://install/` and `blazium://game/` go to BlaziumLauncher on port 39220. `blazium://buy/` opens the store page and does not install. `blazium://hub` and `blazium://install?version=` stay with BlaziumHub. Chat links (`blazium://chat` and `blazium://friends`) open BlaziumLauncher too. Game chat itself is IRC on `irc.blazium.online` port 6697; see [Chat](#chat). ## Recommendations `recommend` gives the same answer for the same inputs; no model picks the games. It only considers public listings of one `asset_type` (`game` unless you pass another) with a clean build for your platform (when you pass `os`), leaves out adult listings unless you turned on adult content at [blazium.games/settings](https://blazium.games/settings#adult), and skips games you own or already liked unless you pass `include_owned`. Each game is scored in this order: 1. **Session fit**: its session length (`15m`, `1h`, `3h`, or endless) against the `minutes` you have. 2. **Friends**: a friend playing it right now, or else friends who own it. Only friends who share their activity count. 3. **Intent**: words from `intent` matched against the listing's genres, tags, tone, name, tagline, and description. When you give an intent, a game that matches none of its words is left out. 4. **Taste**: tags and genres shared with games you liked (`taste_feedback` more like, a review where you enjoyed it, an hour or more of play time, or `like_uid`), and titles the developer lists as similar to them. 5. **Reviews**: enough reviews, with most reviewers saying they enjoyed it. 6. **Crashes**: games with many recent crash reports rank lower and get a caution. 7. **Freshness**: a small, capped boost for recently updated listings. It never counts as a reason on its own. Every result lists `reasons`, each naming the listing field it matched. A game with nothing to cite is left out rather than padded in. `party_size` keeps only games that support that many players. Games you marked less like this never appear. `why_this` explains any one game, including why it was left out. ## Reviews and bug reports You can review and report bugs for games you own: games you bought, and free games you've downloaded (a free game counts once you download it, and stops counting if it later gets a price). You need a verified email, and developers can't review their own games (`4077`). Enjoyed and quality are separate: a well-made game you didn't enjoy can be quality 5 and enjoyed "no". Reviews appear on the store page, where the developer can reply. Review text is never used for ranking; `recommend` only counts whether reviewers enjoyed the game. A bug report goes to the game's developers, up to 10 per day (`4291`). Attached dumps and logs can only be downloaded by the game's developers and our staff. ## Friends Add friends by username from the agent or at [blazium.games/friends](https://blazium.games/friends). You need a verified email to send requests, and you can send up to 20 a day (`4292`). Sending a request to someone who already asked you makes you friends right away. Adding yourself returns `4228`, and asking someone you're already friends with or already asked returns `4078`. Friends see whether you're online and which game you're playing, plus a status of at most 40 characters beside the game name when the game sets one, and the public games you played in the last 14 days. "Playing" comes from the play-time heartbeat your launcher or game sends, and lasts 10 minutes after the last one. The player MCP has no tool that sets that status. Unlisted and draft games are never shown. Turn off **Activity sharing** on the friends page to hide all of it; you then also drop out of your friends' recommendations. ## Chat Game chat is IRC on `irc.blazium.online` and follows the [Chat Rules](https://blazium.games/chat-rules). `get_chat_connection` signs the agent in as you for 10 minutes. For your own IRC client, `request_chat_token` creates a long-lived token: it is returned once, so the agent should hand it straight to you, and only when you ask. Up to 10 token changes an hour (`4290`). A locked account can't sign in to chat with either token. See [IRC clients](../chat/irc-clients.md) for client setup and [For client developers](../chat/client-developers.md) for what an agent sees once it's connected. ## Interactive views A host that supports MCP Apps shows an interactive view beside the tool result. You confirm a purchase, donation, key redeem, or friend request in that view. A card top-up opens a Checkout link for you to pay. Payout setup and cash-out stay text-only tools. A host without MCP Apps keeps the text result. Each view is a `ui://` resource served as `text/html;profile=mcp-app`. ## Resources | URI | Contents | |-----|----------| | `blazium-games://me` | Account status, verification, and what the account may do | | `blazium-games://wallet` | Stored balance and payment rules | | `blazium-games://library` | Owned games and licenses | | `ui://blazium-games/checkout.html` | Quote, buy, and donate. The purchase runs when you click | | `ui://blazium-games/game.html` | Game information and trust checks | | `ui://blazium-games/results.html` | Search, recommendations, shelves, add-ons, and what friends are playing | | `ui://blazium-games/wallet.html` | Balance, ledger, spending limit, and a card top-up link | | `ui://blazium-games/approval.html` | Approval status, confirm link, and the emailed code | | `ui://blazium-games/library.html` | Owned games, redeem, and download links | | `ui://blazium-games/handoff.html` | `blazium://` hand-off for BlaziumLauncher | | `ui://blazium-games/account.html` | Verification, timezone, and links to finish sign-in on the website | | `ui://blazium-games/feedback.html` | Reviews, bug reports, taste, and tag suggestions | | `ui://blazium-games/friends.html` | Friends and requests | ## Moving from the developer server Buying, wallet, and library are only on this server. `get_library` is the library tool here. A developer token that purchases or tops up gets `4034`. ## Live server names - accept_invite - ack_patch_notices - buy_post - cancel_cash_out - cancel_membership - check_update - decline_invite - delete_article_comment - export_account - file_counter_notice - file_dmca_claim - get_asset_library_item - get_game_display_name - get_my_inventory - get_patch_notices - list_article_comments - list_asset_library - list_changelog - list_connections - list_market - list_my_bug_reports - list_spare_copies - list_standing_choices - open_account_finish - open_password_settings - pledge - redeem_spare_copy - report_cheater - report_game - report_player - request_refund - revoke_standing_choice - send_spare_copy - set_game_display_name - set_payout_currency - set_profile_visibility - set_standing_choice - sign_out - sign_out_everywhere - start_connection - start_email_change - unfriend - unlink_connection - write_article_comment # docs/mcp/reference.md # Reference This page covers the developer server at `https://mcp.blazium.games/developer`. `https://mcp.blazium.games/mcp` still reaches that server. The player server is on [Player MCP](./player.md). `uid` accepts a game uid or its vanity name. "Account only" means a project-bound token is refused with `4030`. "Write" means the token needs `mcp:write` or the narrower write scope for that tool's group (see [Scopes](#scopes)). Buying, wallet, and library are only on the [player server](./player.md). A developer token that purchases or tops up gets `4034`. ## Tools | Tool | Inputs | Notes | |------|--------|-------| | `get_profile` | none | Current user. Account only | | `list_games` | none | Games you own or administer, and pending admin invites | | `get_game` | `uid` | One game's settings | | `get_lobby` | `uid` | Lobby settings and published packs: enabled, relay or scripted, TURN, the active checksum, and pack history | | `set_lobby` | `uid` (required), `enabled`, `lobby_type` (`relay` or `scripted`), `ice_enabled` | Only the fields you pass change. Write | | `create_game` | `name` (required), `tagline`, `description`, `visibility`, `asset_type`, `vanity_name`, `adult`, `indexable`, `parent` | New store page. Tools, mods and plugins need a `parent` before they can go public. Needs [developer mode](../developer-mode.md) (`4105`). Account only, write | | `update_game` | `uid` (required), `name`, `tagline`, `description`, `visibility`, `asset_type`, `adult`, `indexable`, `parent` | Update a page; only the fields you pass change. Setting `public` fails with `4225` until the listing check passes. An empty `parent` object clears the parent. Write | | `get_game_analytics` | `uid`, optional `build` | Visitor analytics, the 30-day `downloads` block, and registered funnel events (count, unique devices, daily series). See [Download analytics](../download-analytics.md) and [Progress](../progress.md) | | `get_web_player` | `uid` | Browser player settings: enabled, full build, demo build, size, embed, Discord, Telegram, connect hosts, and share links | | `set_web_player` | `uid`, optional `enabled`, `full_build_id`, `demo_build_id`, `width`, `height`, `fullscreen`, `mobile`, `click_to_play`, `hide_branding`, `start_fullscreen`, `embed_enabled`, `embed_domains`, `embed_game`, `connect_domains`, `discord_enabled`, `application_id`, `public_key`, `telegram_enabled`, `telegram_bot_id`, `reddit_enabled`, `reddit_app_name`, `youtube_enabled`, `tiktok_enabled`, `tiktok_client_key`, `douyin_enabled`, `douyin_app_id`, `wechat_enabled`, `wechat_app_id`, `offer_build_id`, `for_sale`, `price_cents`, `is_demo`, `embed_supported`, `platforms`, `share_build_id`, `share_enabled` | Chooses the full build, an optional demo, the player size, launches, and one build's price or designation. Upload `designations`, `for_sale`, `price_cents`, `is_demo`, `embed_supported`, `web_pack`, and `export_targets` with the build file. Store shelves `steam`, `gog`, `epic`, and `itch` can be priced. A launch host or an embeddable build cannot. An embedded game cannot be sold. The price is not a separate checkout. Instagram is not a launch. Covered by `mcp:build.write` | | `set_host_fetch` | `uid`, `build_id`, `enabled`, optional `rotate` | Turns on, turns off, or rotates the file URL a host uses to download one web build. TikTok, Douyin, WeChat, YouTube, Reddit, Newgrounds, CrazyGames, Poki, Meta, and GameDistribution can have one. Discord, Telegram, Steam, GOG, Epic, and itch do not. The old address fails after it is turned off or rotated. The player server does not return this URL | | `get_achievements` | `uid` | Achievement definitions and their writers | | `set_achievements` | `uid`, `achievements` | Replaces the achievement list. Covered by `mcp:catalog.write` | | `get_stats` | `uid` | Integer stats, their op, and their writers | | `set_stats` | `uid`, `stats` | Replaces the stat list. Covered by `mcp:catalog.write` | | `get_funnels` | `uid` | Registered analytics events and their writers | | `set_funnels` | `uid`, `funnels` | Replaces the funnel list. Covered by `mcp:catalog.write` | | `get_presence_writers` | `uid` | Who may set the short presence status | | `set_presence_writers` | `uid`, `writers` | Replaces that list. Covered by `mcp:catalog.write` | | `list_server_keys` | `uid` | Game server key prefixes and roles. No secrets | | `request_server_key` | `uid`, `role` (`game_server` or `private_server`) | Returns the secret once | | `revoke_server_key` | `uid`, `key_id` | Revokes one game server key | | `list_items` | `uid`, optional `cursor` | One page of item definitions. `next` is the cursor for the following page. Covered by `mcp:read` | | `create_item` | `uid`, `itemdef_id`, `name`, optional platform type, stats, sockets | Creates a definition. `unique` is only set here. Covered by `mcp:catalog.write` | | `update_item` | `uid`, `itemdef_id`, `name` | Edits a definition. `unique` cannot change. Covered by `mcp:catalog.write` | | `give_items` | `uid`, `itemdef_id`, `quantity`, `request_id`, `recipients` | Gives one item to handles or emails. Covered by `mcp:catalog.write` | | `list_item_sets` | `uid`, optional `cursor` | One page of named sets. Bonuses are stored, not applied | | `upsert_item_set` | `uid`, `name`, optional `set_uid`, `pieces`, `bonus` | Covered by `mcp:catalog.write` | | `sync_item_schema` | `uid`, `mode` (`sync`, `overwrite`, or `addon`) | Updates Steam item definitions. Does not move player items. Covered by `mcp:steam.manage` | | `set_inventory_flags` | `uid`, `confirm`, optional `inventory`, `transfer` | Turns a switch on. Neither switch can be turned off. Covered by `mcp:steam.manage` | | `list_mint_keys` | `uid`, optional `cursor` | One page of names and prefixes. Covered by `mcp:keys.manage` | | `request_mint_key` | `uid`, `name` | Returns the 128-character secret once. It can mint, set stats, socket, unsocket, and use items. A player token cannot | | `rename_mint_key` | `uid`, `key_id`, `name` | Covered by `mcp:keys.manage` | | `revoke_mint_key` | `uid`, `key_id` | Covered by `mcp:keys.manage` | | `list_game_crashes` | `uid` | Recent crash reports | | `get_crash` | `uid`, `crash_id` | One crash report including stack excerpt | | `request_crash_download` | `uid`, `crash_id`, `kind` | Private download URL for `dump`, `log`, or `stack`, valid for 1 hour. Covered by `mcp:crash.read` | | `get_crash_reporter` | `uid` | Reads crash webhooks: enabled, webhook URLs, and that game's signing key. The key is not the bug reporter key. Covered by `mcp:crash.read` | | `set_crash_reporter` | `uid`, optional `enabled`, `webhooks`, `refresh_signing_key` | Turns crash webhooks on, replaces up to five https URLs, or refreshes the signing key. A refresh returns only the new key. Covered by `mcp:crash.write` | | `list_mcp_keys` | none | Account key prefixes only. Account only | | `get_setup` | none | Account, games, public URLs, latest `build_id`. No secrets. Account only | | `get_deploy_info` | `uid` | Upload, crash, and page URLs, and the build list. get_deploy_info lists the short code only. It does not include the access token or the secret | | `list_game_builds` | `uid` | Builds. `build_id` is the build UID for CI and crash reporters (`X-Build-Id`), not a version string | | `delete_game_build` | `uid`, `build_id`, optional `idempotency_key` | Deletes one build. The owner approves this. Write | | `add_game_admin` | `uid`, `invite`, optional `idempotency_key` | Invites an admin. Only the owner can invite, and the owner approves this. Write | | `remove_game_admin` | `uid`, `admin_id` | Removes an admin. Only the owner can remove one. Write | | `delete_game` | `uid`, optional `idempotency_key` | Deletes a game the caller owns. The owner approves this. Write | | `get_account_analytics` | none | Analytics across the signed-in account's games. Account only | | `get_game_build` | `uid`, `build_id` | One build, its files, and crash reporter headers | | `request_mcp_key` | `idempotency_key` (optional) | New account key. **Revokes all previous account keys.** Needs the human's approval. Account only, write | | `request_deploy_key` | `uid`, `idempotency_key` (optional) | Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. Returns both values once, after the project owner approves. The access token can be copied later from the Deploy keys tab. The secret cannot. Write | ### Releases and trust Every build file belongs to a channel: `stable` (the default), `beta`, `dev`, or your own lowercase name. Each channel points at one build. A clean upload moves beta, dev, and custom channels forward on its own. Stable waits until you call `promote_build`. `rollback_channel` moves a channel by hand. Players see the build each channel points at, plus anything uploaded after the last move. `dev` is only visible to the game's owner and admins, and `beta` only to players who joined the beta. | Tool | Inputs | Notes | |------|--------|-------| | `list_channels` | `uid` | Each channel's build, expiry, beta subscriber count, and the last 50 promote, rollback, and upload events | | `promote_build` | `uid`, `channel`, `build_id`, `expires_in_hours` (0-2160), `idempotency_key` | Points a channel at a build whose files passed the virus scan. `expires_in_hours` hides the channel from players after that. Promoting to `stable` needs the human's approval. Write | | `rollback_channel` | `uid`, `channel` | Moves the channel back to the build it pointed at before. Nothing is deleted. Write | | `list_crash_groups` | `uid` | Up to 100 crash groups, most recently seen first, with `first_seen`, `last_seen`, counts per build, and a `sample_crash_id` for `get_crash` | | `get_build_provenance` | `uid`, `file_uid` | Uploader, how it was uploaded (`deploy_key` with an 8-character `key_ref`, or `website`), upload time, checksum, and scan history. Never returns a secret | Crash groups use the top stack frames once a minidump has been stackwalked, and the crash message, app version, and OS before that. A new report can take a few minutes to join a group. ### Build health, symbols and bundle check MCP never uploads files. Symbols and builds are uploaded with the [chauffeur CLI](../cli/index.md) and the game's deploy key. Store images are uploaded with chauffeur or on the game's edit page on the website. These tools read and delete them. | Tool | Inputs | Notes | |------|--------|-------| | `get_build_health` | `uid` | The last 50 builds with `devices`, `boot_ok`, `crash_on_boot`, `median_session_seconds` and `band` over the last 30 days, plus the listing's public band and what each band means. See [Launch health](../listings.md#launch-health) | | `list_build_symbols` | `uid`, `build_id` | Breakpad symbol files for a build: `module_name`, `debug_id`, `os`, `arch`, `size`, `checksum`, and the `chauffeur symbols` command to upload more | | `delete_build_symbols` | `uid`, `build_id`, `symbol_uid` (optional) | Deletes one symbol file, or all of the build's symbol files when `symbol_uid` is empty. Write (`mcp:build.write`) | | `upload_symbols_info` | `uid`, `build_id` | The exact `chauffeur symbols` command for the build, its limits, and a link to [Symbols](../cli/symbols.md). Uploads nothing | | `bundle_check` | `uid`, `build_id` | Informational. Compares the files inside the build's zip with asset packs sold on the store and reports each match as `owned`, `licensed`, `attribution` (cc-by, credit needed) or `unlicensed`, with sample paths | | `mod_compat` | `uid` (a mod), `game` (optional) | Compares the mod's [engine compatibility](#dependencies-compatibility-and-license) with the engine version of each supported game's current builds, per channel and platform: `compatible`, `incompatible` or `unknown` | ### Editions A game can sell up to 8 editions. When it has any active edition, its listed price is the cheapest one and `set_game_price` can't change it (`4164`). Owners upgrade by paying the difference, at least 50 cents. See [Selling](../payments/selling.md#editions). | Tool | Inputs | Notes | |------|--------|-------| | `list_skus` | `uid` | Editions with `slug`, `name`, `kind`, `price_cents`, `active`, `sort_order` and, for bundles, `bundle_asset_uids` | | `upsert_sku` | `uid`, `sku_uid` (to replace), `slug`, `name`, `description`, `kind`, `price_cents` (99-50000), `bundle_asset_uids`, `active`, `sort_order` (0-100) | `kind` is `standard`, `deluxe`, `beta_access` (also grants the beta channel) or `bundle` (also grants 1 to 10 of your other listings). Without `sku_uid` it creates one. Write (`mcp:money`) | | `delete_sku` | `uid`, `sku_uid` | Retires an edition. Owners keep it; nobody can buy it any more. Write (`mcp:money`) | ### Player feedback Players review games they own and file bug tickets from the [player server](./player.md) or the store page. | Tool | Inputs | Notes | |------|--------|-------| | `list_reviews` | `uid`, `unreplied`, `page` | Reviews, newest first, with the summary: `count`, `enjoyed`, `quality_avg`, `quality_counts` (1 to 5), and `would_play_with_friends`. `unreplied` lists only reviews without a reply | | `get_review_reporter` | `uid` | Reads new-review webhooks: enabled, webhook URLs, and that game's signing key. The key is not the sale, crash, or bug reporter key. Covered by `mcp:read` | | `set_review_reporter` | `uid`, optional `enabled`, `webhooks`, `refresh_signing_key` | Turns new-review webhooks on, replaces up to five https URLs, or refreshes the signing key. A refresh returns only the new key. Covered by `mcp:catalog.write` | | `reply_to_review` | `uid`, `review_uid`, `text` | Public reply shown under the review on the store page (up to 2000 characters). Empty text removes it. Write | | `list_bug_tickets` | `uid`, `status` (`open`, `fixed`, `unidentified`, `closed`), `page` | 50 tickets a page, newest first, with counts by status. Follow `next_page` until it is absent. `has_screenshot` and `has_log` say which files exist. A dump or log also has a `crash_id` for `get_crash` and `request_crash_download` | | `get_bug_ticket` | `uid`, `bug_uid` | One ticket, including `has_screenshot` and `has_log` | | `request_bug_screenshot` | `uid`, `bug_uid` | A one-hour `url` for the screenshot. The tool returns the link, not the image | | `get_bug_log` | `uid`, `bug_uid`, `offset` | One page of the log, at most 16 KiB. Call again with `next_offset` until it is absent | | `update_bug_ticket` | `uid`, `bug_uid`, `status` (`open`, `fixed`, `unidentified`, or `closed`) | Sets status. Covered by `mcp:bugs.write`. Fixed and unidentified can show an in-game notice. Closed stays silent in the game. | | `get_bug_reporter` | `uid` | Reads the in-game reporter: enabled, daily cap, webhooks, and that game's signing key. Covered by `mcp:bugs.read` | | `set_bug_reporter` | `uid`, optional `enabled`, `daily_cap`, `webhooks`, `refresh_signing_key` | Turns the reporter on, sets the cap (1–10000), replaces up to five webhook URLs, or refreshes the signing key. A refresh returns only the new key. Covered by `mcp:bugs.write` | | `get_steam_auth` | `uid` | Reads whether Steam auth is on, the app id, and whether the Web API key and ticket secret are stored, plus who set each and when. Never returns those secrets. Covered by `mcp:steam.manage` | | `set_steam_auth` | `uid`, optional `enabled`, `confirm`, `app_id`, `web_api_key`, `ticket_secret` | Writes the app id and the two secrets, and turns auth on when all three are stored. `enabled: false` deletes both secrets only when `confirm` is true. Covered by `mcp:steam.manage` | | `unlink_steam` | `uid`, `confirm` | Unlinks the game from Steam. `confirm` only after the human agrees. Covered by `mcp:steam.manage` | | `rotate_steam_key` | `uid`, `confirm` | Replaces the Steam Web API key. The new key is returned once. `confirm` only after the human agrees. Covered by `mcp:steam.manage` | | `resync_steam` | `uid`, `confirm`, optional `groups`, `web_api_key` | Imports the chosen Steam groups again. `confirm` only after the human agrees. Covered by `mcp:steam.manage` | | `import_steam_game` | `app_id`, `web_api_key`, `confirm`, optional `groups`, `uid` | Imports a Steam store page into a new or existing listing. `confirm` only after the human agrees. Needs developer mode | | `set_anonymous_downloads` | `uid`, `enabled`, `confirm_no_license` | Turns the switch on or off. When on, signed-out visitors can download the files and play the full web build and the web demo, with no license. Turning it on needs `confirm_no_license` after the human agrees. Needs `mcp:write`. A missing confirm is `4109`. A paid game or an edition is `4113`. A price while it is on is `4114` | | `set_adult_content` | `show`, `confirm_18` | Shows or hides adult listings for this account. Turning them on needs `confirm_18` after the human confirms they are 18 or older | Only the game's owner and admins can read bug tickets and download their attachments. ### Copyright notices Paid copyright (DMCA) notices that name the account's content. Notices appear only once the claimant has paid. See [Copyright (DMCA) notices](../storefront/dmca.md#if-a-notice-names-your-content). | Tool | Inputs | Notes | |------|--------|-------| | `list_copyright_notices` | none | Notices about the account's content: `uid`, `reference`, `status` (`open`, `accepted`, `rejected`, `resolved`, `closed`), claimant, company, filing and decision dates, and how many of the account's links each names. `open` counts notices still under review | | `get_copyright_notice` | `uid` (from `list_copyright_notices`) | One notice: the claimant's name, company and email, the work described, the statements and signature, the account's links it names and whether those listings were disabled, staff messages, the decision, and `reply_to`. Read only; the human replies to staff by email at `reply_to` with the reference in the subject | ### Dependencies, compatibility and license These show on the store page as **Uses / Used by**, **License** and **Works with**, and players filter [`search_catalog`](./player.md) by them. | Tool | Inputs | Notes | |------|--------|-------| | `declare_dependency` | `uid`, `target_uid`, `kind` (`uses`, `supports`, or `made_with`), `remove` | Links your listing to another public listing: it uses that asset pack or plugin, it's a mod or plugin that supports that game or tool, or it was made with that tool. Up to 50 links. `remove` drops one. Write | | `list_dependents` | `uid` | What a public listing uses (`uses`) and which public listings declared a link to it (`used_by`), with its `license_kind` and `compat` | | `declare_engine_compat` | `uid`, `compat` (up to 10 of `engine`, `min_version`, `max_version`, `renderer`, `platform`) | Replaces the list; an empty list clears it. Either version may be empty to leave that end open, and a `max_version` of `4.3` covers `4.3.x`. Write | | `declare_license` | `uid`, `license_kind` | `cc0`, `cc-by`, `cc-by-sa`, `paid`, `source-available`, or `proprietary`; empty clears it. Write | ### Tools, mods and press A tool, mod or plugin names the game it is for with `parent` on `create_game` or `update_game`: `{"game": "uid-or-vanity"}` for a game or application on Blazium Games, or `{"external_name": "...", "external_url": "https://..."}` for one that isn't. The parent's store page lists it under **Tools and utilities** or **Mods and plugins**. See [Listings and search](../listings.md#parent-games-tools-mods-and-plugins). | Tool | Inputs | Notes | |------|--------|-------| | `set_mod_settings` | `uid`, `install_path`, `loader`, `instructions` | Mods and plugins only (`4234` otherwise). `install_path` is relative to the game folder (for example `mods/my-mod`), `loader` a lowercase slug such as `bepinex`, `instructions` markdown up to 8000 characters. Replaces all three. Write | | `get_press_kit` | `uid` | The press kit behind the listing's `/press` page and `press.zip` | | `set_press_kit` | `uid`, `release_date`, `website_url`, `press_email`, `trailer_url`, `history`, `features`, `awards`, `links`, `quotes`, `credits` | Replaces the whole press kit; fields you leave out are cleared, so read it with `get_press_kit` first. Links must be https. Up to 20 features, awards, links and quotes, 50 credits. See [Press kit](../press-kit.md). Write | | `hide_community_tag` | `uid`, `tag`, `show` | Hides a player-suggested tag from the store page, or shows it again with `show`. Without `tag` it lists every suggestion with its vote count. See [Community tags](../listings.md#community-tags). Write | | `get_store_links` | `uid` | The listing's links to its pages on other stores, shown as **Also on**, and every supported store with its allowed hosts | | `set_store_links` | `uid`, `store_links` (`platform`, `url`) | Replaces every store link; stores you leave out are removed and an empty list clears them, so read them with `get_store_links` first. One per store: `steam`, `gog`, `epic`, `itch`, `humble`, `microsoft`, `playstation`, `nintendo`, `apple`, `google_play`, or `gamejolt`, each an https link on that store's own site (`4238` otherwise). See [Other stores](../listings.md#other-stores). Write | ### Game chat Each game has an IRC channel on `irc.blazium.online`. The owner and accepted admins moderate it. See [Chat for publishers](../chat/for-publishers.md). | Tool | Inputs | Notes | |------|--------|-------| | `get_game_chat` | `uid` | The channel name (`irc_channel`), whether guests may join (`chat_guests`), and who is banned or muted with when each mute ends | | `set_chat_guests` | `uid`, `guests` | Lets people without a license join the channel. Guests can read but can't talk until they own the game. Write | | `ban_chat_user` | `uid`, `username` | Bans a user from the channel until unbanned and removes them right away. The owner, admins, and `blazium` can't be banned. Write | | `unban_chat_user` | `uid`, `username` | Lifts a ban. Write | | `suspend_chat_user` | `uid`, `username`, `minutes` (1-43200) | Mutes a user for up to 30 days; they can still read. Write | | `unsuspend_chat_user` | `uid`, `username` | Lifts a mute. Write | ### Game keys Keys give a game to someone for free, for press, bundles, or giveaways. Each code works once and adds the game to the redeemer's library (a license with source `key`). Players redeem at [blazium.games/redeem](https://blazium.games/redeem) or with `redeem_key` on the player server. Pools can also be managed on the **Game keys** tab of the project page. | Tool | Inputs | Notes | |------|--------|-------| | `create_key_pool` | `uid`, `name`, `campaign` | A named pool, such as Press or a bundle. Up to 50 per game. Write | | `grant_keys` | `uid`, `pool`, `n` (1 to 5000), `campaign`, `idempotency_key` | Creates `n` codes. They come back once, as a `csv_url` that can be downloaded one time within an hour; the codes are stored hashed and can't be shown again. More than 100 at once needs the owner's approval (see below). Write | | `create_gift_link` | `uid`, `pool`, `note` | A single-use `https://blazium.games/redeem/...` link for one person, shown once. Write | | `list_key_pools` | `uid` | Pools with `size`, `redeemed`, `unredeemed`, and `gift_links` | ### Approvals for risky actions Over MCP, rotating an account or deploy key, deleting a deploy key, creating more than 100 game keys at once, adding a project admin, promoting to `stable`, and deleting a game or build wait for the account owner, even with full access. The call returns HTTP 202 with `approval_required: true`, code `4214`, `email_sent`, and an `approval` object whose `uid` you pass as `approval_id` and whose `confirm_url` the owner can open. The owner also gets an email with the link and a 6-digit code. Once `get_approval` says `approved` (or after `confirm_approval` with the code), repeat the call with the same `idempotency_key`; without one, the same agent repeating the same action reuses the pending approval. Each approval works once and expires if nobody decides. Project tokens can't use `get_approval` or `confirm_approval` (`4030`), so approve those from the email. On the website these actions don't need an approval. ### Scopes `mcp:read` and `mcp:write` cover every developer tool except anticheat. OAuth consent can grant narrower scopes instead: | Scope | Covers | |-------|--------| | `mcp:catalog.write` | Game pages, taxonomy, similar titles, lobby settings, achievements, stats, funnels, presence writers, dependencies, engine compatibility, license kind, media, review replies, new-review webhooks, mod settings, press kits, community tags | | `mcp:build.write` | Builds, channels, deploy info, scan status, symbols, bundle check | | `mcp:crash.read` | Crash reports, crash groups, crash analysis, and reading the crash webhook setting and signing key | | `mcp:crash.write` | Changing crash webhooks and refreshing the signing key. Also covers the crash read routes | | `mcp:bugs.read` | Listing bug tickets and reading the in-game bug reporter | | `mcp:bugs.write` | Updating bug tickets and changing the in-game bug reporter. Also covers the read routes | | `mcp:steam.manage` | Reading and changing Steam auth settings. The Web API key and ticket secret can be set and are never returned | | `mcp:analytics.read` | Visitor analytics and events | | `mcp:keys.manage` | Deploy keys, MCP keys, game server keys, MCP access for admins, and project admins | | `mcp:money` | Pricing, editions, sales, sale and refund webhooks, game keys and gift links, wallet, purchases, library, downloads | | `mcp:anticheat` | Anticheat for one game. Not included in `mcp:read`, `mcp:write`, or **Full access**. See [Anticheat](#anticheat). | Every developer token can read the profile, account, and game pages. A write scope also reads its own group; the crash and analytics scopes also cover their actions. A call outside the token's scopes returns `4073`, or `4031` if the token has no write scope at all. The consent page offers presets: **Store page** (`mcp:read mcp:catalog.write`), **CI** (`mcp:read mcp:build.write`), **Crash triage** (`mcp:crash.read mcp:crash.write mcp:analytics.read`), **Bugs** (`mcp:bugs.read mcp:bugs.write`), **Steam** (`mcp:steam.manage`), **Keys** (`mcp:read mcp:keys.manage`), **Money** (`mcp:read mcp:money`), **Anticheat** (`mcp:anticheat`), **Read-only** (`mcp:read`), and **Full access**. `mcp:write` covers the bug and Steam scopes. It does not cover anticheat. ### Anticheat These tools are on the developer server only. Each one needs `mcp:anticheat`. They do nothing for a game until staff have recorded a signed NDA and a signed contract, except `request_anticheat` and a status read. The player server does not have them. What each profile checks is described in [Anticheat](../anticheat.md), without the decision rules. | Tool | Inputs | Notes | |------|--------|-------| | `request_anticheat` | `uid`, contact email, `confirm` | Owner only. `confirm` must be true. Sends the request. A staff member writes to that email. | | `get_anticheat` | `uid` | Before both signatures, the request status only. After that, the profile and its settings. | | `update_anticheat` | `uid`, `profile` (`generic`, `platformer`, or `fps`), and the settings for that profile | A setting from the other profile is rejected. Shutting admins out is owner-only. | | `list_anticheat_keys` | `uid` | Names and prefixes. Never the secret. | | `create_anticheat_key` | `uid`, name, `confirm` | `confirm` must be true. The secret is returned once, for the dedicated server. | | `rotate_anticheat_key` | `uid`, key id, `confirm` | `confirm` must be true. The new secret is returned once. | | `revoke_anticheat_key` | `uid`, key id, `confirm` | `confirm` must be true. | | `list_anticheat_events` | `uid`, optional origin | Reports for that game. Origin is the client or a server key's name. | | `list_anticheat_bans`, `ban_anticheat_player`, `unban_anticheat_player` | `uid`, and a player on the ban and unban tools | | | `list_anticheat_mutes`, `mute_anticheat_player`, `unmute_anticheat_player` | `uid`, and a player on the mute tools | | | `list_anticheat_notes`, `add_anticheat_note` | `uid` | A note the game's developers keep | | `enqueue_anticheat_action` | `uid`, action, player id, `confirm` | `confirm` must be true. Asks the dedicated server to warn, mute, kick, or ban, or to take a screenshot. | | `list_anticheat_audit` | `uid` | Who changed settings, keys, or actions | ### Listings See [Listings and search](../listings.md) for the allowed values and the listing check. | Tool | Inputs | Notes | |------|--------|-------| | `validate_listing` | `uid` | Listing check: `ready`, `errors` (block going public), `warnings`, `passes`, plus the current taxonomy and allowed values | | `game_setup_walkthrough` | `uid` | Read-only. Ordered setup steps, the `validate_listing` checks that still fail, field limits, and `next_tool`. It does not change the game and does not return secrets | | `update_game_taxonomy` | `uid` (required), `genres`, `tags`, `tone`, `inputs`, `content_warnings`, `engines`, `session_bucket`, `net`, `players_min`, `players_max`, `authorship`, `authorship_credit`, `ai_uses` | Only the fields you pass change. `authorship` is the [made-with label](../listings.md#made-with) (`human`, `human_agent`, `agent_heavy`, or empty to clear) and `authorship_credit` an optional credit line up to 120 characters. `ai_uses` is the [generative AI disclosure](../content-rules.md#generative-ai-disclosure) (`art`, `audio`, `code`, `text`, `voice`, `runtime`; an empty list means none). Write | | `set_similar_games` | `uid`, `games` (up to 10 uids or vanity names) | Replaces the similar titles; an empty list clears them. Write | | `set_media` | `uid`, `kind` (`cover`, `thumbnail`, or `gallery`) | Returns the matching [`chauffeur media`](../cli/media.md) commands and the image limits (PNG, JPEG, GIF, or WebP, sniffed from the file). Wide images need width/height between 1.70 and 1.85. Thumbnail 1280x720 recommended, 960x540 to 1920x1080, 5 MB. Cover 1024x576 recommended, 1024x576 to 2048x1152, 8 MB. Screenshot 1920x1080 recommended, 1280x720 to 2048x1152, 10 MB. Avatar 256x256 to 512x512, square (0.95 to 1.05), 2 MB, on the account settings page. MCP never uploads images; use chauffeur or the website. Write | | `scan_status` | `uid` | Scan state and history of every build file, plus files removed in the last 30 days because their scan failed | | `list_oauth_apps` | `uid` | Sign-in applications, the plan, and whether another one can be created. Never returns a secret. One application is included on Free. Another one needs Premium at $29 a month on that project. Business includes that. `mcp:read` | | `create_oauth_app` | `uid`, `name`, `redirects`, `email` | Creates a sign-in application. The secret is shown once. Ask the human for the name, redirect URLs, and email choice. `mcp:write` | | `update_oauth_app` | `uid`, `app_id`, optional `name`, `redirects`, `email` | Changes the name, redirect URLs, or email flag. `mcp:write` | | `rotate_oauth_app_secret` | `uid`, `app_id` | Replaces the secret. The old one stops working. The new secret is shown once. `mcp:write` | | `delete_oauth_app` | `uid`, `app_id` | Deletes the application. Players can no longer sign in with it. `mcp:write` | ### Account and payments Amounts are integer US cents. See [Payments](../payments/index.md) for the rules behind these tools. Buying, wallet, and library are only on the [player server](./player.md), where the library tool is `get_library`. The developer server lists 213 tools. A developer token that purchases or tops up gets `4034`. Seller, payout, and patron tools stay here. | Tool | Inputs | Notes | |------|--------|-------| | `get_account` | none | Email verification, timezone, balances, what the account may do, and the website sign-in steps still open: `legal_acceptance_required` (with `legal_changes`), `setup_required`, `authenticator` (`on`, `skipped`, or `not_chosen`), and `gate` (empty when none). Send the human to blazium.games/account/finish for an open step. Authenticator setup and skipping it stay on the website. Account only | | `create_account` | `email`, optional `password`, `username`, `timezone`, `accept_legal`, `accept_developer_terms` | Creates an account. Continue or Generate only when password is omitted. Enter a timezone or Use this machine when timezone is omitted. Send `accept_legal` and `accept_developer_terms` only after the human agrees | | `login` | `email`, optional `password` | The person types the password. Generate is not offered. The connection is elevated only when sign-in succeeds. `otp_required` means call `confirm_account` | | `confirm_account` | `email`, `code` | Exchanges the email code, elevates this connection, and returns this server's first `bgames_mcp_` key once. A later call does not rotate an existing key | | `elevate_session` | `key` | Signs this connection in with a saved `bgames_mcp_` key. No Authorization header | | `enable_developer_mode` | `accept_terms` | Turns developer mode on. Send `accept_terms` only after the human agrees. Turning it off stays on the website. Account only, write | | `request_email_code` | none | Emails a verification code to the account owner. Account only, write | | `verify_email` | `code` | Verifies the email with the code the human received. Account only, write | | `set_timezone` | `timezone` | Replaces the saved timezone with the human's IANA name. Call it when `get_account` timezone is empty or the human asks to change it. Do not send the machine's timezone. Unknown names return `4085`. Account only, write | | `get_security_status` | none | Whether an authenticator app protects the account: `state` (`on`, `skipped`, or `not_chosen`), `enabled_at`, `skipped_at`, `recovery_codes_left`, and `email_code_alternative`. Enroll, replace, and turn-off stay on the website. Account only, read | | `skip_authenticator` | none | Records that the human chose not to set up an authenticator. Call it only when the human asked. Later sign-in uses `confirm_account` with the email code. Account only | | `set_game_price` | `uid`, `price_cents` (0 or 99-50000), `donations_enabled` | Owners and game admins. A new paid price, donations, a paid edition, or a paid patron tier is refused until the listing owner finishes payout setup. A price of 0 and turning donations off stay allowed. Write | | `list_game_sales` | `uid` | Sales, donations, refunds, and seller earnings | | `get_sale_reporter` | `uid` | Reads sale and refund webhooks: enabled, webhook URLs, and that game's signing key. The key is not the review, crash, or bug reporter key. Covered by `mcp:money` | | `set_sale_reporter` | `uid`, optional `enabled`, `webhooks`, `refresh_signing_key` | Turns sale and refund webhooks on, replaces up to five https URLs, or refreshes the signing key. A refresh returns only the new key. Covered by `mcp:money` | | `start_payout_setup` | none | Returns the Balance page at blazium.games/settings/wallet. The human opens Stripe-hosted onboarding from Set up payouts with Stripe. Identity, tax, and bank details are entered on Stripe only after that. Needs a verified email. US accounts only. Account only, money write | | `get_payout_dashboard_link` | none | Returns the same Balance page. The human opens the Express dashboard from there. Account only, money write | | `cash_out` | `amount_cents` (at least 2500) | Cashes out available earnings to the Express account on that same account. Every agent cash-out, including a player key, returns `approval_required` and waits for the owner (retry with the same `idempotency_key`). The owner is emailed after each one. The fee is the account's rate from `get_wallet` (8%, 7%, or 6%, plus $0.25). Payouts are processed on weekdays from 8:00am to 5:00pm Pacific. `4095` finish payout setup, `4021` not enough available earnings, `4057` below the minimum. Account only, money write | | `get_patron_status` | `developer` (optional) | Read-only memberships for the caller: tier, billing, status, period end, whether the 12 hour check is open, and license ids. No card data | | `list_patrons` | `page` (optional) | Developer only. Usernames, tiers, status, and since | | `get_patron` | `username` | Developer only. One patron's tier, status, and since | | `list_tiers` | none | Developer only. Tiers and proposed game links | | `create_tier` | `name`, `rank`, `price_cents`, `billing`, optional `unlock`, `until` | Developer only. Rank, billing, and unlock stay fixed after create | | `update_tier` | `uid`, optional `name`, `price_cents`, `active` | Developer only. A new price applies to new pledges. `active` hides or shows the tier | | `delete_tier` | `uid` | Developer only. Refused while a membership is pending or active | | `list_posts` | `page` (optional) | Developer only. Drafts and published posts, with `tier_uids` | | `create_post` | `title`, `body`, `status`, `visibility`, `tier_uids` | Developer only. `visibility` is `public` or `tiers` | | `update_post` | `uid` plus the create fields | Developer only | | `delete_post` | `uid` | Developer only. The public page then 404s | | `get_approval` | `approval_id` | State of a purchase approval: `pending`, `approved`, `denied`, `expired`, or `used`. Account only | | `confirm_approval` | `approval_id`, `code` | Approves with the 6-digit code the human read from their email. Account only, write | Payout setup and cash-out need `mcp:write` or `mcp:money` and an account-level token; project tokens can't use them. They stay on both servers. See [Agent payouts](../payments/wallet-and-cash-out.md#agent-payouts). ### Sales and review webhooks `get_sale_reporter` and `set_sale_reporter` use `mcp:money`. `get_review_reporter` is a catalog read, so `mcp:read` can read it, and `set_review_reporter` needs `mcp:catalog.write`. Each list stores up to five URLs and its own signing key. Refreshing one key does not change the others. A Discord webhook URL receives an embed and no file. Any other https URL receives JSON. `http` is allowed only for localhost. The `signature` is base64 HMAC-SHA1 of the JSON body before that field is added, using that list's key. Each URL is posted up to three times with the same signed body. A 2xx stops the retries. One URL failing does not skip the others, and a failed delivery does not fail the sale, refund, or review. The settings response includes `last_delivery` for each URL. A paid purchase or donation, after it commits. `purchase_uid` is the idempotency key. `kind` is `purchase` or `donation`. `buyer` is the username only. ```json {"event":"sale","game_uid":"gme_1","game_name":"Example","purchase_uid":"pur_1","kind":"purchase","price_cents":1000,"sale_fee_cents":105,"seller_net_cents":895,"currency":"usd","buyer":"ada","signature":""} ``` A full refund uses the same event name with `partial` false. A partial Stripe refund sets `partial` true and `refunded_cents` to the amount refunded so far. Top-up refunds are not sent. The staff name is not included. `reason` is omitted when empty. ```json {"event":"refund","game_uid":"gme_1","game_name":"Example","purchase_uid":"pur_1","kind":"purchase","partial":false,"refunded_cents":1000,"currency":"usd","buyer":"ada","reason":"changed mind","signature":""} ``` A new review only. An edit or a delete does not send. ```json {"event":"review","game_uid":"gme_1","game_name":"Example","review_uid":"rv_1","enjoyed":true,"quality":4,"would_play_with_friends":true,"text":"Worth it","buyer":"ada","signature":""} ``` Field values: - `visibility`: `draft` (you and admins), `owner` (only you), `invisible` (anyone with the link), or `public` - `asset_type`: `game`, `application`, `tool`, `mod`, `plugin`, `game_asset`, `dev_asset`, or `rom` - `adult`: marks 18+ content. See [Content rules](../content-rules.md#adult-content) - `indexable`: `false` keeps the store page out of search engines. See [SEO and indexing](../seo-and-indexing.md) ## Prompts | Prompt | Arguments | Purpose | |--------|-----------|---------| | `setup_account` | none | Create an account, confirm the email code, and save the first key. A later connection calls `elevate_session`. Do not set Authorization | | `sign_in` | none | Sign in with a typed password and, when a code is required, confirm it. The connection is logged in only after sign-in succeeds | | `draft_game_page` | `pitch` | Draft a name, tagline, and description from a short pitch | | `improve_game_copy` | `description` | Rewrite an existing description, keeping the facts | | `analytics_summary` | `uid` | Summarize recent visitors | | `bootstrap_game` | `pitch`, `uid` (optional) | Create or update the store page and rotate deploy keys so an agent can ship a build | | `setup_oauth_app` | `uid` | Call `list_oauth_apps`, then create one sign-in application. If the owner must approve, the action is not done and no secret was issued. The person opens `confirm_url`. Call `get_approval`, then retry with the same `idempotency_key` | | `review_oauth_apps` | `uid` | Report each sign-in application. Do not create, rotate, or delete on its own | ## Resources | URI | Contents | |-----|----------| | `blazium-games://me` | Authenticated user. Account only | | `blazium-games://games` | Games list | | `blazium-games://games/{uid}` | One game page | | `blazium-games://games/{uid}/analytics` | Visitor analytics | | `blazium-games://games/{uid}/crashes` | Crash reports | | `blazium-games://games/{uid}/deploy` | Non-secret deploy endpoints and the short code of each deploy key | | `blazium-games://games/{uid}/builds` | Builds and crash reporter `build_id` values | | `ui://blazium-games/account.html` | Account status, with links to finish sign-in on the website | | `ui://blazium-games/approval.html` | Approval status, confirm link, and the emailed code | | `ui://blazium-games/dev-game.html` | Store pages you can edit | | `ui://blazium-games/analytics.html` | Visitor analytics | | `ui://blazium-games/sales.html` | Sales, and a price form that saves when you click | | `ui://blazium-games/crashes.html` | Crash reports and a private download link | A host that supports MCP Apps renders these `ui://` resources (`text/html;profile=mcp-app`) beside the tool result. You confirm a price change in the sales view. Other hosts keep the text result. Key-issuing tools, payout setup, and cash-out stay text-only. Buying views are on the player server. Template `{uid}` values must be a uid or vanity name made of letters, digits, `-` and `_`. Anything else, including dots or slashes, returns an error instead of calling the API. ## Errors Tool errors return `API : `. Some low codes (`4040`, `4050`–`4056`, `4090`–`4093`) are reused by different routes, so read the message along with the code. | Code | Meaning | |------|---------| | `4010` | Not authenticated | | `4030` | Not allowed: the game isn't yours, or a project token called an account-level tool or another game | | `4031` | Token is read-only | | `4032` | Token mixes developer (`mcp:*`) and player (`player:*`) scopes | | `4033` | This route isn't available to this server's tokens (for example a player token on a developer route) | | `4006` | Build not found | | `4096` | The account email is not verified | | `4085` | `set_timezone` got a name that isn't an IANA timezone | | `4020` | Not enough balance; top up first | | `4221` | No billing address for tax; top up by card once or buy on the website | | `4023` | Buy the game before downloading it | | `4094` | The total changed since the quote; confirm again with the human | | `4099` | The file is still being scanned, or the build has no clean file to promote | | `4212` | This token can't make purchases (project token, or a player token without `player:buy`) | | `4214` | Waiting for the human's approval (HTTP 202, returned as a normal result) | | `4215` | The human denied the request | | `4216` | Wrong or expired approval code | | `4095` | The idempotency key belongs to a different purchase, or payout setup isn't finished (payout tools) | | `4097` | The approval was already used | | `4098` | The approval was already decided or expired | | `4083` | Website only (for example account settings, approval links, or key management). It does not apply to `set_anonymous_downloads` | | `4109` | Anonymous downloads were turned on without `confirm_no_license` | | `4113` | Anonymous downloads are only available on a free listing | | `4114` | A price or an edition was set while anonymous downloads are on | | `4071` | A taxonomy value isn't allowed; `validate_listing` lists the allowed values | | `4072` | A similar title isn't a public game, or is this game | | `4225` | The listing check failed, so the page can't go public (HTTP 422, report in `data.lint`) | | `4073` | The token's scopes don't cover this tool | | `4074` | The file isn't on a channel you can see (for example a beta build when you haven't joined the beta) | | `4075` | The channel has no earlier build to roll back to | | `4226` | Invalid channel name or `expires_in_hours` out of range (HTTP 422) | | `4034` | Buying and top-ups are only on the player server; a developer token gets this code | | `4076` | Reviews and bug reports need a copy of the game (bought, or downloaded if it's free) | | `4077` | You can't review your own game | | `4227` | Invalid review: `enjoyed` missing, `quality` outside 1 to 5, or text too long (HTTP 422) | | `4291` | Too many bug reports today (10 per player per day, HTTP 429) | | `4078` | Already friends, or the friend request was already sent (HTTP 409) | | `4228` | You can't send a friend request to yourself (HTTP 422) | | `4292` | Too many friend requests today (20 per day, HTTP 429) | | `4229` | Invalid dependency: unknown kind, a non-public target, a link to itself, or more than 50 links (HTTP 422) | | `4230` | Invalid engine compatibility: engine or renderer not a slug, a version without numbers, or `min_version` above `max_version` (HTTP 422) | | `4231` | Unknown license kind (HTTP 422) | | `4232` | Invalid key pool request: missing name, more than 50 pools, `n` outside 1 to 5000, or a pool over 100,000 keys (HTTP 422) | | `4233` | Invalid parent: not a game or application, the listing itself, a type that can't have a parent, or an external parent without a name and https link (HTTP 422) | | `4234` | Invalid mod settings: not a mod or plugin, an absolute or `..` install path, a loader that isn't a slug, or instructions too long (HTTP 422) | | `4235` | Invalid press kit: a link that isn't https, a bad email or date, or too many items (HTTP 422) | | `4236` | Invalid tag, or the player already suggested 5 tags for this game (HTTP 422) | | `4237` | Play the game for at least an hour before suggesting tags (HTTP 403, `play_seconds` and `needed_seconds` in `data`) | | `4238` | Invalid store link: an unknown store, a link that isn't https on that store's own site, or a second link for the same store (HTTP 422) | | `4104` | Adult listing: the viewer hasn't turned on adult content (HTTP 403; signed-out viewers get `4004`) | | `4105` | Developer mode is off on this account (HTTP 403) | | `4042` | That key or gift link isn't valid (HTTP 404) | | `4079` | That key was already redeemed (HTTP 409) | | `4084` | The player already has this game; the key stays unused (HTTP 409) | | `4103` | The key CSV was already downloaded or has expired (HTTP 410) | | `4034` | Also: only the project owner can add admins or remove other admins | | `4040` | Not found (game, build file, crash, crash group, bug ticket, review, approval, purchase, top-up, key, or user; the message says which) | | `4043` | Key pool or key export not found | | `4050` | `price_cents` must be 0 or between 99 and 50000 | | `4051` | Donations are only available on free games | | `4052` | Donation `amount_cents` must be between 100 and 50000 | | `4053` | `kind` must be `purchase` or `donation` | | `4054` | Only the balance can pay here; card payments go through the store page | | `4055` | `idempotency_key` is required (up to 100 characters) | | `4056` | Top-up amount out of range | | `4080` | The project owner turned off MCP access for admins | | `4081` | Agent spending limits and MCP access settings can only be changed on the website | | `4082` | Agents pay from the balance, not by card; or only the owner can change MCP access for admins | | `4090` | Already done: you already own the game, or the crash has no dump, log, or stackwalk to download | | `4091` | You can't buy your own game | | `4092` | The game is free | | `4093` | The game doesn't accept donations | | `4100` | The top-up expired; create a new one | | `4130` | Too many crash metadata keys (64) or analytics events in one request (HTTP 413) | | `4290` | Too many requests, crash reports for the day, analysis requests, or redeem attempts (HTTP 429) | | `4155` | Invalid edition: slug, name, kind, price, bundle listings or order (HTTP 422) | | `4156` | The game already has 8 editions (HTTP 422) | | `4157` | The player already owns this edition or a higher one (HTTP 409) | | `4158` | A standard analytics event is missing a field or has one out of range (see [Crash reporting](../crash-reporting.md#standard-events)) | | `4164` | The price comes from the game's editions; change them with `upsert_sku` instead of `set_game_price` (HTTP 409) | | `4165` | This game sells beta access as an edition; buy it to join the beta (HTTP 402, editions in `data.skus`) | | `5030` | A download URL couldn't be signed; try again | | `5031` | Email codes aren't configured on the server | | `5032` | Payments, or a sign-in provider, aren't configured on the server | | `5033` | x402 top-ups aren't configured on the server | ## Live server names - accept_invite - ack_patch_notices - buy_post - cancel_cash_out - cancel_membership - check_update - decline_invite - delete_article_comment - delete_web_player_poster - export_account - file_counter_notice - file_dmca_claim - get_asset_library_item - get_game_display_name - get_my_inventory - get_patch_notices - get_sign_in_providers - list_article_comments - list_asset_library - list_changelog - list_connections - list_market - list_my_bug_reports - list_spare_copies - list_standing_choices - open_account_finish - open_password_settings - open_web_player_poster - redeem_spare_copy - report_cheater - report_game - report_player - request_refund - revoke_gift_link - revoke_key_code - revoke_key_pool - revoke_standing_choice - send_spare_copy - set_game_display_name - set_payout_currency - set_presence_sharing - set_profile_visibility - set_sign_in_providers - set_standing_choice - sign_out - sign_out_everywhere - start_connection - start_email_change - unfriend - unlink_connection - write_article_comment # docs/mcp/versioning.md # Versioning Both MCP servers report their version in `serverInfo.version` and on their server cards. The public API is under `/api/v1`. ## What can change without notice - New tools, prompts, resources, and API routes - New optional inputs - New fields in results and API responses - New error codes for new situations Write clients that ignore fields they don't know. ## What needs 30 days' notice - Removing or renaming a tool, resource, route, input, or result field - Making an optional input required - Changing what an existing field or error code means ## Recent additions Developer and player servers 1.23: - The live cards list 217 developer tools and 100 player tools. - `set_host_fetch` turns on, turns off, or rotates the file URL a host uses to download one web build. The player server does not return that URL. - `skip_authenticator` records that the human chose not to set up an authenticator. Call it only when the human asked. - `set_anonymous_downloads` turns the switch on after the human agrees (`confirm_no_license`). The switch covers file downloads, the full web build, and the web demo. `4083` no longer applies to this tool. It needs `mcp:write`. Developer server 1.22: - `list_oauth_apps`, `create_oauth_app`, `update_oauth_app`, `rotate_oauth_app_secret`, and `delete_oauth_app`. Prompts `setup_oauth_app` and `review_oauth_apps`. One sign-in application is included on Free. Another one needs Premium at $29 a month on that project. Business includes that. The player tool list was unchanged - `game_setup_walkthrough` adds an optional `player_sign_in` step. It does not change `ready` or `next_tool` Developer server 1.21: - `get_bug_ticket`, `request_bug_screenshot`, and `get_bug_log`. `list_bug_tickets` takes `page` and returns `next_page`. The screenshot tool returns a link. The log tool returns one page. The player tool list was unchanged. The developer server then listed 208 tools - `game_setup_walkthrough` is read-only. It returns the ordered setup steps, the `validate_listing` checks that still fail, the field limits, and `next_tool`. It does not change the game and does not return secrets Developer and player servers 1.20: - No token is required to connect. Call `initialize`, then `prompts/get` for `setup_account` or `sign_in`. The prompt list, tool list, and resource list are readable with no token. A call that needs an account names that prompt, or `elevate_session` when a key already exists. Do not set Authorization and do not call the server with Python. The connection becomes logged in only after sign-in succeeds. `confirm_account` returns that server's first key once and does not rotate a key that already exists. A later connection calls `elevate_session` - `enable_developer_mode` turns developer mode on for an existing account after the human agrees. Turning it off stays on the website - Developer tools: `delete_game_build`, `add_game_admin`, `remove_game_admin`, `delete_game`, `get_account_analytics`, `unlink_steam`, `rotate_steam_key`, `resync_steam`, `set_anonymous_downloads`, `import_steam_game`, and `set_adult_content`. Unlink, rotate, resync, anonymous downloads, Steam import, and adult content run only when the tool sends the human's confirm - Player tools: `get_inventory`, `list_listings`, `create_listing`, `cancel_listing`, `remove_friend`, `get_presence`, and `set_presence_sharing` - Builds, images, and symbol files stay on the chauffeur CLI. MCP never uploads files Developer and player servers 1.18: - Game chat on the player server: `get_chat_connection` (a 10-minute SASL PLAIN sign-in), `get_chat_token_status`, and `request_chat_token` and `revoke_chat_token` (both need `confirm`; the new token is returned once). See [Player tools](./player.md#chat) - Game chat moderation on the developer server: `get_game_chat`, `set_chat_guests`, `ban_chat_user`, `unban_chat_user`, `suspend_chat_user`, and `unsuspend_chat_user`. See [Game chat](./reference.md#game-chat) Developer server 1.17: - New read-only developer tools: `list_copyright_notices` and `get_copyright_notice`, for paid copyright (DMCA) notices that name the account's content. See [Copyright notices](./reference.md#copyright-notices) - The player server reports 1.17.0 too, with no tool changes Developer and player servers 1.16: - Interactive views (MCP Apps). Tools a person should see carry `_meta.ui.resourceUri` (and the older `_meta["ui/resourceUri"]`) pointing at a `ui://blazium-games/…` resource served as `text/html;profile=mcp-app`, and both servers advertise the `io.modelcontextprotocol/ui` extension. See [Player tools](./player.md#interactive-views) and the [reference](./reference.md) - A purchase, donation, key redeem, friend request, or price change runs only when the human clicks in the view. Key-issuing tools, x402 signing, payout setup, and cash-out stay text-only - The `checkout`, `wallet`, and `library` views are on the player server. Buying is only there - The servers no longer advertise the `logging` capability. No tools were added or removed Developer and player servers 1.15: - New tools on both servers: `start_payout_setup` and `get_payout_dashboard_link` (Stripe links for the human) and `cash_out` (`amount_cents`). Agents with `player:buy`, `mcp:write`, or `mcp:money` can set up payouts and cash out to the account's own Stripe payout account without approval; the owner is emailed after each agent cash-out. `4083` no longer applies to payouts - `get_wallet` now returns `payouts` (`connected`, `payouts_ready`), `cash_outs`, and `rules.payout_arrival` (up to 72 business hours) to agents - Donations are no longer refundable, and purchase results show `refundable_until` as null for donations Developer and player servers 1.14: - New developer tools: `get_store_links` and `set_store_links` for the listing's pages on other stores such as Steam, GOG, or Epic Games Store (`4238` for a link on the wrong site). `get_game_details` returns them as `store_links` - `search_catalog`: several values in one filter match any of them (comma-separate `asset_type`, `session_bucket`, `net`, `os`, and `authorship`), and `exclude_types`, `exclude_genres`, `exclude_tone`, `exclude_tags`, and `exclude_ai_uses` leave listings out. `sort` defaults to best match - `os` on `search_catalog` and `get_shelf` accepts `ios` - `get_shelf` takes eight more shelves (`featured`, `new`, `recently_updated`, `made_with_blazium`, `in_development`, `browser_playable`, `community`, `tools_and_assets`) and a `limit` (1-24). Shelf and search results add `has_browser_build` and `has_downloads` Developer and player servers 1.13: - New tools: `set_timezone` (sets the human's IANA timezone; `4085` for an unknown name) and `get_security_status` (authenticator on, skipped, or not chosen, and recovery codes left) - `get_account` returns `legal_acceptance_required`, `legal_changes`, `setup_required`, `authenticator`, and `gate`. Agents send the human to the website to finish those steps (see [Account security](../account-security.md#for-agents-mcp)) - `set_media` returns a structured `limits` object for the slot it was asked about (thumbnail, cover, or screenshots with `max_images`) - Signing in to approve an agent uses its own `__Host-BG_MCP` cookie on mcp.blazium.games, signed by the MCP server Developer server 1.12: - Tools, mods and plugins: `asset_type` gains `tool` and `plugin`; `create_game` and `update_game` accept `parent`, `adult` and `indexable`, and `update_game` accepts `asset_type` - `update_game_taxonomy` accepts `ai_uses` - New tools: `set_mod_settings`, `get_press_kit`, `set_press_kit`, and `hide_community_tag` - Signing in and creating developer, project or deploy keys need [developer mode](../developer-mode.md) on the account (`4105`) Player server 1.12: `suggest_tag`, `list_game_addons`, and `exclude_warnings` and `ai_uses` on `search_catalog`. Adult listings stay out of search and recommendations unless the player opted in. Developer server 1.11: - Editions: `list_skus`, `upsert_sku`, and `delete_sku`. `set_game_price` returns `4164` while a listing has editions - Builds: `get_build_health`, `list_build_symbols`, `delete_build_symbols`, `upload_symbols_info`, `bundle_check`, and `mod_compat` - `update_game_taxonomy` accepts `authorship` and `authorship_credit` - `set_media` returns the `chauffeur media` commands to upload local files (it no longer accepts `url`) Player server: `get_shelf`, `sku` on `quote_purchase` and `purchase_game`, and `authorship` on `search_catalog`. # docs/multiplayer.md # Multiplayer A Blazium game uses the engine module. A game built on another Godot engine vendors the public `games_plugin` addon and sets `blazium/game/game_uid` to the project id from the editor. Unity and Unreal games use the packages on [Engines](./engines.md). They call the native library instead of opening these sockets themselves. ## Sign-in The game opens a websocket to `wss://login.blazium.online/api/v1/connect` with protocols `blazium` and the project id. It sends `getid`, then `getlogin`, and receives the session token. GitHub, X, Discord, and Steam are the providers a game can turn on. ## Lobby and connections Turn lobbies on in the game editor. Choose Relay or Scripted. Relay seats players without a pack. Scripted runs a published Luau pack. A separate switch turns TURN and STUN on or off for that game. Create or join returns only after the player is admitted. The response includes `lobby_url`, `ice_enabled`, and, when TURN is on, `ice_session_id`. The module opens the lobby socket after that call succeeds. `lobby_seat` and SDK message 19 report `seated`, `lobby_loading`, or `lobby_failed`. The SDK does not open the socket. The `games_plugin` addon opens its own. The lobby socket is `wss://lobby.blazium.online/`. ICE servers come from `https://stun.blazium.online/v1/ice` using `ice_session_id` from that response. Relay uses `wss://turn.blazium.online/v1/signal`. When the TURN switch is off, the game does not request ICE. A presence notice on the lobby socket does not replace that ICE fetch. Achievements, stats, funnel events, and that notice are described in [Progress](./progress.md). Inside a Discord activity, the module and the Godot addon send API calls to `https://{applicationId}.discordsays.com/.proxy/blazium/api` and open `wss://{applicationId}.discordsays.com/.proxy/blazium/login/api/v1/connect` and `wss://{applicationId}.discordsays.com/.proxy/blazium/lobby/` instead of the public hosts. Turn lobbies on as Relay or Scripted, and leave the TURN switch off. Discord does not carry WebRTC. A Discord player still has to sign in and own the game or hold a license before the lobby socket accepts them. Unity and Unreal do not open these sockets. A Telegram Mini App uses `api.blazium.online`, `login.blazium.online`, and `lobby.blazium.online` directly. The same sign-in and license rule applies before the lobby socket accepts them. STUN and TURN are not offered. ## Scripted lobbies Turn scripted lobbies on in the game editor. Publish the Luau pack with the CLI: ```bash chauffeur lobby publish --dir . chauffeur lobby list chauffeur lobby status ``` Packs are Luau only. # docs/payments/agent-purchases.md # Agent purchases AI agents connected through the [MCP server](../mcp/index.md) can buy games and donate for you, but only from your stored balance. You choose how much each agent may spend on its own; anything else waits for your approval. ## Choose what an agent may spend 1. Verify your email. 2. Connect the agent. MCP API keys are listed automatically. An agent connected through OAuth sign-in appears after it calls `get_agent_policy` or tries to buy once. 3. Open [MCP settings](https://blazium.games/settings/mcp) on blazium.games and pick a mode under each agent: | Mode | What the agent can do on its own | | --- | --- | | **Ask me each time** (default) | Nothing. Every purchase and donation waits for your approval. | | **Unlimited** | Buy and donate with no limit. | | **Monthly limit** | Spend up to the amount per calendar month (UTC). | | **Yearly limit** | Spend up to the amount per calendar year (UTC). | | **One-time limit** | Spend up to the amount in total. Tick **Start over** to give it a fresh budget. | Limits go up to $1,000. They count each purchase's total, including tax; refunded purchases do not count. Each MCP API key and each OAuth client is a separate agent with its own mode. Only you can change these settings, on the website; agents can read them with `get_agent_policy`. Agents buy through the [player server](../mcp/player.md) at `https://mcp.blazium.games/player`, with a token that has `player:buy` (tick **Allow purchases** on the consent page or when creating a player key). Without it, purchase calls return `4212`. A developer token that purchases or tops up gets `4034`. Buying is only on the player server. ## How an agent buys 1. `quote_purchase` returns the price, tax, and total in cents. 2. The agent tells you the total. 3. `purchase_game` (or `donate_to_game`) with `confirm_total_cents` set to that total and a unique `idempotency_key`. If the purchase fits the agent's limit, it completes at once. If the total changed since the quote, it is refused with code `4094` and the agent has to quote again. Retrying with the same `idempotency_key` never charges twice. ## Approving a purchase When the agent is set to **Ask me each time**, or the purchase would go over its limit, the tool returns `approval_required` (code `4214`) instead of buying. You get an email with the amount, the game, a link, and a 6-digit code. Approve in either way: - open the link (or **MCP settings**, under **Waiting for your approval**) and click **Approve** or **Deny**; or - read the code to the agent, which sends it with `confirm_approval`. The agent can check the state with `get_approval`. Once approved, it calls `purchase_game` again with the same `idempotency_key` and total, and the purchase completes. Each approval covers that one purchase only and expires after 30 minutes. If it expires, the next retry sends a fresh email. ## Paying Agents always pay from the balance. If it is too low (`4020`), the agent can: - give you a card top-up link from `create_top_up_link`; or - top up with USDC from its own wallet over x402. See [Adding balance](./top-up.md). ## Codes agents may see | Code | Meaning | | --- | --- | | `4214` | Waiting for your approval (not an error; HTTP 202) | | `4215` | You denied the request | | `4216` | Wrong or expired approval code | | `4095` | The `idempotency_key` was already used for a different purchase | | `4097` | This approval was already used | | `4098` | This approval was already decided or expired | | `4096` | The account email is not verified | | `4212` | This token can't make purchases (no `player:buy`, a project token, or an unknown agent) | | `4030` | A project-bound developer token called an account-level tool | | `4034` | Buying moved to the player server; developer tokens can't buy after the cutoff | | `4090` | You already own the game | | `4091` | You can't buy your own game | | `4092` | The game is free; add it from the store page instead | | `4093` | The game doesn't accept donations | | `4020` | Not enough balance | | `4221` | No billing address on file for tax. Top up by card once, or buy on the website | | `4094` | The total changed; quote again | | `4082` | Agents cannot pay by card | ## What agents cannot do Agents cannot pay by card, change their own limits, approve their own requests except with the code you give them, or request refunds. An agent can send you to Balance. Every cash-out waits for you, including a player key. You're emailed after each cash-out. See [Agent payouts](./wallet-and-cash-out.md#agent-payouts). # docs/payments/buying.md # Buying games ## Buy a game On a paid game's store page, choose **Buy**: - **Pay by card:** you are sent to Stripe Checkout. The price, tax for your location, and a card processing fee are shown before you pay. After paying you come back to a page that confirms the purchase. - **Pay from balance:** the page shows a quote with the price, tax, and total. Confirm it and the total is taken from your balance at once, with no card fee. If the total changes before you confirm (for example, the price changed), you are asked to confirm again. Either way you get a license for the game, listed in your [Library](https://blazium.games/library). ## Donate Free games that accept donations show a **Donate** box. Pick an amount from $1.00 to $500.00 and pay by card or from your balance. Donations do not change your access to the game and are not refundable. ## Download Downloads need a verified email. Paid games also need a license. Download buttons on store pages and in your library give you a short-lived link (5 minutes) to the file. | What you see | What to do | | --- | --- | | Sent to log in | Log in, then press Download again | | Sent to verify your email | Enter the code sent to your account email | | Sent back to the store page to buy | Buy the game, then download | | "Still being scanned" | The file was just uploaded. Try again in a few minutes | ## Playtime Your library shows how long you have played each game, as reported by the Blazium Games app while a game runs. Playtime matters for refunds: a purchase stops being refundable after 2 hours of play. See [Refunds](./refunds.md). ## Purchase history Every purchase, from a card or the balance, is listed in your [wallet](https://blazium.games/settings/wallet) transactions. # docs/payments/index.md # Payments on Blazium Games Blazium Games accounts are free. Developers can sell games or accept donations, and players can buy with a card or from a balance stored on their account. All amounts are in US dollars. Payments are processed by [Stripe](https://stripe.com). Blazium Games is operated by Divine Games, Inc. ## Verify your email first A verified email address is required to: - make a game public or upload builds and images; - download any game, free or paid; - buy, donate, top up, or cash out; - let AI agents buy, set up payouts, or cash out for you. Verify at [blazium.games/settings/verify](https://blazium.games/settings/verify). A code is sent to your account email. Agents can start the same flow with the MCP tools `request_email_code` and `verify_email`, but the code always goes to your inbox. ## Fees at a glance | When | Who pays | Amount | | --- | --- | --- | | A game is sold or a donation is made | Developer (taken from the sale) | $0.25 + 8% of the price | | A buyer pays by card | Buyer | A card processing fee, shown before you pay | | A buyer pays from the balance | Buyer | Nothing extra | | Sales tax | Buyer | Calculated by Stripe Tax where Blazium Games is registered | | Adding balance by card | Buyer | The card processing fee; no tax | | Adding balance with USDC (x402) | Buyer | A 1.5% network fee | | Cashing out earnings | Developer | 8% + $0.25 on Free, 7% + $0.25 on Premium, or 6% + $0.25 on Business, from the best plan that account owns. USDC cash-outs also pay the network fee and do not use Stripe. Payouts are processed on weekdays from 8:00am to 5:00pm Pacific | A $10 game sold by card: the buyer pays $10, any tax, and the card fee. Blazium Games keeps $1.05 ($0.25 + $0.80), and the developer's pending earnings grow by $8.95. ## Guides - [Selling games](./selling.md): prices, donations, the sale fee, and the sales view. - [Buying games](./buying.md): the Buy button, paying from the balance, your library, and downloads. - [Adding balance](./top-up.md): card top-ups and USDC over x402. - [Wallet and cash-out](./wallet-and-cash-out.md): credit, pending and available earnings, Stripe Connect, the $25 minimum, payout timing, and agent payouts. - [Patron memberships](./patrons.md): tiers, posts, the 12 hour check, and why a membership cannot be refunded. - [Refunds](./refunds.md): the 7-day and 2-hour rule, non-refundable donations, and how to ask. - [Agent purchases](./agent-purchases.md): letting AI agents buy from your balance, with per-agent limits. The [Terms of Service](https://blazium.games/terms-of-service) are the binding version of these rules. # docs/payments/patrons.md # Patron memberships A developer can sell tiers on their public page. A higher tier includes every lower tier's games, locked posts, and patron-only sales. A page can have at most 12 tiers. Monthly tiers renew by card. One-time tiers are paid by card or from the wallet balance. The sale fee is the same as a game sale: $0.25 plus 8%. Tax and the card fee are added at checkout. The price you pay is copied onto the membership. A later price change applies only to new pledges. A membership payment is not refundable, including by staff. Cancel does not return the money. It stops the next renewal. Access that lasts only while you belong continues until the paid period ends. Access starts after a 12 hour payment check. Until that check finishes, the games are listed in your library as pending and are not playable. If the check fails, a first pledge is not granted. A missed later month removes only while-you-belong games. A permanent or lifetime game from a month that was paid stays. A card dispute is different: that charge was never paid, so every game that charge unlocked is removed, including a permanent one. Buying a higher tier charges that tier's full price. There is no credit for time left on the lower tier. The lower pledge ends when the new charge is confirmed. One game can be pooled onto one tier of another developer's page. The page developer has to accept the link before anyone is granted the game. Removing the link does not take away licenses already issued. See [Wallet and cash-out](./wallet-and-cash-out.md) for USDC payouts. # docs/payments/refunds.md # Refunds ## The rule A purchase can be refunded until **7 days** have passed or you have played for **2 hours**, whichever comes first. Your [library](https://blazium.games/library) shows each game's refund window and playtime. **Donations are not refundable.** A donation is a gift to the developer, not a purchase. The only exceptions are where the law requires a refund, or where we reverse a donation tied to fraud. ## How to ask Email [support@blazium.games](mailto:support@blazium.games) from your account email with the game name and, if you have it, the purchase ID from your wallet transactions. Refunds are not available through the site buttons or MCP. We may refund outside the window at our discretion, for example for a broken build. ## What you get back A refund is always credited to your account balance, never to a card: the price plus tax, minus the platform fee. The card processing fee and the platform fee are not returned. Nothing is sent to a card, a bank, or a USDC address. To get money out, request a payout. - **Paid by card or USDC:** credited to your account balance. - **Paid from balance:** credited to your account balance as credit, which cannot be cashed out. The license is revoked when the refund goes through, and the game can no longer be downloaded. A paid copyright-notice fee is not a purchase refund. Filing starts the review, so the work is performed when the fee is paid. Support does not refund that fee, whether the claim is accepted, rejected, resolved, closed, or withdrawn. ## What happens for the developer The sale's earnings are taken back from the developer's balance. The platform fee is not returned. ## Chargebacks Disputing a card payment with your bank revokes the license while the dispute is open. Please contact support first; it is usually faster. # docs/payments/selling.md # Selling games ## Set a price Open your game's edit page on blazium.games and go to the **Pricing** tab. Only the owner and accepted game admins can change pricing, and they need a verified email. - **Price:** $0 (free), or between $0.99 and $500.00. - **Donations:** free games can accept donations from $1.00 to $500.00. Paid games cannot. Agents can do the same with the MCP tool `set_game_price` (`price_cents`, `donations_enabled`). ## Editions A paid listing can sell up to 8 editions, added under **Editions** on the Pricing tab or with the MCP tools `upsert_sku` and `delete_sku`. | Kind | What the buyer gets | |---|---| | `standard` | The game | | `deluxe` | The game, as a higher tier you describe (soundtrack, art book, extra content you ship in the files) | | `beta_access` | The game plus the `beta` channel. Once a listing has an active `beta_access` edition, the beta channel is only for buyers of that edition | | `bundle` | The game plus 1 to 10 of your other listings, each granted as its own license | Each edition has a name (up to 80 characters), a slug (lowercase letters, digits and dashes, up to 40), a price from $0.99 to $500.00, an optional description, and a sort order. - **The listing price follows the editions.** It is always the cheapest active edition, donations are turned off, and `set_game_price` returns `4164` while editions exist. - **Upgrades.** A buyer who owns a cheaper edition pays the difference, at least $0.50. Editions can only be upgraded: a cheaper edition than the one owned returns `4157`, and the same edition is refused as already owned. - **Buying without naming an edition** buys the cheapest one. Agents pass `sku` (slug or uid) to `quote_purchase` and `purchase_game`. - **Retiring an edition** (delete, or untick **On sale**) removes it from the store. Buyers keep what they bought, and existing game keys for it still work. Editions share the same sale fee, refund rules, and earnings schedule as any other sale. `4155` means an edition field is invalid, and `4156` means the listing already has 8. ## What you receive Each sale or donation pays you the price minus the sale fee of **$0.25 + 8%**. The percentage is rounded up to the cent, and the fee never exceeds the price. | Price | Sale fee | You receive | | --- | --- | --- | | $0.99 | $0.33 | $0.66 | | $4.99 | $0.65 | $4.34 | | $10.00 | $1.05 | $8.95 | | $20.00 | $1.85 | $18.15 | Buyers pay tax and any card fee on top of the price, so those never come out of your share. ## When earnings become available New earnings are **pending**. They become **available** 7 days after the sale, when the refund window closes. The buyer's playtime does not release them sooner. See [Wallet and cash-out](./wallet-and-cash-out.md). If a purchase is refunded or charged back, its earnings are taken back from your balance. The platform fee is not returned. ## Taxes Blazium Games collects and remits sales tax on game purchases through Stripe Tax, in the places where it is registered. You receive the price minus the sale fee; tax is never part of your earnings. ## Track sales The **Sales** button on the edit page lists purchases, donations, refunds, and your net earnings for that game. Agents can read the same list with `list_game_sales`. ## Download access Buyers of a paid game need a license to download it. You, your game admins, and anyone you grant a license to (through support) can always download. Free games stay downloadable by any verified account. # docs/payments/top-up.md # Adding balance Your balance lets you buy games and donate without a card fee each time, and it is how AI agents pay. Top-ups are between $5 and $500 and go into your **credit**. Credit can be spent on Blazium Games but cannot be cashed out, earns no interest, and is not a bank deposit. See [Wallet and cash-out](./wallet-and-cash-out.md). ## By card On the [wallet page](https://blazium.games/settings/wallet), enter an amount and choose **Add balance**. Stripe Checkout adds the card processing fee; no tax is charged on top-ups. The credit shows up once Stripe confirms the payment, usually within seconds. An agent can create the same link with `create_top_up_link` and hand it to you. Agents cannot pay by card themselves. ## With USDC (x402) USDC top-ups use the [x402](https://x402.org) payment protocol, so an agent can pay from its own wallet without a browser. 1. `get_payment_options` lists the networks on offer (Base, and Solana when enabled) and the fee (1.5%). 2. `create_x402_top_up` with `amount_cents` (and optionally `network`) returns x402 payment requirements. The amount and recipient are fixed by Blazium Games. 3. The agent signs a payment for exactly those requirements with its wallet. 4. `pay_with_x402` with the `top_up_id` and the signed `payment_payload` submits it. The payment is verified and settled on chain through the Coinbase facilitator. 5. The credit is added once Stripe confirms the on-chain payment. Each top-up expires if it is not paid, and a signed payment can only be used once. ## Problems with a top-up If a payment went through but no credit appeared, contact [support@blazium.games](mailto:support@blazium.games) with the top-up ID from your wallet transactions. # docs/payments/wallet-and-cash-out.md # Wallet and cash-out Blazium is the marketplace. The buyer pays Blazium. Blazium keeps $0.25 + 8% of the price. The rest is the creator's earnings. A game sale, a donation, and a patron charge credit the creator's balance and can be cashed out. A Premium or Business subscription is charged to the subscriber and is not transferred to an Express account. A top-up becomes credit and cannot be cashed out. Your [Balance](https://blazium.games/settings/wallet) page shows three amounts: | Balance | Where it comes from | Spend it | Cash it out | | --- | --- | --- | --- | | **Credit** | Top-ups and refunds of balance purchases | Yes | No | | **Pending** | Your sales that can still be refunded | No | No | | **Available** | Sales past the refund window | Yes | Yes, from $25 | When you buy from your balance, credit is used first, then available earnings. Pending earnings become available 7 days after the sale. Playtime can end the buyer's right to a refund sooner, but it never releases earnings early. If a balance goes negative, for example because a top-up was refunded or disputed, the debt is repaid from your other balance first. Until then it is subtracted from what you can spend and cash out. The wallet page also lists every transaction: sales, purchases, top-ups, refunds, and cash-outs. ## Set up payouts A project cannot charge money until its owner has finished payout setup. A price of 0 stays allowed. An existing paid price stays in place and can still be bought. The owner cannot change it to another paid price, turn donations on, add a paid edition, or add a paid patron tier until transfers are active. Cash-outs are paid through [Stripe Connect](https://stripe.com/connect) Express. Stripe is available for United States accounts. USDC does not use Stripe. 1. The owner verifies their email. 2. On Balance, with USD or USDC selected, choose **Set up payouts with Stripe**. That creates the Express account if needed and opens Stripe-hosted onboarding in a new tab. Identity, tax, and bank details are entered there. Return and refresh land on Balance. 3. Until payouts are ready, Balance says to finish setup, or that Stripe is still reviewing after it has accepted the details and transfers are not active yet. **Continue payout setup** opens the hosted form again. 4. When transfers are active, Balance shows **Open Stripe payout dashboard** and **Cash out**. The Express dashboard is where the creator sees the payout to their bank. Blazium pays Stripe's processing fees and is responsible for a negative balance. An agent can send you to Balance. You open Stripe from that page. See [Agent payouts](#agent-payouts). ## Cash out A creator cashes out available earnings of $25 or more. The cash-out fee is 8% + $0.25, 7% + $0.25, or 6% + $0.25, from the best plan that account owns. The transfer goes only to the Express account on that same account. Payouts are processed on weekdays from 8:00am to 5:00pm Pacific. Stripe verification, tax-form holds, or a Stripe review can add time after a payout is sent. A refund or dispute stays on Blazium's balance. Stripe does not reverse a transfer that was already sent. ## USDC On Balance you can choose USD or USDC. **Set up payouts with Stripe** stays on the page for both. USD is paid through the Express account and is limited to United States accounts. USDC does not use Stripe. It uses the same email check, the same $25 minimum, and the same plan cash-out fee. You also pay a network estimate of $0.02, twice a typical Base or Solana transfer. Balance shows that estimate, and it is taken from the amount sent. The net is converted to USDC one-for-one and capped at 10,000 USDC per cash-out. A larger request is refused. USDC needs a Base address (`0x` and 40 hex characters) or a Solana address. A new address is checked before anything is sent. Changing the address starts that check over. The address cannot change while a cash-out is pending or while the check is still open. Payouts are processed on weekdays from 8:00am to 5:00pm Pacific. Each cash-out can send at most 10,000 USDC. The Free examples below use 8%. Premium is 7% + $0.25, and Business is 6% + $0.25. | You cash out (Free) | Fee | Fixed fee | Transferred (USD) | | --- | --- | --- | --- | | $25.00 | $2.00 | $0.25 | $22.75 | | $100.00 | $8.00 | $0.25 | $91.75 | If a transfer fails or is reversed, the cash-out amount and the fee return to your available balance. ## Agent payouts An agent can send you to Balance. Every agent cash-out waits for you, including a player key. - Wallet access means a player key or token with `player:buy`, or a developer token with `mcp:write` or `mcp:money`. Read-only and single-project tokens can't. - `start_payout_setup` and `get_payout_dashboard_link` return the Balance page. You open Stripe from **Set up payouts with Stripe**. Identity, tax, and bank details are entered on Stripe only after you open that page, never through the agent. - `cash_out` sends available earnings to the Express account on that same account. The same $25 minimum and the account's plan fee apply. The fee is the rate from `get_wallet`: 8%, 7%, or 6%, plus $0.25. Money can't be sent anywhere else. - We email you after every cash-out an agent makes, with the amount and the agent's name. - Your email must be verified first. To stop an agent, revoke its key or disconnect it in [MCP settings](https://blazium.games/settings/mcp). See [Permissions](../legal/permissions.md#agent-payouts). ## Chargebacks If a buyer disputes a card payment, the license is revoked and that sale's earnings are held back from your balance. If the dispute is won, they are restored. ## Partial refunds If support refunds part of a card payment, the buyer keeps the game and your earnings from that sale shrink in proportion. The Blazium Games fee shrinks the same way. # docs/plans.md # Free, Premium, and Business Each game or application has its own plan. A new game is Free. The public store page does not show the plan. Only the owner and an accepted admin can see it, on the project's Plan page. Either of them can start, upgrade, downgrade, or cancel it. The card is charged to the person who subscribes, monthly or annually, through Stripe. The marketplace fee is not added on top. Cash-out is 8% + $0.25 on Free, 7% + $0.25 on Premium, and 6% + $0.25 on Business. The wallet uses the best plan the account owns. The per-sale fee stays $0.25 + 8%. Blazium is the marketplace. The buyer pays Blazium. Blazium keeps $0.25 + 8% of the price. The rest is the creator's earnings. A Premium or Business subscription is charged to the subscriber and is not transferred to an Express account. A project cannot charge money until its owner has finished Stripe payout setup. A price of 0 stays allowed. | Plan | Price | History an owner or admin can read | |---|---|---| | Free | $0 | 45 days | | Premium | $29/month or $278.40/year | 360 days | | Business | $99/month or $950.40/year | 5 years | A year is 20% off twelve times the monthly price, so Premium is 27840 cents and Business is 95040 cents. Business includes everything Premium includes, and Premium includes everything Free includes. Premium adds lobby settings, achievement and stats settings, and more than one OAuth application. Business adds the anticheat settings for that game. Free and Premium do not include anticheat settings. This page does not sell anticheat and does not set a license price. The window covers analytics events, including funnel series and owner stats, crash report list and detail, and bug ticket list and detail. Funnel, achievement, and stat definitions stay. The bug intake caps stay. A Free game can still receive new crashes and bug reports. Developer tools that call these private routes see the same cutoff. Rows are kept until they are 5 years old, so a later upgrade can read them again. A daily job then deletes analytics events, crash reports, and bug tickets older than 5 years. A year is 20% off twelve times the monthly price. An upgrade, including monthly to annual, charges the new price immediately and does not credit unused time. A downgrade, annual to monthly, or a cancel to Free takes effect at the end of the period already paid. Until then the higher plan stays in force. A failed renewal is retried every 48 hours. The third failure emails the payer and the owner. Fifteen days after the original due time, the game becomes Free and the subscription is canceled. A successful retry before that clears the failure and keeps the paid plan. # docs/press-kit.md # Press kit Every public or invisible listing has a press page at `https://.blazium.games//press`, linked as **Press kit** from the store page. It shows the facts from your listing plus the press kit you fill in, and offers a zip download with the facts and your store images. ## Fill it in Open the **Press kit** tab of the edit page, or use the `get_press_kit` and `set_press_kit` MCP tools. Everything is optional. | Field | Notes | |---|---| | Release date | Free text up to 32 characters, for example `2026-11-14` or `Q1 2027` | | Press contact email | Shown on the press page | | Website, trailer link | `https://` links | | History | How the game came to be, markdown, up to 8000 characters | | Features, awards | Up to 20 each, one per line on the website, up to 200 characters each | | Links | Up to 20, as `Label | https://...` on the website | | Quotes | Up to 20, as `Quote | Source | https://...` on the website (the link is optional) | | Team | Up to 50 credits, as `Name | Role` on the website | Saving replaces the whole press kit. A link that isn't https, a bad email, or too many entries returns `4235`. ## What the press page shows Your listing's name, tagline, description, type, status, developer, platforms, cover, thumbnail and gallery, and its newest changelog entries, plus everything above. Placeholder images are left out. ## The zip `press.zip` holds `factsheet.json` (the same facts as the page) and an `images/` folder with the cover, thumbnail, and gallery. Images over 16 MB, or past 64 MB in total, are left out. It is rate limited to 10 downloads a minute per visitor. ## API - `GET https://api.blazium.online/api/v1/public/games/{uid}/press`: the factsheet as JSON. - `GET https://api.blazium.online/api/v1/public/games/{uid}/press.zip`: the zip. - `GET` and `PUT /api/v1/private/games/{uid}/press`: read and replace the press kit. Press pages follow the listing: a draft has no press page, an adult listing's press page needs the viewer's [adult opt-in](./content-rules.md#adult-content), and the page is indexed only when the listing is (see [SEO and indexing](./seo-and-indexing.md)). # docs/progress.md # Progress, funnels, and presence Each achievement, stat, and funnel event names the writers that may change it. A call is refused when the caller's role is not in that list. An empty writer list refuses every write. A new definition defaults to `client`. | Writer | Who it is | |---|---| | `client` | The logged-in player, through the SDK, the Godot plugin, or the engine host. Can only write that player. | | `game_server` | The studio's official dedicated server, using a game server key. May name any player who owns the game. | | `private_server` | A community server, using a key with that role. Same ownership check, and only definitions that list this role. | | `scripted_lobby` | The published Luau pack running on the lobby host, for a player seated in that lobby. | Removing `client` stops a modified client from granting the stat. The game server key is not the deploy key and not an anticheat key. The secret is returned once. `GET /api/v1/server/progress?user_uid=` uses the same key (`X-Server-Key` or `Bearer bgs_…`). The player must own the game. The body matches the player read: `achievements` (`slug`, `name`, `unlocked_at`) and `stats` (`slug`, `name`, `value`). A missing player and a player who does not own the game are refused the same way as a write. This read has its own limit, separate from the 120 writes a minute. The SDK method is `BlaziumAPI_ServerProgressRead(server_key, user_uid)`. The Godot plugin method is `server_progress(server_key, user_uid)`. ## Steam On the **Progress** tab of a game or application, **Pull from Steam** copies published achievement names and integer stats into these lists. Steam auth verification has to be on, with an app id and a stored Web API key. **Push to Steam** and **Two-way sync** stay unavailable, because Steam publishes achievement and stat definitions only on the Steamworks site. Float and average-rate stats are skipped. A definition that exists only here stays, and player unlocks and stat values are not removed. Funnels and presence are not on Steam's list. The same copy runs when **Achievements and integer stats** is ticked on a Steam import or resync. See [Import from Steam](./steam-import.md). ## Ownership `GET /api/v1/private/games/{id}/ownership` answers the signed-in session. - `owned` and `beta_access` match the license. - `owns_edition` is true when `?edition=` is a SKU slug or kind the player owns, or a lower edition in the existing upgrade order. - `?listing=` answers a second listing used as DLC. There is no separate DLC relation. The SDK method is `BlaziumUser()->Ownership(edition, listing)`. The Godot plugin method is `ownership(edition, listing_uid)`. ## Achievements and stats An achievement unlocks once. A stat is an integer with op `set`, `add`, or `max`. A game can have 100 achievements and 50 stats. The store page lists the definitions. The library shows that player's unlocks and stat values. A game reads the same rows with `GET /api/v1/private/player/progress?game_id=`. The Godot plugin method is `progress()`. The SDK method is `BlaziumAPI_Progress()`. Unity and Unreal call `Progress()` on the user binding. The answer has `achievements` (`slug`, `name`, `unlocked_at`) and `stats` (`slug`, `name`, `value`). ## Funnels `session_start`, `session_end`, `boot_ok`, `first_input`, `quit`, and `crash` stay on `POST /api/v1/public/events` with `X-App-Id` and `X-Build-Id`. `RecordStandardEvents` and `record_standard_events` send those six in one call. Any other name must be a registered funnel. Unknown names are refused. `get_game_analytics` adds an `events` block for registered events: count, unique devices, and a daily series. Pass `build` to limit that series. Visitor and download numbers stay as they are. ## Rich presence Friends see a status of at most 40 characters beside the game name, and the lobby id the lobby API already returns. It is hidden when activity sharing is off. `presence_writers` defaults to `client`. A single-player game sets its own status with `set_presence(status)` on the Godot plugin and `BlaziumAPI_SetPresence` on the SDK. Unity and Unreal call `SetPresence`. That call is allowed only when `presence_writers` includes `client`. It does not send a lobby signature. A scripted lobby does not write presence. `lobby:set_presence(user, status)` notifies that player's connection. The lobby host signs that notice. The launcher, the engine host, or the Godot plugin applies it only when the signature is present and `presence_writers` includes `scripted_lobby`. A client cannot claim the scripted lobby writer by itself. The Godot plugin also writes as an official server with `server_unlock_achievement`, `server_set_stat`, and `server_record_event`, and reads one owner with `server_progress(server_key, user_uid)`, using the same server key as the SDK. Those calls do not set presence. ## Scripted lobby The pack calls these on `lobby`. The host performs them. The user must be seated in that lobby. - `unlock_achievement(user, slug)` - `set_stat(user, slug, value)` - `record_event(user, name, fields)` - `analytics(name)` reads count, unique devices, and the daily totals for one event that lists `scripted_lobby`. An optional build filter uses the same shape. It does not return visitor or download analytics. - `set_presence(user, status)` only notifies that player. ## MCP and the progress file These developer tools replace a whole list. Set calls need `mcp:catalog.write`. `get_achievements`, `set_achievements`, `get_stats`, `set_stats`, `get_funnels`, `set_funnels`, `get_presence_writers`, `set_presence_writers`, `list_server_keys`, `request_server_key`, `revoke_server_key`. A deploy key can upload the same lists. A section that is present replaces that list. A section that is absent is left as it is. Server keys stay on MCP and the private API. ```bash chauffeur progress show chauffeur progress apply --file progress.yml ``` ```yaml spec: progress achievements: - slug: first_win name: First win writers: [client, game_server] stats: - slug: score name: Score op: max writers: [client] funnels: - name: level_complete writers: [client, scripted_lobby] presence_writers: [client, scripted_lobby] ``` # docs/project-oauth.md # Sign in with a project's application An OAuth application lets a project's players sign in, or create a Blazium account, and link it. The application has a client id and a secret. The player's platform sends both. This is not the MCP server at `mcp.blazium.games`, and it is not Steam auth. A token from this flow cannot call MCP or spend money. One application is included. Another one needs Premium at $29 a month on that project. Business includes that. After a downgrade, the first application stays usable. Extra applications stay listed and paused, and their authorize requests fail until the project is Premium or Business again. Create one on the project's **Sign-in** tab, or with `list_oauth_apps` and `create_oauth_app`. The secret is shown once. Copy it before you leave the page. It cannot be shown again. ## What the player agrees to share The person sees the project, the application, and the claims, then Allow or Deny. The browser returns to the application. - Always: the account's user id, the username when one is set, and the avatar URL when one is set. - Email only when the application has email turned on and the request includes the `email` scope. An unverified email is not released. The page says so. The player can revoke a link from **Settings > Linked apps**. Revoking deletes that application's tokens for that account. Blazium does not give the developer a list of every linked player's email. ## URLs | Step | URL | |---|---| | Authorize | `https://blazium.games/oauth/authorize` | | Token | `https://api.blazium.online/api/v1/oauth/token` | | User info | `https://api.blazium.online/api/v1/oauth/userinfo` | | Discovery | `https://blazium.games/.well-known/oauth-authorization-server` | `state` is required and echoed. PKCE `S256` is required, and the client secret is required. Redirect URLs are matched exactly: `https`, or `http://127.0.0.1` and `http://localhost` with a port. No wildcards. One to eight URLs, each up to 512 characters. The name the player sees is 1 to 64 characters. Codes work once and expire after 10 minutes. Access tokens expire after 1 hour. Refresh tokens rotate and keep a 30-day family. The token endpoint answers with `error` and `error_description`. `userinfo` accepts only an access token from this flow. The owner on a website session creates, changes, rotates, and deletes immediately. An agent create waits for the owner. The action is not done and no secret was issued. The person opens `confirm_url`. The agent calls `get_approval`, then retries the same tool with the same `idempotency_key`. An admin who is not the owner waits the same way. # docs/seo-and-indexing.md # SEO and indexing Search engines and AI crawlers may index a store page when all of these are true: - The listing is `public`. - It isn't marked [adult](./content-rules.md#adult-content). - **Let search engines and AI crawlers index this page** is ticked on the **Settings** tab (on by default), or `indexable` is `true` over the API or MCP. The Settings tab says whether the page can be indexed right now. Other pages still reach the listing through links; turning indexing off only asks crawlers to stay away. To hide a listing from people too, make it `invisible`, `draft` or `owner` (see [visibility](./listings.md#visibility)). ## What changes when a page isn't indexable - The store page, its press page, and its tools and mods pages send `` and an `X-Robots-Tag: noindex` header. - The listing is left out of every sitemap and llms.txt file. - The page has no structured data. ## Sitemaps and robots.txt | URL | Contents | |---|---| | `https://blazium.games/sitemap.xml` | The platform's public pages, including `/blog` and each published post, every developer profile with an indexable listing, and every indexable store page | | `https://.blazium.games/sitemap.xml` | Your profile, and your indexable store pages and their press pages | | `https://blazium.games/robots.txt` | Points to the root sitemap and keeps crawlers off signed-in routes. Public pages stay allowed | | `https://.blazium.games/robots.txt` | Points to your sitemap and the root sitemap, and keeps crawlers off embed pages (`//embed`) | Sitemaps list listings whose owner has a verified email and a finished account. The data behind them refreshes every ten minutes, and responses may be cached for up to an hour. `GET https://api.blazium.online/api/v1/public/sitemap` returns the same data as JSON. ## llms.txt [llms.txt](https://llmstxt.org) files give AI agents a plain-text summary: - `https://blazium.games/llms.txt` describes the platform, its APIs, the blog, and its MCP servers. It is a map for agents, not a search-ranking file. The blog is [https://blazium.games/blog](https://blazium.games/blog), the articles API is [https://api.blazium.online/api/v1/public/articles](https://api.blazium.online/api/v1/public/articles), and the feed is [https://cdn.blazium.online/articles/rss.xml](https://cdn.blazium.online/articles/rss.xml). The other files machines read are on [Discovery files](./discovery.md). - `https://.blazium.games/llms.txt` lists your indexable listings with a link to each one's summary. - `https://.blazium.games//llms.txt` summarizes one indexable listing: type, price, platforms, genres, tags and community tags, generative AI use, content warnings, parent game, and links to the store page, press kit, tools and mods pages, and the listing JSON. It returns 404 for a listing that can't be indexed. ## Structured data Indexable store pages include [JSON-LD](https://json-ld.org): a `VideoGame` for games, mods and plugins, or a `SoftwareApplication` for everything else, with the tagline, cover image, developer, genres, price, operating systems, player count (games, mods and plugins), tags and community tags as keywords, the review rating when there are reviews, and `isBasedOn` when the parent game is on Blazium Games. `/blog` is a `Blog`. Each post is a `BlogPosting` and links to its markdown file. Profiles also publish `ProfilePage` / `Person` structured data. Embed pages describe the project and stay out of the index. ## Share titles Each public page publishes an Open Graph and Twitter card: a title, a short description, and an https image. `twitter:card` defaults to `summary_large_image` and `og:type` defaults to `website`. | Page | Title | Description | |---|---|---| | Home | Blazium Games | Blazium Games is a game publishing platform, with an infrastructure focus. | | Browse | Browse Blazium Games | Find games, applications, mods, and assets to play. | | Desktop app | Blazium Games - Desktop App Download | Download BlaziumLauncher for Windows. It installs under the shared Blazium folder. | | Profile | `{display name} (@{username}) on Blazium Games` | Up to three project names, then "and N more". Two names use "A and B." None: `{display name} on Blazium Games.` Square card. | | Project | `{name} on Blazium Games` | The tagline, or one plain line of the description, or `{Type} by {username} on Blazium Games.` | | Press kit | `{name} press kit` | The tagline, or `Press kit for {name} by {developer}: facts, screenshots, logos and contacts.` | | Mods | `Mods and plugins for {name} on Blazium Games` | The count. One item is "1 mod or plugin". | | Tools | `Tools and utilities for {name} on Blazium Games` | The count. One item is "1 tool or utility". | | Embed | The same title and description as the project | `noindex` | `(@username)` is left off a profile title when the display name and the username are the same after trimming. Images are https only, at most 2048 characters, with no userinfo. A project page uses the cover, then the thumbnail. A profile uses the avatar. A URL whose path is `/favicon.ico` is skipped. Anything else uses `https://blazium.games/og-image.png`. Width and height are not set. A cover's alt text is `Cover art for {name}`; a thumbnail's is `Thumbnail for {name}`. # docs/steam-auth.md # Steam auth verification Steam auth verification lets a Steam build of your game sign players in through Blazium Games. The game sends a Steam session ticket, and Blazium Games checks it with Steam, confirms the player owns the game, and returns a signed session token. Your servers, or any third-party service you run, check that token with a signing key derived from the game's **auth key** and its game id. You don't need your own Steamworks Web API key on your servers, and players don't need a Blazium Games account. If a player has [linked Steam](./linked-accounts.md#steam) to their Blazium Games account, the token says which account that is. ## Turn it on The listing must be linked to its Steam app. Either: - tick **Enable Steam auth verification** when you [import from Steam](./steam-import.md) and supply a ticket secret, or - open the listing's **Steam** tab, enter the Steamworks Web API key and the ticket secret, and click **Turn on**. Auth stays off until three values are stored on the listing: | Value | Secret? | What it does | |---|---|---| | **App id** | No | The Steam app this listing is linked to. It stays when auth is turned off. | | **Web API key** | Yes, write-only | The publisher key Blazium Games uses to ask Steam about tickets and ownership. Sealed at rest. | | **Ticket secret** | Yes, write-only | The identity string your game passes to `GetAuthTicketForWebApi`. You choose it and put the same value in the game. Blazium Games does not generate it. | A save replaces a secret. No page, reveal, or MCP result returns the Web API key or the ticket secret, not even a prefix. The Steam tab shows whether each is stored, who set it, and when. After a save the secret fields are empty. Turning auth off asks you to confirm, then deletes both secrets and revokes Steam sessions. The app id stays. The session-signing **auth key** is separate: together with the game id it is the secret your servers use to check tokens, and **Show auth key** still reveals it to an owner on the website. Agents cannot reveal it. An agent with `mcp:steam.manage` (or `mcp:write`) can set the app id, the Web API key, and the ticket secret with `set_steam_auth`. `get_steam_auth` returns the app id and the audit fields only. `enabled: false` does nothing unless `confirm` is true. ## Sign a player in In the game, ask Steam for a Web API ticket with the ticket key as the identity, then send it to Blazium Games: ```cpp // Steamworks SDK SteamUser()->GetAuthTicketForWebApi("the-ticket-secret-from-your-listing"); // In the GetTicketForWebApiResponse_t callback, hex-encode m_rgubTicket. ``` ```http POST https://api.blazium.online/api/v1/steam/{game_uid}/auth Content-Type: application/json { "ticket": "140000006a7e..." } ``` The answer: ```json { "success": true, "data": { "token": "eyJhbGciOiJIUzUxMiIs...", "expires_at": "2026-10-08T19:04:05Z", "steam_id": "76561197960287930", "family_shared": false, "session_uid": "3f0c...", "blazium_user_uid": "u_..." } } ``` `blazium_user_uid` is only there when the player linked Steam. A token is issued only when Steam accepts the ticket, the account owns the game, and it has no publisher ban. The game sends the token to your servers, which check it as below. The exact URLs for your listing are on its Steam tab, under **Endpoints**. ## Refresh a token Tokens last 1 hour. Before or up to 24 hours after a token expires, the game can swap it for a new one without asking Steam for another ticket: ```http POST https://api.blazium.online/api/v1/steam/{game_uid}/refresh Content-Type: application/json { "token": "eyJhbGciOiJIUzUxMiIs..." } ``` Ownership is checked again, and the old token is revoked. After 24 hours, or once a token is revoked, the game needs a new ticket. ## Check a token on your servers Your servers can check a token themselves. Derive the signing key, verify the HS512 signature with that key, then check the claims. The signing key is HMAC-SHA512 of the UTF-8 string `blazium.games/session:` followed by the listing's `game_uid`, using the auth key as the HMAC key. The raw auth key is not the JWT signing key. A token signed for another listing does not verify, even with the same auth key. Tokens already issued before this derivation (they last 1 hour) will not verify; the game refreshes with a new ticket. | Claim | Value | |---|---| | `iss` | `https://blazium.games` | | `aud` | `steam:{app_id}` | | `gid` | The listing's `game_uid`. | | `sub` | The player's SteamID64. | | `osid` | The owner's SteamID64 when the game is borrowed through Family Sharing. | | `own` | `true` | | `vac` | Whether Steam reported a VAC ban. | | `buid` | The player's Blazium Games user ID, if they linked Steam. | | `jti`, `iat`, `exp` | Token ID, issue time, and expiry. | A local check can't see revocations. To include them, ask Blazium Games, sending the auth key as a Bearer token: ```http POST https://api.blazium.online/api/v1/steam/{game_uid}/server/verify Authorization: Bearer Content-Type: application/json { "token": "eyJhbGciOiJIUzUxMiIs...", "recheck_ownership": false } ``` The answer has `valid`, `expired`, `revoked`, `claims`, and `blazium_user` (`uid` and `username`) when the player linked Steam. With `recheck_ownership: true` it also asks Steam again and adds `ownership`. ## Revoke tokens and check ownership ```http POST https://api.blazium.online/api/v1/steam/{game_uid}/server/revoke Authorization: Bearer { "jti": "..." } // one token { "steam_id": "7656119..." } // every token for a player ``` ```http GET https://api.blazium.online/api/v1/steam/{game_uid}/server/ownership/{steam_id} Authorization: Bearer ``` The ownership answer has `owns_app`, `permanent`, `owner_steam_id`, and `checked_at`. It doesn't need a session token. ## Rotate keys and turn it off On the Steam tab: - **New auth key** makes a new auth key. The old one stops working right away and every session token is revoked. - **New ticket key** makes a new ticket key. Builds with the old one can't sign in until they're updated. - **Replace Web API key** swaps in a new Steamworks Web API key after you revoke the old one. The auth key, ticket key and session tokens keep working. - **Turn off** revokes every token, deletes both keys, and forgets the Web API key. Turning it on again makes new keys. If the auth key leaks, make a new one at once, then update your servers. If the Web API key leaks, revoke it in Steamworks and replace it here. ## Limits | Routes | Limit | |---|---| | `auth` and `refresh` | 60 per minute per IP address, and 1,200 per minute per game. | | `server/*` | 1,200 per minute per game. Wrong auth keys are limited to 30 per minute per IP address. | ## Errors | Code | HTTP | Meaning | |---|---|---| | `4245` | 404 | Steam auth verification is off for this game. | | `4246` | 400 or 401 | The ticket isn't hex, or Steam refused it. Make it with the game's ticket key. | | `4247` | 403 | The Steam account doesn't own the game, or has a publisher ban. | | `4248` | 401 or 422 | The token isn't valid for this game, or its session ended. | | `4249` | 401 | Send the game's auth key as a Bearer token. | | `4240` | 400 | `steam_id` isn't a SteamID64, or revoke got neither `jti` nor `steam_id`. | | `4243` | 502 | Steam didn't answer, or refused the game's Web API key. Replace the key on the Steam tab. | | `4290` | 429 | Too many requests. | ## What players should know Each sign-in stores a session record with the player's Steam ID, the owner's Steam ID for Family Sharing, the linked Blazium Games account if any, the token's expiry, and the IP address. Records are deleted 30 days after the token expires. Tickets aren't stored. See the [Steam API disclosure](./legal/steam-api-disclosure.md) and the [Privacy Policy](https://blazium.games/privacy-policy). # docs/steam-import.md # Import from Steam If your game is already on Steam, you can copy its store page into a Blazium Games listing instead of filling it in by hand. Everything that has a matching field here comes over: the name and description, genres and tags, release status, images, press kit details, price, content warnings, and a link back to the Steam store page. You need [developer mode](./developer-mode.md), the game's Steam app ID, and a Steamworks Web API key for the publisher that owns the app. ## Get a Steamworks Web API key Importing uses a **publisher** Web API key, not a personal Steam Web API key. 1. Sign in to [Steamworks](https://partner.steamgames.com/). 2. Open **Users & Permissions > Manage Groups** and pick a group that has the app. 3. Create a Web API key for the group, or copy its existing one. It is 32 characters, 0-9 and A-F. Blazium Games asks Steam which apps the key covers before it reads anything. A key that doesn't cover the app is refused with `4241`. ## Import 1. Open [Import from Steam](https://blazium.games/import/steam). It is also on your [Dashboard](https://blazium.games/dashboard) as **Import from Steam**, and on the New project page. 2. Enter the app ID, or paste the store link (`https://store.steampowered.com/app/480/...`). 3. Paste the Web API key. 4. Under **Import into**, choose **A new draft listing**, or a listing you own or help run. 5. Untick any **Parts to import** you want to keep as they are. A new listing always takes the name and description. 6. Tick **Enable Steam auth verification** if your game will use [Steam auth verification](./steam-auth.md). Otherwise the key is used for this import only and is not saved. 7. Click **Preview** to see what would change. Nothing is saved yet. 8. Click **Import**. You land on the listing's **Steam** tab. A new listing starts as a draft. Check it over, upload builds, and publish it from the Settings tab as usual. Imported images go through the same size checks as uploads; see [Listings](./listings.md). ## What is imported | Part | Listing fields | |---|---| | Name, tagline and description | Name, short description, and the "About this game" text converted to Markdown. | | Genres, tags, players and inputs | Steam genres and the most used store tags mapped onto platform genres and tags, single-player or multiplayer, local or online play, and keyboard and mouse, gamepad, or VR input. | | Release status | **Released**, or **In development** while Steam says "Coming soon". | | Cover, thumbnail and screenshots | Steam's screenshots, resized to the platform sizes, up to the screenshot limit. The first becomes the cover and thumbnail, and screenshots under 1280x720 are skipped. These replace the current images. | | Press kit release date and website | The release date, website, trailer, and developer and publisher credits on the [press kit](./press-kit.md). | | Price | The US price, or free. A non-USD or missing price is skipped. | | Content warnings and adult flag | Steam's mature content descriptors and age gate. | | Steam store link | The Steam entry in the listing's store links. | | Achievements and integer stats | Published achievement names and integer stats. Float and average-rate stats are skipped. A definition that exists only here stays, and player unlocks and stat values are not removed. | The preview and the result list every field as **imported**, **skipped** (with the reason, such as a value the listing check would refuse), or **not imported**. Languages, system requirements, and DLC have no field here. Achievements and integer stats are copied when that part is ticked. Supported operating systems come from the builds you upload. Import each DLC as its own listing. ## Resync and unlink The listing's **Steam** tab (on the edit page, `/edit/{your-listing}?tab=steam`) shows the linked app and when it was imported and last synced. - **Resync** runs the import again for the parts you tick. Enter the Web API key, or leave it empty when Steam auth verification is on and the saved key is used. - **Unlink from Steam** removes the link, turns off Steam auth verification, deletes its keys, and forgets the Web API key. The imported fields stay as they are. Each Steam app can be linked to one listing. Unlink it there before importing it somewhere else (`4242`). ## Limits - 60 previews and 10 imports or resyncs per account per day (`4290` past that). - Only apps that Steam lists as a game can be imported. - The Web API key is never shown again, never written to logs, and can't be used through MCP. Importing is only on the website. ## API The website calls these routes with your session. They are refused for MCP tokens. | Method and path | Body | Returns | |---|---|---| | `POST /api/v1/private/steam/import/preview` | `app_id`, `web_api_key`, optional `game_uid` and `groups` | The fields that would change: `imported`, `skipped`, `not_imported`, `screenshots`, and `target`. | | `POST /api/v1/private/steam/import` | The same, plus `enable_auth` | `game_uid`, `vanity_name`, `created`, the report, and `steam` (the Steam tab settings). | | `GET /api/v1/private/games/{game_id}/steam` | | The Steam tab settings. `4244` when the listing isn't linked. | | `POST /api/v1/private/games/{game_id}/steam/resync` | `groups`, optional `web_api_key` | The report and the settings. | | `POST /api/v1/private/games/{game_id}/steam/progress` | `mode`: `pull`, `push`, or `sync` | `pull` copies published achievements and integer stats. `push` and `sync` are refused, because Steam publishes those definitions only on the Steamworks site. Steam auth verification has to be on, with an app id and a stored Web API key. | | `DELETE /api/v1/private/games/{game_id}/steam` | | Unlinks the listing. | `groups` can include `text`, `taxonomy`, `status`, `images`, `press`, `price`, `age`, `store_link`, and `progress`. Leaving it out imports every part. A progress pull has its own limit of 30 an hour per listing, separate from the 10 imports a day. ## Errors | Code | HTTP | Meaning | |---|---|---| | `4105` | 403 | Turn on [developer mode](./developer-mode.md) first. | | `4240` | 400 or 422 | The app ID, key, or groups are not valid, Steam has no store page for the app, the app isn't a game, or a progress push or two-way sync was asked for. | | `4241` | 403 | The key isn't a Steamworks publisher key for this app. | | `4242` | 409 | Another listing has this app, or this listing is linked to a different app. | | `4243` | 502 | Steam didn't answer. Try again in a few minutes. | | `4244` | 404 | The listing isn't linked to Steam. | | `4290` | 429 | Daily preview or import limit reached, or the hourly progress pull limit. | Published achievement and integer-stat names are read with `GetSchemaForGame` when that part is imported or pulled. What else Blazium Games reads from Steam, and what it keeps, is in the [Steam API disclosure](./legal/steam-api-disclosure.md). # docs/storefront/approve-agent-requests.md # Approve an agent request When an AI agent connected to your account through [MCP](../mcp/index.md) wants to do something important, it asks you first. You get a link to a page called **Agent request**. 1. Open the link and sign in if asked. 2. Read the line "Your agent wants to: ..." and the details under it. A purchase shows the price and the total taken from your balance. Other actions show what will happen, for example: - **Release to stable**: every player gets this build as the current release. - **Delete game**: the game page, builds and downloads go away for everyone. - **New deploy key**: the old deploy keys stop working, so anything using them must be updated. - **Create game keys**: each key gives one person the game for free. 3. Click **Approve** or **Deny**. "Approved. Your agent can go ahead now." or "Denied. Your agent has been told no." confirms your choice. Only approve requests you asked your agent to make. ## Good to know - Requests expire. An expired request says "This request expired. Your agent can ask again." - Agents only pay from your stored balance, never your card. - Agents with wallet access can set up payouts and cash out your earnings without a request here. Money only goes to the payout account on your own account, and you get an email after each cash-out. See [Agent payouts](../payments/wallet-and-cash-out.md#agent-payouts). - Pending requests are also listed under **Waiting for your approval** in [MCP settings](https://blazium.games/settings/mcp), where you also set how much an agent may spend without asking. See [Agent purchases](../payments/agent-purchases.md). # docs/storefront/builds-and-reports.md # Builds and reports ## Builds Builds are uploaded with a [deploy key](./team-and-keys.md#deploy-keys), from your CI or the [chauffeur CLI](../cli/index.md). The website doesn't take uploads. See [Deploy](../deploy.md). Every upload is scanned for viruses. The **Builds** tab lists each build with its version, platform, channel, scan result and launch health. ### Release channels A clean upload moves beta, dev, and custom channels forward. Stable waits until you promote a build onto it: - **stable** is what every player gets. - **beta** is shown to players who join the beta. - **dev** is only for you and your admins. To change what a channel offers: - **Promote**: pick a build, a channel and how many hours until it expires (0 means never), then click **Promote**. - **Roll back**: returns a channel to its previous build. Players stop seeing the current one, but it isn't deleted. **Delete** removes a build's files, so players can no longer download it. Each build can also have debug symbols, uploaded with the chauffeur CLI, and a check for store assets bundled inside it. Open **Symbols and bundle check** under a build. Crash reports are covered in [Crash reporting](../crash-reporting.md). ### Launch health Launch health shows how reliably the current build starts for players, based on the last 30 days: | Badge | Meaning | |---|---| | **Launches reliably** | At least 98% of launches reached the game, and at most 1% crashed on start. | | **Launches well** | At least 93% reached the game, and at most 3% crashed on start. | | **Mixed launch reports** | At least 80% reached the game, and at most 10% crashed on start. | | **Launch problems reported** | Many launches crashed or never reached the game. | | **Not enough launch data** | Fewer than 20 players launched the current build. | Players see it on the store page, and games with launch problems are marked in Browse. ## Analytics Open **Analytics** from the project's Dashboard card or the bar at the top of the edit page. For the last 30 days it shows visitors, views, actions, countries and downloads. **Download JSON** saves the numbers. The downloads section splits downloads by where they came from, how players had access, which client they used, and why downloads were refused. See [Download analytics](../download-analytics.md). **All analytics** on the Dashboard adds up every project. ## Crashes **Crashes** lists reports from builds that include the crash reporter, with the severity, platform, version and message. **Dump**, **Log** and **Stack trace** download the files; each link works for an hour. See [Crash reporting](../crash-reporting.md). ## Sales **Sales** shows sales and donations, gross revenue, platform fees and your earnings, then a list of each sale. Earnings become available after the refund window ends. Refunded and disputed sales are counted separately. See [Selling](../payments/selling.md) and [Wallet and cash out](../payments/wallet-and-cash-out.md). # docs/storefront/buy-and-download.md # Buy and download a game ![A store page with the price panel](/img/storefront/store-page.png) Every game has a store page at `developer.blazium.games/game`. The top shows the name, tagline, developer, platforms, price and typical session length. Below are the screenshots, **About**, **What's new**, reviews and similar games. The panel on the right is where you buy and download. ## Before you start - **Sign in.** Signed-out visitors see **Log in to buy** or **Log in to donate**, which brings you back to the page after you sign in. - **Verify your email.** Until you do, the button reads **Verify your email to buy** and opens [Verify email](https://blazium.games/settings/verify). Downloads need a verified email too. ## Buy a paid game 1. If the game has more than one edition, pick one under **Edition**. Each edition says what it includes, for example "Includes the beta channel." 2. Choose how to pay: - **Buy for $X by card** opens a secure checkout. Card payments add a processing fee, shown at checkout before you pay. - **Pay from balance ($X available)** uses money you added to your [wallet](../payments/wallet-and-cash-out.md). A summary shows the price, tax and total. Click **Confirm $X from balance** to finish. 3. After a card payment you land on a confirmation page. It says "Payment received. The game is in your library." once the payment clears. If it is still processing, the game is added as soon as the payment is confirmed. If your balance is too low, the panel says "Not enough balance. Add funds or pay by card." Once you own the game, the panel says "You own this game." or "You own the Deluxe edition." While a refund is still possible it also shows the deadline. See [Refunds](../payments/refunds.md). ### Upgrade to another edition If you already own an edition, the panel shows **Upgrade to** with the editions above yours. You only pay the difference. ### Donate to a free game Free games can accept donations. Enter an **Amount (USD)** and click **Donate by card** or **Donate from balance**. Donations are not refundable. ## Download ![The store page sidebar with downloads, the beta panel and game facts](/img/storefront/downloads.png) Each platform has its own button, such as **Download for windows amd64**. Builds from the beta channel say **(beta)**. Under each button you see: - The version and the date it was uploaded. - The virus scan result, such as **Virus scan passed** or **Virus scan in progress**. - A checksum, so you can check the file you downloaded. Paid games say "Downloads unlock after you buy the game." until you own them. To get an earlier build, open **Older versions** and pick one from **Choose an older build**. Some developers only offer the latest build, and then this menu is missing. Some free projects allow downloads without an account. They say "No account needed. Sign in to keep it in your library." Games marked **Play in browser** have a browser pack. A web demo is marked **Demo**. Web files are hosted and are not download buttons. Download buttons are Windows, Linux, content packs, and a non-web demo labeled **Download Demo**. A host name appears only when that build is assigned and the page may offer it. Steam, GOG, Epic, and itch stay on **Also on**. The control at the top of the store page follows whether this visitor can start that build. **Play in browser** opens the full game. **Demo** opens the demo. A priced game's store demo needs an account, so a signed-out visitor sees **Sign in to play**. **Sign in to play**, **Verify your email to play**, and **Buy to play** go to those steps and do not start a session. The player beside the page uses the same address. From the library, **Play** opens that control. **Download** still opens the download list. A mini-game pack is not **Play in browser**. ## Join a beta If a game has a beta, the panel says "This game has a beta with newer, less tested builds." 1. Click **Join the beta**. 2. Beta builds now appear in your download list, marked **(beta)**. 3. To go back to stable builds only, click **Leave the beta**. Some editions include the beta channel. If you own one, beta builds are already in your list. ## What can go wrong - **"Purchases are not available for this project right now."** The game's purchase details could not be loaded. Try again later. - **"Checkout was canceled. You have not been charged."** You left the card checkout before paying. - **"The payment failed. You have not been charged."** Try again or use another card. - **A download sends you to the login page.** Downloads need you to be signed in, unless the project allows downloads without an account. # docs/storefront/chat.md # Game chat Friend messages and each game's chat are IRC on `irc.blazium.online`. Chat follows the [Chat Rules](../legal/chat-rules.md) and is not logged. The full guide is in the [Chat](../chat/index.md) section: - [Chat overview](../chat/index.md): ways in, who can talk, spectating, moderation, and what chat keeps. - [IRC clients](../chat/irc-clients.md): get a chat token from [Settings > Chat](https://blazium.games/settings/chat) and set up HexChat, WeeChat, irssi, or any IRC client (server `irc.blazium.online`, port `6697` with TLS, SASL PLAIN). - [Commands](../chat/commands.md): `GAMEJOIN`, spectating with `LFGSUB`, `GAMES`, and what every reply means. - [For client developers](../chat/client-developers.md): capabilities, message tags, and numerics. - [Chat for publishers](../chat/for-publishers.md): guests, bans, and mutes for your project. - [Troubleshooting](../chat/troubleshooting.md). # docs/storefront/create-a-project.md # Create and edit a project ![The Dashboard with projects and an admin invite](/img/storefront/dashboard.png) Projects are the pages you publish: games, applications, mods, plugins, tools and assets. You need [developer mode](../developer-mode.md) first. Without it, the form says "Creating projects needs developer mode." with a link to the setting. Your projects are on the **Dashboard**, in the account menu. Each card shows the status, the visibility and your role (**Owner** or **Admin**), with buttons for **Edit**, **Analytics**, **Crashes** and, for owners, **Delete**. ## Create a project 1. On the Dashboard, click **New Project**. 2. Fill in **Name** and **Project URL**. The URL is the part after `username.blazium.games/`: lowercase letters, numbers and dashes. 3. Add a **Short description** of up to 255 characters. 4. Add both images: - **Add thumbnail**: 960×540 to 1920×1080, 16:9, up to 5 MB. - **Add cover**: 1024×576 to 2048×1152, 16:9, up to 8 MB. Image guidance is in [Graphical asset guidelines](../graphical_assets_guidelines.md). 5. Choose the **Project type**, **Status** and **Visibility**. 6. Write the **Description**. The editor supports headings, lists, links, tables and code, or you can switch to plain Markdown. 7. Click **Create project**. The edit page opens. Mods, plugins and tools pick their parent game on the edit page after you create them. ### Visibility | Option | Who can see the page | |---|---| | **Draft (you and admins)** | You and the project's admins. | | **Owner only** | Only you. | | **Invisible (link only)** | Anyone with the link. It isn't listed anywhere. | | **Public** | Everyone. Listed in Browse and on the home page. | Draft and owner-only pages show a notice at the top, so you can preview the store page before going public. ## The edit page ![The edit page Settings tab](/img/storefront/edit-project.png) The edit page has a tab for each part of the project. Links such as `/edit/my-game#builds` open a tab directly. | Tab | What it's for | |---|---| | **Settings** | Images, name, URL, type, parent game, status, description, visibility, the adult content flag, search engine indexing, and [anonymous downloads](../anonymous-downloads.md). | | **Listing** | Genres, tags, engines, tone, inputs, session length, players, network, content warnings, how it was made, generative AI use and similar titles. See [Listings and search](../listings.md). | | **Pricing** | Price, donations and editions. See [Selling](../payments/selling.md). | | **Images** | Screenshots for the store page carousel: 1280×720 to 2048×1152, 16:9, up to 10 MB each. | | **Admins**, **Deploy keys**, **Game keys** | See [Team and keys](./team-and-keys.md). | | **Builds** | See [Builds and reports](./builds-and-reports.md). | | **MCP** | Connect an AI agent to this project. See [MCP](../mcp/index.md). | | **Mod settings** | Mods and plugins only: the install folder, the mod loader and install instructions. | | **Press kit** | Facts, links, quotes and team for your public press page. See [Press kit](../press-kit.md). | | **Player tags** | Tags players suggested. Hide any you don't want shown. | | **Links** | Other listings this project uses or works with, and pages on other stores, shown under **Also on**. | Most tabs have their own save button, such as **Save**, **Save listing** or **Save pricing**. ## Make it public A project needs to pass the listing check before it can be public. The check shows at the top of the **Listing** tab, and under **Visibility** while the project isn't public: - **✗** items are required, for example enough tags and a build that passed the virus scan. - **!** items are recommended, such as three or more screenshots. When everything required passes, it says "Listing ready to be public". Then set **Visibility** to **Public** and click **Save**. You also need a verified email. Until then, the edit page says "Your email is not verified, so this project cannot be public and builds cannot be uploaded." Adult content and the generative AI disclosure must be labeled honestly. See [Content rules](../content-rules.md). ## Rename the project URL Change **Project URL** on the **Settings** tab and click **Save**. The store page moves to the new address, so update any links you shared. ## Delete a project Only the owner can delete a project. 1. On the Dashboard, click **Delete** on the project's card. 2. The dialog says "The project, its page, and its downloads will no longer be available. Admins lose access too." 3. Click **Delete project**. # docs/storefront/desktop-app.md # The desktop app BlaziumLauncher installs, updates and launches the games in your library. It is not BlaziumHub. BlaziumHub installs editors and lives in `{autopf}\Blazium\Engine`. ## Download it Both downloads are on the [launcher releases](https://github.com/blazium-games/games_launcher/releases) page. - **Windows**: the setup (`BlaziumLauncher-Setup-.exe`). Windows 10 or 11, 64-bit. The program is `BlaziumLauncher.exe` under `{autopf}\Blazium\Games`. Shared tools live in `{autopf}\Blazium`. - **Linux**: the Debian package (`blazium-games__amd64.deb`), x86_64. Install it with `sudo apt install ./blazium-games__amd64.deb`. The program is `/opt/blazium/games/BlaziumLauncher`, with a menu entry. macOS is not supported. If `blazium-cli` or BlaziumHub is already installed, either installer leaves BlaziumHub's `blazium://` handler and `hub_remote.json` alone and writes `launcher_remote.json` instead. Otherwise BlaziumLauncher registers `blazium://` itself. The Windows setup can also download BlaziumHub into the same folder. ## What it does - **Library**: browse and launch purchased and free games. - **Friends**: the friends window. - **Chat**: friend messages and game chat on `irc.blazium.online` port 6697, one tab per friend and per game. It asks before sending a message or a game invite. See [Chat](../chat/index.md). - **Links**: `blazium://install/`, `blazium://game/`, and `blazium://buy/` open in BlaziumLauncher. `blazium://buy` does not install. `blazium://hub` and `blazium://install?version=` stay with BlaziumHub. ## For developers Upload builds with `npm install -g @blazium-games/cli` (`chauffeur`). Source: [blazium-games/games_cli](https://github.com/blazium-games/games_cli). The command has builds for Windows, Linux, and macOS (Apple Silicon and Intel). See the [chauffeur CLI](../cli/index.md). # docs/storefront/dmca.md # Copyright (DMCA) notices If content on Blazium Games infringes your copyright, file a notice at [blazium.games/dmca](https://blazium.games/dmca). It's the only way we accept copyright notices. The rules are in [section 17.1 of the Terms of Service](https://blazium.games/terms-of-service#171-copyright-and-dmca-notices). Blazium Games' designated DMCA agent is registered with the United States Copyright Office as DMCA-1085117, and notices are still filed only through this form. ## The fee Filing costs **$100, plus $100 for each uploader account** your links belong to. Links to two games by the same developer cost $200; links to games by two different developers cost $300. The form shows the total before you pay. The fee pays for reviewing and verifying the claim. The notice work is performed when the fee is paid. **It is not refundable**, whether the claim is accepted, rejected, resolved, closed, or withdrawn. A refund or chargeback started in Stripe is noted on the claim. The claim stays open, and the fee is not returned. ## File a notice You don't need an account. 1. Open [blazium.games/dmca](https://blazium.games/dmca). If you emailed a notice to [dmca@blazium.games](mailto:dmca@blazium.games), the automatic reply has a link that fills in your email address and the links from your message. 2. Enter your **Full legal name**, **Company** (optional), **Email**, **Phone** and **Postal address**. 3. Describe the work you own, or are authorized to act for. 4. Paste the links to the content on blazium.games, one per line, up to 50. Use a listing page (`developer.blazium.games/game-name`), a developer page (`developer.blazium.games`) or a download link. Each link is checked as you type: a ✓ shows the listing and account it belongs to, and a ✗ explains what's wrong. The fee updates with each new account. 5. Tick the good faith and penalty of perjury statements, and type your full legal name as your signature. 6. Tick that you understand the fee isn't refundable, then click **Pay $… and file**. You pay on Stripe Checkout. After payment you're sent back to a page that shows your claim reference (`DMCA-` and six characters) once the payment is confirmed, and the receipt email includes that reference. Keep it for any follow-up. If you cancel Stripe Checkout, the notice is not filed and your card is not charged. Notices sent by email, post or any other way aren't filed. An email to dmca@blazium.games only gets the automatic reply with the link. ## What happens next - We forward your notice to each uploader named in it, including your name, company and email address. Only our staff see your postal address and phone number. - Our staff review the claim and may email you or the uploader for more information. - If we decide the claim is valid, we may disable or remove the content and suspend or ban the uploader's account. If not, we close the claim and the content stays up. Staff decide alone. Filing doesn't guarantee removal, and we don't owe an explanation or an appeal. - Account action is decided claim by claim. There is no fixed repeat-infringer policy. - While a claim is open, we keep a record of each named listing and file as it was when you filed, even if the uploader changes or deletes it. - We don't share the uploader's identity or contact details without a United States court order. - Forwarding a notice or deciding a claim is not legal advice, and it is not an admission that the content does or does not infringe. To add information to your claim, email [dmca@blazium.games](mailto:dmca@blazium.games) with your claim reference in the subject. ## If a notice names your content You get an email with the notice, and it shows up under **Settings > Copyright notices** at [blazium.games/settings/copyright](https://blazium.games/settings/copyright). A banner on your dashboard points to it while a claim is under review. Notices appear only once the claimant has paid. The list shows each notice's reference, status, claimant, filing date and how many of your links it names. A notice is `open` while staff are reviewing it, then `accepted`, `rejected`, `resolved`, or `closed`. Open one to see: - the claimant's name, company and email address - the work they describe, their statements and signature - your links that it names, and whether a listing was disabled - messages from our staff, such as a request for information - the decision, once there is one There is no formal counter-notice. What you can do: - Answer the claimant directly at their email address, if you want to. - Send us anything relevant, such as a license or proof that the work is yours, by emailing [dmca@blazium.games](mailto:dmca@blazium.games) with the reference in the subject. - Remove the listing or any of its builds yourself at any time from your dashboard. AI agents connected with the developer MCP tools can read the same notices with `list_copyright_notices` and `get_copyright_notice`. Nothing about a notice can be changed over MCP. See the [MCP reference](../mcp/reference.md#copyright-notices). You remain responsible for what you upload. See [What you upload is yours to answer for](../deploy.md#what-you-upload-is-yours-to-answer-for). # docs/storefront/embed.md # Embed a game on your website ![The Embed this game dialog](/img/storefront/embed-dialog.png) Anyone can put a small widget for a game on their own website. 1. Open the game's store page. 2. Click **Embed**, near **Report** and **Press kit**. 3. The **Embed this game** dialog shows a preview and the HTML. 4. Copy the HTML and paste it into your page. The code looks like this: ```html ``` ## What the widget shows - The thumbnail, the name, the developer and the tagline. - **Free** for free games and **Play in browser** for a browser pack. A web file is not a download. - The download count, when the game has been downloaded at least once. - A main button: **Buy** for paid games, otherwise **Play now** (web build), **Download** or **View**. - A **Blazium Games** link. Both buttons open in a new tab, so visitors don't leave your page. The main button goes to the store page, where they buy or download as usual. The widget always shows the game's current details, so you don't need to update the code when the game changes. # docs/storefront/find-a-game.md # Find a game ## The home page ![The home page with the Featured game and the Friends are playing row](/img/storefront/home.png) The [home page](https://blazium.games) is a set of shelves. Each shelf only lists games that have a clean download for the platform your browser reports, so a Linux visitor sees games that run on Linux. Shelves with nothing to show are hidden. | Shelf | What it shows | |---|---| | **Featured** | One standout game, shown large. | | **New releases** | Games published in the last 30 days, newest first. | | **Recently updated** | Games and apps with the newest builds. | | **Made with Blazium** | Projects built with the Blazium engine. | | **In development** | Games still in development or at the prototype stage. | | **Play in your browser** | Games with a web build. | | **From the community** | Games players have reviewed and tagged recently. | | **Tools, mods & assets** | Tools, mods, plugins and assets for developers. | | **Something for tonight** | Short games that launch reliably. | | **Unheard of** | New games that few players have found so far. | Shelves with a **See all** link open Browse with the matching filter already set. When you are signed in and a friend has played something in the last 14 days, a **Friends are playing** row appears under Featured. See [Friends](./friends.md). If a shelf fails to load, the page says "Some sections could not be loaded. Reload the page to try again." ## Game cards Each card shows the title, the developer, a short tagline and the price (or **Free**). Depending on the game, it can also show: - **Play in browser** for a browser pack, **Demo** for a web demo, or **Download** for Windows, Linux, and content packs. Web files are not downloaded. - **In development** or **Prototype**. - How long a session usually lasts and how many players it supports. - How it was made: **Made by people**, **People with AI agents** or **Mostly AI agents**, as the developer states it. - **18+** for adult listings. These only appear after you [turn on adult content](./profile-and-settings.md#adult-content). On Browse, a game with launch problems also shows **Launch problems reported**. Click the title or picture to open the store page, or the developer's name to open their page. ## Browse ![Browse with the filter panel open](/img/storefront/browse.png) Open **Browse** in the header. 1. Type in **Search for games, mods and tools**. Results update as you type. 2. Pick a quick filter: **All**, **New**, **Updated**, **Multiplayer**, **Browser** or **Made with Blazium**. Picking one replaces the previous quick filter. 3. Pick one or more types: **Game**, **Application**, **Mod**, **Plugin**, **Tool**, **Game asset** or **Development asset**. Click a type again to turn it off. 4. Change the order with the sort menu: **Best match**, **Newest** or **Recently updated**. Click **More filters** for more options. Each group opens when you click it, and its summary says how many options are shown or hidden. - **Genre**, **Tone** and **AI use** let you pick what to show and also what to hide. - **Session length**, **Network**, **Platform** and **Made with** narrow the results to what you pick. - **Content warnings** only hides: tick **Hide violence**, **Hide flashing lights** and so on. - The text boxes filter by tags, hide tags, and a number of players. - **Hide adult content** (signed in only) leaves adult listings out of this search even if you have turned them on. A dot on **More filters** means one of these is set. **Clear all** resets everything. If nothing matches, the page says "Nothing matches these filters. Try fewer filters or clear them all." ## Mods and tools for a game A game's store page can have **Tools and utilities** and **Mods and plugins** rows. Items marked **From the developer** come from the game's own developer; **Community** items come from other people. **See all** opens a page with every mod or tool for that game, split into **From the developer** and **From the community**. A mod's store page shows whether it works with the game's current build, and **How to install** explains where its files go. ## The developer's page Each developer has a page at `username.blazium.games` with their **Games**, **In development** and **Tools, mods & assets**. Adult listings are hidden there too unless you have turned them on. # docs/storefront/friends.md # Friends ![The Friends page](/img/storefront/friends.png) Open **Friends** from the account menu. ## Add a friend 1. Type their username in **Username**. A leading `@` is fine. 2. Click **Send request**. The page says "Request sent to @name". If they had already sent you a request, you become friends right away. Requests you sent are listed under **Sent requests**, where **Cancel** withdraws one. ## Answer a request Incoming requests are under **Requests**. Click **Accept** or **Decline**. ## See what friends play - **Playing now** lists friends in a game right now. - **Your friends** shows each friend as **Playing** a game, **Online** or **Offline**. - **Played in the last 14 days** lists recent games. The home page shows the same recent games in **Friends are playing**. **Remove** takes someone off your list straight away. There is no confirmation. ## Chat Friend messages and each game's chat are on `irc.blazium.online`. A friend message is a private message to your friend's username, so it works from BlaziumLauncher or any IRC client. In the launcher you can also invite a friend to a game. Details are in [Chat](../chat/index.md). ## Activity sharing Under **Activity sharing** you choose whether friends see what you play: - **Stop sharing** hides your current and recent games from friends. - **Share with friends** shows them again. ## Profile visibility Profile visibility is separate from activity sharing and from each game's visibility. Set it on Profile at [settings](https://blazium.games/settings). - **Public:** anyone can open your profile. - **Private:** a signed-in friend and you can open it. Everyone else sees a page that says the profile is private. - **Hidden:** nobody else can open it, including friends. The page says the profile is hidden. You can still open your own page while signed in. # docs/storefront/get-help.md # Get help The [Support page](https://blazium.games/support) lists the right place for each kind of problem. It opens without signing in. Check the [status page](https://status.blazium.games) first. If something is down, it will say so there. | Problem | Where to go | |---|---| | A bug in the website, the desktop app, the MCP servers or the chauffeur CLI | Open an issue on [GitHub](https://github.com/blazium-games/support/issues). Search the open issues first. | | Your account, a purchase or a refund | Email [support@blazium.games](mailto:support@blazium.games) from the address on your account. For a purchase, include the purchase ID from your wallet or receipt. | | A bug in a game | Contact the game's developer. | | Your data, or deleting your account | Email [privacy@blazium.games](mailto:privacy@blazium.games). | | Someone breaking the [Chat Rules](../legal/chat-rules.md), or your account can't use chat | Email [support@blazium.games](mailto:support@blazium.games). See [Something in chat](./report.md#something-in-chat). | | A leaked chat token | Regenerate it in [Settings > Chat](https://blazium.games/settings/chat). That disconnects anyone using the old one. | | Chat won't sign in, won't let you join, or won't let you talk | See [Chat troubleshooting](../chat/troubleshooting.md). | | A security problem | Report it privately on GitHub: [Report a vulnerability](https://github.com/blazium-games/support/security/advisories/new). If you can't use GitHub, email [support@blazium.games](mailto:support@blazium.games) with "Security" in the subject. Don't post it in a public issue. | GitHub issues are public. Never include passwords, keys, payment details or your email address in them. To report a game or a person that breaks the rules, see [Report a game or a person](./report.md). Refund rules are in [Refunds](../payments/refunds.md). # docs/storefront/index.md # Using Blazium Games These guides walk through the [blazium.games](https://blazium.games) website. Each one names the buttons and messages you will see, so you can follow along in another tab. The screenshots use sample games and accounts. ## Playing - [Find a game](./find-a-game.md): the home page shelves, Browse, filters, and mods and tools for a game. - [Buy and download a game](./buy-and-download.md): paying by card or from your balance, downloads, older versions, and betas. - [Your library](./library.md): the games you own and how to get back to their downloads. - [Redeem a key or gift link](./redeem-a-key.md) - [The desktop app](./desktop-app.md) - [Friends](./friends.md): requests, who is playing what, and activity sharing. - [Chat](../chat/index.md): friend messages and game chat, IRC on `irc.blazium.online`. - [Reviews and player tags](./reviews-and-tags.md) - [Report a game or a person](./report.md) - [Copyright (DMCA) notices](./dmca.md) - [Embed a game on your website](./embed.md) ## Your account - [Sign up and sign in](./sign-up-and-sign-in.md): email, GitHub, X or Discord, emailed codes, and updated terms. - [Profile and settings](./profile-and-settings.md): avatar, username, adult content, and cookie choices. - [Approve an agent request](./approve-agent-requests.md) - [Get help](./get-help.md) Security settings are covered in [Account security](../account-security.md) and [Linked accounts](../linked-accounts.md). Money is covered in [Payments](../payments/index.md). ## Publishing - [Create and edit a project](./create-a-project.md): the new project form, the edit page tabs, the listing check, and deleting a project. - [Team and keys](./team-and-keys.md): admins, deploy keys, and game keys. - [Builds and reports](./builds-and-reports.md): release channels, launch health, analytics, crashes, and sales. Publishing needs [developer mode](../developer-mode.md). # docs/storefront/library.md # Your library ![The library with two games](/img/storefront/library.png) Open your library from the account menu: **Library**, under the player items. It lists every game you bought or were given, with: - The developer. - Your play time, or "Not played yet". - **Bought** or **Granted** and the date (UTC). - "Refundable until ... UTC. Contact support" while a refund is still possible. See [Refunds](../payments/refunds.md). ## Filter the list The chips above the cards narrow the list: | Chip | Shows | |---|---| | **All** | Everything you own. | | **Ready to play** | Games with a web build or a download. | | **Browser** | Games with a web build. | | **Download** | Games with a download. | | **In development** | Games still in development or at the prototype stage. | If nothing matches, click **Show all**. ## Get a game Each card has buttons for what the game offers: - **Download** opens the game's store page at its downloads. See [Buy and download a game](./buy-and-download.md#download). - **Play** appears for games with a browser pack and opens the store page to play in the browser. It does not start a web download. - **Store page** opens the store page. You can also install and update your games with the [desktop app](./desktop-app.md). ## An empty library A new account shows "Your library is empty." with a **Browse games** button. Free games are added the first time you download them, and keys are added when you [redeem them](./redeem-a-key.md). # docs/storefront/profile-and-settings.md # Profile and settings ![Account settings with the Profile card](/img/storefront/settings.png) Open **Settings** from the account menu. The side menu has **Account**, **Linked accounts**, **Authenticator**, **Verify email**, **Wallet**, **MCP**, **Chat** and **Copyright notices**. ## Profile - **Upload avatar**: a square image from 256×256 to 512×512 pixels, up to 2 MB (PNG, JPG, GIF or WebP). Without one, your initials are shown. - **Username**: your developer page lives at `username.blazium.games`, so changing it changes your store links. - **Display name**: the name shown on your page and in the header. - **Timezone**: used for dates and times. Click **Save**. "Settings saved" confirms it. Your public page at `username.blazium.games` shows your avatar, display name, username and published projects. Click **View profile** in the account menu to see it. ## Developer mode Turning on developer mode lets you publish games, mods and tools. Players don't need it. See [Developer mode](../developer-mode.md). ## Adult content Adult listings (sexual content or nudity) are hidden by default, and always hidden from people who aren't signed in. To see them: 1. Under **Adult content**, tick "I am 18 or older, and adult content is legal where I live". 2. Click **Show adult content**. Adult listings then appear in Browse, on developer pages and on store pages, marked **18+**. **Hide adult content** turns them off again. You can still leave them out of a single search with **Hide adult content** in Browse's filters. How developers label adult content is covered in [Content rules](../content-rules.md). ## Chat **Chat** creates a chat token so you can use your own IRC client (HexChat, WeeChat, irssi, and others) with game chat. The token is shown once. **Regenerate token** replaces it and disconnects every client signed in with the old one (tick **Disconnect clients using my current token** first); **Revoke token** removes it. The page also shows the server settings. See [IRC clients](../chat/irc-clients.md) and the [Chat Rules](../legal/chat-rules.md). ## Copyright notices **Copyright notices** lists the paid copyright (DMCA) notices that name your content, with their status and any messages from our staff. It's empty unless someone has filed one. See [Copyright (DMCA) notices](./dmca.md#if-a-notice-names-your-content). ## Cookies The first time you visit, a banner asks about analytics. **Accept** turns on Google Analytics and browser fingerprinting, which help us understand how game pages are used. **Decline** keeps them off. Sign-in cookies are always on because the site needs them. To change your choice later, click **Cookie settings** at the bottom of any page. The details are in [Permissions](../legal/permissions.md). # docs/storefront/redeem-a-key.md # Redeem a key or gift link Developers hand out keys and gift links for press, bundles and giveaways. Each one adds a game to your library for free. ## Redeem a key 1. Sign in, open the account menu and choose **Redeem a key**. 2. Type or paste the code into the box. Codes look like `XXXXX-XXXXX-XXXXX-XXXXX`. 3. Click **Add to my library**. When it works, the page says "Starfall Drift is in your library." (with the game's name), and offers **Go to** the game and **Library**. ## Open a gift link A gift link looks like `https://blazium.games/redeem/...`. Opening it fills in the code for you. Sign in if asked, then click **Add to my library**. ## Good to know - Each code works once. - If you already own the game, the code stays unused, so you can pass it on to someone else. - If the page says the code was not found or was already used, check it for typos, then ask whoever gave it to you. For anything else, see [Get help](./get-help.md). # docs/storefront/report.md # Report a game or a person If a game or a person breaks the rules, report it from their page. You don't need an account. 1. Click **Report** on the game's store page or on the developer's page. 2. If you are signed out, enter **Your Email** so we can ask for more details. 3. Pick a **Report Category**: spam, inappropriate, harassment, copyright or other. 4. Describe the problem in **Detailed Report Reason**. Links and specifics help. 5. Click **Submit Report**. A message under the form confirms it was sent. Reports are reviewed against the [Terms of Service](https://blazium.games/terms-of-service#16-community-guidelines-and-reports), and what happens next is our decision. ## Something in chat Chat follows the [Chat Rules](../legal/chat-rules.md). In a game's channel, the game's owner and admins can ban or mute someone. For anything else, email [support@blazium.games](mailto:support@blazium.games) with the channel, the usernames, and the time. Chat isn't logged, so a screenshot helps. If a child is in danger, contact your local authorities first. ## Copyright notices A report with the **copyright** category is input to our own moderation, not a copyright notice. A report, an email, or any other demand is not a takedown. [Section 17 of the Terms](https://blazium.games/terms-of-service#17-moderation-is-our-decision) says outside demands are not orders we follow. The only outside process is a paid copyright notice under [section 17.1](https://blazium.games/terms-of-service#171-copyright-and-dmca-notices), filed at [blazium.games/dmca](https://blazium.games/dmca). See [Copyright (DMCA) notices](./dmca.md) for the fee and what happens next. If a notice names content you uploaded, you can read it under **Settings > Copyright notices**. You are responsible for what you upload. ## Bugs are different A bug in a game is not a report. Contact the game's developer instead. For problems with the website, the desktop app or your account, see [Get help](./get-help.md). # docs/storefront/reviews-and-tags.md # Reviews and player tags ## Read reviews **Player reviews** on a store page sums up every review: how many there are, the share of players who enjoyed it, the average quality out of 5, and the share who would play it with friends. Each review shows whether the player enjoyed the game, the quality they gave, their play time once it passes an hour, and any reply from the developer. ## Write a review The review form appears on the store page once you can review the game, usually after you own it. 1. Under **Did you enjoy it?**, choose **Yes** or **No**. 2. Under **Quality, separate from whether you enjoyed it**, pick a score from 1 to 5. 3. Tick **I'd play it with friends** if that fits. 4. Optionally, write what stood out, up to 4000 characters. 5. Click **Post review**. To change it later, edit the form and click **Update review**. **Delete** removes it. Developers can reply to reviews. A reply shows under your review as "Developer replied: ...". ## Player tags **Players say** lists tags that players agree describe the game. With no public tags, the page says "You can add tags to this" instead of an empty section. With no reviews, the page says "Be the first to review this game." You can suggest tags for a game you own after you have played it for an hour: 1. Type a tag in **Suggest a tag**, for example `short-runs`. Tags are letters, digits and dashes, up to 32 characters. 2. Click **Suggest**. The counter shows how many suggestions you have left. Your tags appear under **Your tags**. Click a tag's **×** to take it back. A tag shows on the store page once three players who played for an hour suggest it. The developer can hide a tag. Until you have played long enough, the page says how much play time you still need. # docs/storefront/sign-up-and-sign-in.md # Sign up and sign in You need to be at least 13 to use Blazium Games. Buying, adding money and cashing out need you to be 18, or to have a parent or guardian who accepts the [Terms of Service](https://blazium.games/terms-of-service). Uploading or publishing needs you to be 18 or otherwise able to enter a contract. ## Create an account with email 1. Click **Sign up** in the header. 2. Fill in **Email**, **Username** and **Password**, then type the password again in **Confirm password**. - Usernames are 4 to 32 letters, numbers or hyphens, and start and end with a letter or number. Your username becomes your developer page address, `username.blazium.games`, so some names are reserved. - Passwords are 10 to 128 characters. **Show** next to the password displays what you typed; **Hide** masks it again. - If the two passwords differ, the form says "The passwords don't match." and won't submit. 3. Tick "I accept the Terms of Service and Privacy Policy". 4. Click **Sign up**. 5. Enter the 6-digit code we email you and click **Confirm**. The code works for 10 minutes. If the code doesn't arrive within a minute, check your spam or junk folder for mail from noreply@blazium.games. **Send another code** sends a new one after a short wait. ## Sign in with email 1. Click **Log in**. The GitHub, X and Discord buttons are at the top; the email form is below "or use email". 2. Enter your **Email** and **Password**, then click **Log in**. 3. If we ask for a code, enter the one from your email or your authenticator app. If you came from another page, you return to it after signing in. "Your session expired. Log in again to continue." means you were signed out after a while. Sign in again and you continue where you were. ## Sign in with GitHub, X or Discord Click **GitHub**, **X** or **Discord** on the sign-up or login page. - **First time with this service:** if it isn't linked to an account yet, we ask you to **Finish your account** with an email and password, then **Send code** to confirm the email. If the email is already registered, you confirm that account's password instead, and the service is linked to it. - **Already linked:** you may be asked to **Confirm your password**, and then for a code. Some accounts are asked to choose a second step. **Set up an authenticator app** uses a phone app for codes; **Email me a code instead** keeps using emailed codes. You can change this later. To link or unlink services, see [Linked accounts](../linked-accounts.md). ## Finish setting up After signing in, you may see a **Finish signing in** page. It walks you through whatever is still missing: - **Finish setting up your account**: choose a username, and a password if you don't have one. - **Protect your account with an authenticator app**: set one up, or click **Skip for now** to keep using emailed codes. Save the recovery codes you see after setting up an authenticator. They are shown only once. More in [Account security](../account-security.md). **Log out instead** is always available on this page. ## Updated terms When the Terms of Service or the Privacy Policy change, you see **Review the updated terms** the next time you sign in. 1. Read the summary of each change. The titles open the full documents. 2. Tick "I have read and accept the updated Terms of Service and Privacy Policy". 3. Click **Accept and continue**. Until you accept, other pages send you back here. Support and the legal pages still open. ## Forgot your password 1. On the login page, click **Forgot password**. 2. Enter your email and click **Email me a code**. 3. Enter the 6-digit code and a **New password**, then click **Reset password**. "Password reset" confirms it. Your other sessions are signed out. ## Verify your email Buying, downloading, publishing, uploading builds and cashing out need a verified email. The exception is a free project whose developer turned on [anonymous downloads](../anonymous-downloads.md), which anyone can download without an account, and play the web build and the demo without an account. Until you verify, a banner says "Verify your email to publish games, upload builds, download, and buy." 1. Click **Verify now** in the banner, or open Settings and choose **Verify email**. 2. Click **Send code**. 3. Enter the code and click **Verify**. ## Log out Open the account menu and click **Log out**. On a developer's page, you are asked "Log out of Blazium Games on this browser?" first. # docs/storefront/team-and-keys.md # Team and keys ## Admins Admins can edit the project, upload builds and manage keys. Only the owner can delete the project or change who may use MCP. ### Invite an admin 1. On the edit page, open the **Admins** tab. 2. Enter a username or user ID in **Add an admin**. 3. Click **Add admin**. Accepting turns on [developer mode](../developer-mode.md) for the person if it isn't on yet. ### Accept an invite Invites appear at the top of your Dashboard under **Admin invites**, as "Name invited you to help manage Game". Click **Accept** or **Decline**. If developer mode is off, tick **I accept the developer terms** first; accepting then turns it on. After you accept, the project is in your Dashboard list with the **Admin** badge. ### Remove an admin On the **Admins** tab, click **Remove** next to their name and confirm. This also revokes their MCP key for the project. ## Deploy keys A deploy key is two values for one project: an access token and a secret. chauffeur and CI need both. 1. Open the **Deploy keys** tab. 2. Click **New deploy key** and confirm. Creating a new deploy key replaces the previous one. Uploads that used the old key stop working. 3. Copy the secret before you leave the page. It is shown once. It cannot be shown again. The access token is `BLAZIUM_ACCESS_TOKEN`, sent as `X-Access-Token`. It stays on the Deploy keys tab. The secret is `BLAZIUM_SECRET_KEY`, sent as `X-Secret-Key`. The short code in the table is the start of the access token and is not enough to upload. To remove a key, click **Delete** next to it. Uploads that used it stop working. How to upload is covered in [Deploy](../deploy.md). ## Game keys and gift links Game keys give the game to someone for free, for press, bundles or giveaways. Each code works once. 1. Open the **Game keys** tab. 2. Create a pool: enter a name such as "Press", optionally a campaign, and click **New pool**. 3. To make keys, enter how many (1 to 5000) and click **Create keys**. 4. Download the CSV straight away. It works once and expires after an hour, because codes are stored in a form we can't read back. For a single person, click **Gift link** instead. You can add a note in **For (optional)**. The link is shown once, so copy it before leaving the page. The pool table shows how many keys were created and redeemed. Players use keys and links on the [Redeem](./redeem-a-key.md) page. # docs/web-player.md # Browser player A game or application can play in the browser. Upload a web build, then open **Edit project → Web player**. The player hosts Godot and Blazium single-pack shells, Godot and Blazium HTML5, Unreal 4.23, Unreal 5.8 and 5.9 WebGPU, Unity WebGL, and a browser pack for BabylonJS, Cocos, Construct, Defold, Flutter, melonJS, Phaser, PixiJS, PlayCanvas, React, three.js, Kaplay, p5, GDevelop, GameMaker, or a custom page. Pick one web build as the full game. You can pick a different web build as the demo. The player uses the same page rules as the store page: who can see the page, adult content, and whether anonymous play is allowed. Status (released, in development, and the rest) is a badge. It does not hide the player. Hiding the page hides the player. ## Who can play | Page | Who is offered a player | | --- | --- | | Draft | You and accepted admins | | Owner only | You | | Link only | Anyone with the link, once the page can be bought or played | | Public | Anyone, once the page can be bought or played | | Viewer | Price | What plays | | --- | --- | --- | | You or an accepted admin | Any | Full build | | Signed-in player | Free | Full build. They receive a free license first, and they keep the full build if you later add a price | | Signed-out visitor | Free, and anonymous downloads are on | The full build when it can play. Otherwise the web demo. No license | | Signed-out visitor | Free, anonymous downloads off | No player. They need to sign in | | Signed-out visitor | Paid | No player. They need to sign in. The store demo does not start | | Someone who already has the game | Paid | Full build | | Signed-in player who does not have the game | Paid | The demo, if you set one. Otherwise the buy button | An embed plays the build marked embed-supported. That build cannot be priced, and the launch does not grant a license. Adult listings and drafts cannot be embedded. Embed is off until you turn it on, and only a public page can be embedded. Turning on **Enable embedded game** refuses a listing price and every build price. ## Upload Send `os=web` with `web_engine`, `web_version`, and `web_variant`. Add `web_pack` (`browser`, `tiktok`, `douyin`, or `wechat`) and `export_targets` when the pack is checked for another host. A Godot or Blazium `web_nothreads` pack is one `.pck`. An Unreal 4.23 cook includes `Utility.js` and stays on the generated page. Unreal 5.8 and 5.9 WebGPU packs bring their own `index.html`, one `.js`, and one `.wasm`, and they need cross-origin isolation outside Discord, Telegram, and a Playables preview. A Unity WebGL folder needs `index.html`, a `.loader.js`, a `.framework.js` or `.js`, a `.data`, and a `.wasm`. A mini-game pack needs `game.js`, `game.json`, and `project.config.json`, and it is downloaded for TikTok ttmg, Douyin DevTools, or WeChat DevTools. The version has to be one the player host publishes. Unity WebGL and the generic `web` rows accept the publisher's version. A web file is hosted. Visitors do not download it. Play in browser is the full build. Demo is the web demo. A non-web demo stays a download labeled Demo. ## Embed The store card embed stays the store card. A separate snippet plays the game: ```html ``` Replace `GAME_UID` with the game id. Add `allow="fullscreen"` when fullscreen is on. ## Discord activity The Discord section is on the Web player tab only after the saved browser player is enabled. Turning the browser player off turns Discord hosting off. Hosting can be turned on only while the player is already on. Discord hosting does not follow the embed switch. Adult listings and hidden pages are not offered as a Discord launch, the same way an embed is refused. Turn hosting on with the Application ID and the Public Key from that Discord application. Both are required. There is no bot token. Enable Activities, check the supported platforms, and leave Application URL Override off in production. For local proxy testing, use a tunnel you reset when you do not own the domain. Do not trust SDK user, guild, or channel fields as proof. Copy the mappings into the Discord portal. Targets have no `https://`. The shortest prefix, `/`, is last. | Prefix | Target | | --- | --- | | `/blazium/api` | `api.blazium.online` | | `/blazium/login` | `login.blazium.online` | | `/blazium/lobby` | `lobby.blazium.online`, only when this game's lobby is on as Relay or Scripted | | `/` | `{uid}.play.blazium.online` | There is no mapping for `stun.blazium.online` or `turn.blazium.online`. Leave the TURN switch off for this activity. A threaded web build is not served with COOP or COEP. Assign the build that Discord launches. That build cannot be priced, and the launch does not grant a license. A paid game with no assigned build plays its demo. A free game with anonymous play plays the full build. A Discord player still has to sign in and own the game or hold a license before the lobby socket accepts them. ## Telegram Mini App Telegram is a launch of the same browser pack, not a second profile. Turn it on with the numeric bot id and paste `https://{uid}.play.blazium.online/` into the bot menu or an inline button. No bot token is stored. The page loads `https://telegram.org/js/telegram-web-app.js`, then calls `Telegram.WebApp.ready()` and `Telegram.WebApp.expand()`. games_service checks `initData` with Telegram's published Ed25519 key and the bot id, and rejects `auth_date` older than one hour. That check is not a Blazium sign-in. The play cookie is `SameSite=None` and `Partitioned`. The launch plays the build assigned to Telegram. That build cannot be priced, and the launch does not charge or grant a license. `connect-src` adds `api.blazium.online`, `login.blazium.online`, and `lobby.blazium.online`. There is no URL-mapping proxy. Threaded and WebGPU packs are refused. Adult listings and hidden pages are not offered. ## Other hosts Playables, Devvit, itch, Newgrounds, Yandex, CrazyGames, Poki, Meta Instant Games, and GameDistribution are checks on a browser pack. YouTube and those portals host the zip. Blazium does not submit it and does not call their ad or purchase APIs. A Playables pack cannot use `.br` or `.gz`, a threaded build, or WebGPU. Devvit files cannot contain an absolute URL. Meta accepts Instant Games SDK 8.0 for Facebook and Messenger. Instagram is not a launch. Facebook Web Games ended. A TikTok, Douyin, or WeChat pack is not played in the browser and is not a public download. The publisher downloads that zip from the Builds page. The Builds page also shows a host file URL for TikTok, Douyin, WeChat, YouTube, Reddit, Newgrounds, CrazyGames, Poki, Meta, and GameDistribution. That address returns the scanned zip. It is not the unlisted play link, it is not on the store page, and turning it off or rotating it makes the old address fail. Discord and Telegram do not get a file URL. Steam, GOG, Epic, and itch stay on Also on. Each build can record its own price. A demo cannot be priced. A web demo is the browser demo. Any other demo is the downloadable demo. Only one build is the demo. A build marked embeddable, or designated for a launch host, cannot be priced. A store shelf (Steam, GOG, Epic, or itch) says where else the file is published and can still have a Blazium price. One build holds each host. Assigning that host to a second build removes it from the first. Send `designations`, `for_sale`, `price_cents`, `is_demo`, and `embed_supported` with the upload, or set them later on the Builds page. A designation does not run an export check. TikTok, Douyin, and WeChat need that host's mini-game pack. Discord, Telegram, and the other launch hosts need a browser pack. The recorded price is not a separate buy button. The game is still bought at the listing price. ## Plays Plays are counted beside downloads, not inside them. A play is recorded when someone is offered a session. Later requests for the same session are not new plays. Time is how long the tab was visible. Project Analytics and account Analytics show plays for the last 30 days: total, unique players, anonymous plays, seconds, median session, and full versus demo.