Skip to main content
A game’s store page, uploads, publishing and releases. 22 operations. How to call them, and what the answers mean: Operations reference.
Generated from the summer-engine npm package 4.8.0: its public operation catalog (registry/operations/public-catalog.json) and its engine and local operations. If something here is wrong, the operation’s definition is wrong.

cancel_publish

store.cancel_publish: Withdraw a publish request Withdraw a publish request that still waits for the owner, so its approval link stops working. Nothing that is live changes. Next: store.publish for a new request. Inputs:
Example: Take back a publish request before the owner answers.

get_listing

store.get_listing: Read the store page Read a game’s store page as the store will show it: page state, visibility (public or private), targets, text per store, art per slot, price, the publish checklist (what is missing), publish requests and the tags a page can pick. Next: store.update_listing. Inputs:
Example: What does the store page still need?

go_live

store.go_live: Go live
Preview: search finds it and summer_call runs it. It may still change.
Take a store game live: release its checked Build, publish its page, watch until players get it or name the failing check and fix. Confirm-gated. Inputs:
Example: Go live

store.preview_link: Make a store preview link Make a private link to the saved store page draft on summer.games (not indexed; Buy and Play do nothing) to look at it or show it to someone. Expires after 1h, 1d or 7d. Returns the url. Inputs:
Example: A link to look at the draft page.

publish

store.publish: Publish the game Publish the store page with a build and price: live once the automatic checks pass, never waiting on staff. Publishes now (a job) when the person’s Agent permissions allow; else answers the owner’s approval link. Needs an idempotencyKey. Next: jobs.wait, then store.status. Inputs:
Example: Publish the game

release

store.release: Release a build Release a ready bundle build: uploadId, else the one the owner approved, else the newest ready one. Never waits on staff, except a build asking for internet access. Answers a job (jobs.wait). Needs an idempotencyKey. Web builds and downloads need no release. Inputs:
Example: Ship the newest ready build.

remove_build

store.remove_build: Remove a build Remove a bundle build that no environment serves from the game’s versions. Its version number stays used; a live build cannot be removed. Asks the person first. Next: store.status. Inputs:
Example: Remove a failed build from Versions.

remove_file

store.remove_file: Remove a file kept privately Remove a file that was kept privately (store.status files): it leaves the list, and no build uses it. Asks the person first. Next: store.status. Inputs:
Example: Remove an old file kept privately.

remove_trailer

store.remove_trailer: Remove the store trailer Take the trailer off the store page draft. The live page keeps its trailer until the draft is published. Asks the person first. Next: store.get_listing. Inputs:
Example: Drop the old trailer before a new one is ready.

set_art

store.set_art: Set store art Put images into one store art slot from the person’s assets (assetId) or public image URLs. Each is checked for the slot’s shape and size, then by Summer Games. Screenshots take a list; an empty list clears the slot. Next: store.get_listing. Inputs:
Example: Use a generated image as the key art.

set_bundles

store.set_bundles: Set store bundles Replace the store page draft’s bundles: Items (ids from store.get_listing itemStore.items) sold together for one Sparks price below their total. Bundles sell several Items together for one price; sales take a percentage off between two dates. A refusal names the field. Next: store.publish. Inputs:
Example: A sword and ten potions for 600 Sparks.

set_details

store.set_details: Set details
Preview: search finds it and summer_call runs it. It may still change.
Fill store page sections update_listing lacks: genres, features, credits, languages, requirements, content survey, AI disclosure. Never publishes. Inputs:
Example: Set details

set_sales

store.set_sales: Set store sales Replace the store page draft’s timed sales: 1-90% off one Item or bundle from startsAt until endsAt (at most 90 days). Bundles sell several Items together for one price; sales take a percentage off between two dates. A refusal names the field. Next: store.publish. Inputs:
Example: A week of 20% off the fire pack.

set_sound

store.set_sound: Set the store sound Set the soft loop visitors hear on the game’s summer.games page: a loop from the summer.games sound library (preset), the person’s audio asset, or a public MP3 or M4A URL; source null removes it. Next: store.get_listing. Inputs:
Example: Soft rain on the store page.

set_trailer

store.set_trailer: Set the store trailer Set the store page trailer from the person’s video asset or a public MP4 or WebM URL; Summer Games checks it first. Muted and looping at the top of the page. To remove it: store.remove_trailer. Next: store.get_listing. Inputs:
Example: Use a generated gameplay video as the trailer.

status

store.status: Check where a game stands Read where a game stands on Summer Games in one call: live or not, what the automatic checks found, Summer’s staff review after going live, a publish request waiting for the owner, every upload and its checks, and what players get now on each platform. Returns one next step. Inputs:
Example: Is the game live, and what do players get now?

update_listing

store.update_listing: Edit the store page Edit the store page draft: title, targets, desktop and mobile text, tags, long description, support, release stage, content rating, other languages; visibility (public or private) applies at once. Omitted fields keep their value; saving never publishes. Next: store.get_listing, then store.publish. Inputs:
Example: Set the tagline and tags.

update_release_notes

store.update_release_notes: Write release notes Write the release notes players read for a released bundle build: a title and Markdown text. Players see them at once once the release is live. Empty title and text take them down. Asks the owner first. Next: store.status. Inputs:
Example: Tell players what changed in the new build.

upload_begin

store.upload_begin: Start a store upload Start uploading a build to a game: kind bundle (the summer.games export or one .pck), web (an HTML5 zip with index.html) or download (a desktop archive). Returns uploadId and the part plan. Next: store.upload_sign_parts. Inputs:
Example: A web build that plays on summer.games.

upload_complete

store.upload_complete: Finish a store upload Finish a store upload after every part is PUT: Summer seals it and checks it. Answers a job while it checks (jobs.wait), or the finished status. Safe to call again. On a live game only the owner may finish a web build or download. Inputs:
Example: Finish a bundle upload and follow its checks.

upload_file

store.upload_file: Upload file Upload an export to the creator’s store game, confirm-gated: a bundle as a Build with its per-platform checks, or a web or native download. Inputs:
Example: Upload file

upload_sign_parts

store.upload_sign_parts: Sign upload parts Get upload URLs for parts of a store upload, up to 100 at a time. PUT each part to its URL with every returned header; sign again for a part that failed or expired. Bundle parts need their SHA-256. Next: store.upload_complete. Inputs:
Example: The URL for the one part of a small web build.