Skip to main content
Your games on Summer Games, and who works on them. 9 operations. How to call them, and what the answers mean: Operations reference.
Generated from the operation catalog: src/lib/ops/public-catalog.json in publicsummerengine at 0d85f61e2b and the summer-engine npm package 4.0.0 for engine and local operations. If something here is wrong, the operation’s definition is wrong.

create

games.create: Create a game Create a game on Summer Games with its first store page draft; nothing is published. Include web in targets so it can play in the browser. Returns the game id. Next: store.update_listing, store.set_art, store.upload_begin. Inputs:
Example: A new game that plays in the browser and on Mac.

get

games.get: Read a game Read one of the person’s games on Summer Games: name, store address, status, targets, tagline and when it changed. Next: store.status for review, uploads and releases, or store.get_listing for the page. Inputs:
Example: What is this game called and where is its page?

invite_member

games.invite_member: Invite someone to a game Invite someone by email to work on a game, with a role; Summer emails them a link. Runs when the person allows Contact people (off by default); otherwise answers needs_approval with a link and sends nothing. Inputs:
Example: Invite Sam as a developer.

leave

games.leave: Leave a game Leave a game the person works on, so they lose access to it; the owner cannot leave. Runs when the person allows Delete for good (off by default); otherwise answers needs_approval with a link. Inputs:
Example: Leave this game.

list

games.list: List my games List the person’s games on Summer Games: game id, name, status, targets and store link, newest change first. Next: store.get_listing or analytics.summary with a gameId. Inputs:
Example: Which games does this person have?

members

games.members: List a game’s members The people on one game on Summer Games: members and their roles, pending invites, the person’s own role and whether they may manage members. Next: games.invite_member or games.set_member_role. Inputs:
Example: Who works on this game?

remove_member

games.remove_member: Remove a member from a game Remove a member from a game, so they lose access to it. Runs when the person allows Delete for good (off by default); otherwise answers needs_approval with a link and changes nothing. Inputs:
Example: Take this member off the game.

set_member_role

games.set_member_role: Change a member’s role Change what a member may do on a game (admin, developer or viewer). Runs when the person allows Prices and live changes; otherwise answers needs_approval with a link. Next: games.members. Inputs:
Example: Make this member an admin.

withdraw_invite

games.withdraw_invite: Withdraw a game invite Withdraw a pending invite to a game, so its link stops working. Runs when the person allows Delete for good (off by default); otherwise answers needs_approval with a link and changes nothing. Inputs:
Example: Cancel the pending invite.