A destination is somewhere a finished build is shipped to — a store, a web server, a chat announcement or a local archive. A profile can combine any number of them. They all consume the same staged copy of the build (with Unity’s DoNotShip folders already removed) and run sequentially, one after another, so parallel uploads never saturate your bandwidth or interleave the log.
Available destinations
- itch.io (butler): pushes the build to an itch.io channel via butler.
- Steam (steamcmd): uploads the build to a Steam depot via steamcmd.
- FTP / Web Server: uploads the build to a web server via FTP(S) — ideal for WebGL.
- Discord & Slack: posts a release announcement via webhook.
- Zip Archive: zips the staged build next to the output folder.
Adding and ordering destinations
Click + Add in the Destinations section of a profile and pick a type. Each destination has a foldout with its own settings, an enable toggle, and a colored status dot that turns green when the configuration is valid. Use the ▲/▼ buttons to reorder them — a typical order is to upload to the store first and post the chat announcement last, so it only fires once the build is live.
If a destination fails
A failing destination does not roll back the ones that already succeeded, and it does not force a rebuild. Fix the problem and use Ship last build in the window to re-ship the staged output of the previous build without building again.
