The Steam (steamcmd) destination uploads your staged build to a Steam depot using steamcmd. Build & Ship generates a minimal app_build script for you and runs steamcmd with it.
Setup
- Download steamcmd and point the destination’s SteamCMD Path at the executable.
- Enter your App ID and Depot ID (from Steamworks → App Admin → Depots) and your build account’s Username. App ID and Depot ID must be numeric.
- Steam Guard: run
steamcmd +login <user>once manually and enter the Guard code. steamcmd caches the session, so you can then leave the Password empty in the profile. This is the recommended setup and avoids Steam Guard prompts in automated runs.
Branches
Leave the Branch field empty to only upload the build without setting it live. Setting the default branch live is not possible via steamcmd — do that in the Steamworks web UI. Any other branch name is set live automatically (via SetLive). The destination refuses public/default as a branch name for exactly this reason.
Credentials & security
If you do store a password it is saved AES-256 encrypted inside the profile asset and is never written to any log — the steamcmd argument line and all process output are redacted. For unattended builds we still recommend cached steamcmd credentials over a stored password.
Build & Ship writes a minimal app_build script into Library/BuildAndShip/ that maps the staged build (*, recursive) into your depot, then runs steamcmd +login <user> +run_app_build <script> +quit. On success the log links to your app’s Steamworks builds page.
