Skip to content

Destinations

James edited this page Sep 28, 2025 · 10 revisions

Destinations are where you send your build after the sources have been saved locally and modified using modifiers.

Destinations

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.

GithubNewRelease

Create a new release on a specific Github repository.

  • 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.

Itchio

Upload a file or folder for a game.

  • Channels: Which platforms to upload to (lower case). eg: windows,mac,linux,android.
  • Game: ID of the game as seen in the URL.
  • User: Account that owns owns the game.

LocalPathDestination

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.

NowhereDestination

Does not move the files anywhere. Useful for testing sources and modifiers.

Steamworks

Uploads files to Steamworks

  • App: Which Steam App to upload to. eg: 1141030
  • Branch: Which Branch to upload to. eg: internal-testing
  • Depot: Which Depot to upload to. eg: 1141031
  • Create AppFile: If true, a new App File is creating to upload the build to Steam.
  • AppFile: 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.
  • Create DepotFile: If true, a new Depot File is creating to upload the build to Steam.
  • DepotFile: If Create DepotFile is false then use a file with this name that will be found in the SteamSDKs path to upload a build to Steam.
  • Upload to Steam: If true, the build will be uploaded to Steam. Otherwise will still attempt to login. Good for testing if you can login correctly.

Clone this wiki locally