-
-
Notifications
You must be signed in to change notification settings - Fork 12
Destinations
James edited this page Aug 15, 2026
·
10 revisions
Destinations are where you send your build after the sources have been saved locally and modified using modifiers.
Specify where you want to upload your build. All destinations are executed at the same time.
- Enabled: When on, this destination will upload all content of the source files.
Upload an .ipa to App Store Connect / TestFlight via xcrun altool.
- API Key: Which App Store Connect API Key to authenticate with.
- App: Which App Store Connect app receives the upload.
- Build Version: CFBundleShortVersionString to match when polling App Store Connect for the uploaded build. Defaults to {version}.
- Build Number: CFBundleVersion (numeric build number) to match when polling App Store Connect for the uploaded build. Defaults to {buildNumber}.
- Find Build Timeout (seconds): How long to wait for the uploaded build to appear in App Store Connect after altool completes. Apple's processing pipeline can take several minutes; 600 (10 minutes) is the default.
Upload to a folder on Dropbox.
- App: Which Dropbox App to upload to.
- Folder: Which Dropbox folder to upload to. Leave unset to upload to the root.
- File Name: Name the uploaded file will appear as on Dropbox. Supports {keys} like {version}, {buildTarget} and {time}.
- Zip Contents: When uploading a folder: if true, the folder is zipped and uploaded as a single file. If false, each top-level file is uploaded individually.
- Create Shared Link: When true, a public shared link is created for the uploaded file and exposed via {dropboxShareLink}.
Upload an artifact to Epic Games.
- Organization: Use the Organization string that was provided along with your credentials.
- ProductID: Use the Product/Game string that was provided along with your credentials.
- Artifact: Specify the Artifact string that was provided along with your credentials.
- Cloud Directory Override: Optional: Directory where BuildPatchTool can save files to be uploaded, this can be empty each run. As with the BuildRoot, this can be an absolute or a relative path. (This location is used to cache information about existing binaries, and should be a different directory from the BuildRoot parameter. It is OK if this directory is initially empty; BuildPatchTool will download information as needed from the Epic backend and store it in the CloudDir.)
- BuildVersion: The version string for the build. This needs to be unique for each build of a specific artifact, independent of platform. For example, BuildVersion-1.0 can only exists for Windows or Mac, not both. The build version string has the following restrictions: Must be between 1 and 100 chars in length, whitespace is not allowed, should only contain characters from the following sets a-z, A-Z, 0-9, or .+-_
- AppLaunch: The path to the app executable that should be launched when running your game, relative to (and inside of) the BuildRoot. For Mac binaries, this should be the executable file contained within the .app folder, usually in the location Game.app/Contents/MacOS/Game.
- AppArgs: The commandline to send to the app on launch. This can be set to “” when no additional arguments are needed.
Create a new release on a specific Github repository.
- Description Format: What description to appear on the package.
- Draft: If true, the release will not be published but be editable on github.
- Owner: The owner of the repository.
- Prerelease: If true, marks the release as pre-release.
- Release Name: The name of the release that appears on Github.
- Repo: The name of the repository.
- Tag Name: The tag that is attached to this release. eg: v1.0.0
- Target: Branch name or commit hash to attach to the release. eg: main
- ZipContents: Each file is uploaded individually to Github as a separate download. If true, all files will be sent as a single compressed file instead.
Upload a build to Google Drive.
- App: Which Google App to use to upload.
- Folder: Which Google Drive folder to upload to. Leave unset to upload to the root of My Drive.
- File Name: Name the uploaded file will appear as on Drive. Supports string formatting like {version}, {buildTarget} and {time}.
- Zip Contents: When uploading a folder: if true, the folder is zipped and uploaded as a single file. If false, each top-level file is uploaded individually.
Upload an Android bundle/APK to Google Play with track rolling optional.
- App: Which Google App to use to upload to to (must include the androidpublisher scope).
- Play App: Which Google Play application to publish to.
-
Track: Which release track receives the upload.
- Internal
- Alpha
- Beta
- Production
- Release Status: Status of the release on the track. 'completed' rolls out immediately; 'draft' stages it for manual rollout.
- Release Name: Optional release name shown in the Play Console. Supports string formatting like {version}.
- Release Notes: Optional release notes (en-US). Supports string formatting like {version}.
- Binary File Name: When the source is a folder, the file name to upload. eg: 'game.aab'. Leave empty to auto-detect a single .aab or .apk in the source folder.
Upload a file or folder for a game.
- Channels: Which platforms to upload to (lower case). eg: windows,mac,linux,android.
- Description Format: What description to appear on Itchio attached to the build. Typically short and listed as the version eg: 'v1.0.0'
- Game: ID of the game as seen in the URL.
- User: Account that owns owns the game.
Copy the build to a location on your local pc.
- Directory: The absolute path of the folder to copy the files to. eg: C:/MyBuilds/TodaysBuild
See docs for formatting options like {version} and {time} to use in the path.
-
Duplicate Files: When copying files over and there already being the same file, what should we do with the new file?
- Error
- Skip
- Overwrite
- Name: If Zip Content is true, This is the name of the zipped file.
- Zip Content: If true, the content will be zipped into a single file.
Uploads files to the Nintendo Developer Center
- Title: Which Nintendo Title to upload to.
- Branch: Which Branch / release ring to upload to. eg: internal
- Description Format: Build description that appears in the Nintendo Developer Center.
Does not move the files anywhere. Useful for testing sources and modifiers.
Uploads files to PlayStation Partners via the local PlayStation SDK publishing tool
- Title: Which PlayStation Title to upload to.
- Branch: Which Branch / release ring to upload to. eg: internal
- Description Format: Build description that appears in PlayStation Partners.
Uploads files to Steamworks
- App: Which Steam App to upload to. eg: 1141030
- Branch: Which Branch to upload to. eg: internal
- Depots: Which Depots to upload to. eg: 1141031
- Create AppFile: If true, a new App File is creating to upload the build to Steam.
- AppFile Path: If Create AppFile is false then use a file with this name that will be found in the SteamSDKs path to upload a build to Steam.
- Overwrite AppFile Description: If Create AppFile is false and this is true, the the chosen appFile will be copied and description changed to fit selected Build Uploader description.
- Description Format: What description to upload to steam to appear on steamworks.
Upload a game package to Microsoft Partner Center via the Store Submission API.
- App: The Xbox app entry whose credentials will be used for this submission.
- WaitForCertification: Wait for a submission status after committing and log the result. Adds extra time but confirms the submission was accepted.
- RemoveFailedPendingSubmission: Delete the current pending submission if there is one before creating a new submission. Checks on xbox if there is a pending submission and deletes it before we start a new submission.