game_upload_ticket

Behavior#

For a client with a shell on the remote endpoint (Claude Code or Codex over HTTP): a signed ticket to upload one build folder from the creator's machine. Returns upload_base, slug, version, ticket (good for 3 hours and this one build; keep it out of anything else), rules (the size limits), upload_url (the site's upload page, where the creator uploads the folder in the browser) and, when the platform gives one (none while the Looping MCP package is unpublished), command: the upload with the Looping MCP package's CLI (looping-mcp publish <dir> --ticket …), which checks the folder, uploads every file straight to the games worker, publishes it as a new preview of the selected project and prints the version and preview_url.

Run command in your shell only where that CLI is installed on this machine; if it is not (the command cannot find the package), don't retry it or ask the creator to install anything: hand them upload_url. Give dir (the absolute build folder) and note to have them filled into the command. Over the stdio server use game_publish { dir } instead.

Input parameters#

The descriptions above include conditional requirements. The full schema below shows structural validation; runtime checks also apply.

JSON Schema#

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "dir": {
      "description": "the absolute build folder, filled into the command",
      "type": "string",
      "minLength": 1,
      "maxLength": 400
    },
    "note": {
      "description": "what changed in this build",
      "type": "string",
      "maxLength": 280
    }
  },
  "additionalProperties": false
}