Update the game live in the Playgama catalog
send_playgama_catalog_updateSend this archive and the saved form to the Playgama catalog as an update of the game live there, without moderation: once it is published, every catalog player gets it and no moderator checks it first. Write updateNote — what players will notice in this update — every time; a refused note writes nothing: fix it and call again. Call it only on the developer’s explicit yes in this conversation: first tell them the game, the archive and that the game live in the Playgama catalog will be updated for all its players with no moderation; a yes to an earlier update or to a sandbox publish does not count. Before asking, read get_submission_state with this archiveId and reviewType AUTO: it says whether this call would be refused, in the same words. Only a game live in the catalog takes it (autoReviewPlatforms holds PLAYGAMA); a first publication and every other platform go to moderation, which a human submits in the console. Answers outcome PENDING and releaseId: follow that PLAYGAMA publication in get_publications, read before the call too. On FAILED players keep the previous build. Until it ends, another publication of the game, to the catalog or the sandbox, is refused with 409 PUBLICATION_IN_PROGRESS. Never call again on an old yes: the form goes as it is when the call goes in, so another call is a new update, after get_submission_state and a new yes. Refusals (reason): AUTO_REVIEW_UNAVAILABLE — not live in the catalog; NO_CHANGES — the archive and the form are those of the last submit; PUBLICATION_IN_PROGRESS; and every reason get_submission_state names.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"applicationId": "<applicationId>",
"archiveId": "<archiveId>",
"updateNote": "<updateNote>"
},
"name": "send_playgama_catalog_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| archiveId | Yes | The archive to send: one of this game whose build check PASSED (get_archive_status `state`), the one get_submission_state judged with `reviewType` AUTO. Its form goes with it, as saved | |
| updateNote | Yes | What a returning player will notice in this build, 80 to 500 characters, 1 to 4 sentences. Not a changelog: pick the one or two changes a player would actually feel (a new level, controls that work differently, a boss that got easier) and say them the way you’d tell a friend who played last week. Skip refactors, build settings and fixes nobody could see. If it fixes something players complained about, say so. Required: this update replaces the build every catalog player has now. It is kept with this release. Write it in the voice `story` of update_application_form describes. Non-Latin letters and links are refused. Here the note cannot be left out: fix a refused one and send it again. | |
| applicationId | Yes | Game id from list_applications |