Skip to main content
A game’s items: propose or sync the item plan for the owner’s approval. 2 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.

propose_items

economy.propose_items: Propose item changes to the owner
Preview: search finds it and summer_call runs it. It may still change.
Send a game’s item plan (items by item key) to its owner. Answers needs_approval with a link; on Approve, Studio creates or revises each item, sets its price and submits it for Summer’s review. Never publishes. At most 50 items. Inputs:
Example: Ask the owner to add a new emote for 150 Sparks.

sync_items

economy.sync_items: Sync items
Preview: search finds it and summer_call runs it. It may still change.
Sync summer.items.json to the store game by item slug - a plan, then the owner’s approval in Studio. Needs the store sign-in (summer login —store). Inputs:
Example: Sync items