What it is
A handoff layer between your GDD and partner.steamgames.com. Valve exposes no write API for achievements, store pages or item definitions, so this produces the exact files their partner site imports rather than pushing on your behalf. Builds are the one exception:
GetAppBuilds and SetAppBuildLive are real API calls, so build history is read live and you can promote a build to a branch from here. Requires a Pro or Team plan.When to use it
- Setting up a Steam page and refusing to retype the GDD into Steamworks by hand.
- Shipping achievements you already designed in the Achievements module.
- Publishing items designed in Items & Objects to the Steam Inventory Service.
- Translating store copy once in Localization and exporting it for every Steam language.
- Checking which build is live on which branch without leaving the GDD.
How to use it
- 1Enter your Steam App ID, then add a publisher API key (project owner only).
- 2Run Seed — it copies store and achievement text into Localization under `steam.*` keys and assigns permanent achievement API names and item IDs.
- 3Translate those `steam.*` strings in the Localization module, using AI translate if you like.
- 4Download the exports: achievements (.vdf), item definitions (.json), store page localization (.json).
- 5Upload each in the matching Steamworks section — Stats & Achievements, Steam Inventory Service, Store Presence → Localization.
Tips you should know
- →Achievement API names and Steam item IDs are permanent once players earn or own things — Seed assigns them one time and never reissues, even after you delete an item.
- →Emoji achievement icons do not transfer; Steam needs 64×64 images. The export lists the exact filenames to upload.
- →Items always export as tradable:false and marketable:false — those have real-money consequences, so opt in deliberately inside Steamworks.
- →Item icons must be public HTTPS URLs. Older projects with bare filenames from the Asset Engine era are reported rather than exported broken.
- →Publishing a build to the default branch reaches every owner immediately, so it asks you to type the branch name to confirm.
- →Your publisher key is encrypted with AES-256-GCM before storage and never sent back to the browser.