Skip to main content

​
Upload a build

The upload workflow scans a packaged game directory, computes file hashes, transfers the required files, and creates a release.

​
Before uploading

Confirm:
  • The packaged build starts locally.
  • The executable path matches the game configuration.
  • The folder contains runtime files only.
  • The version has not already been used.
  • You have permission to publish to the selected game and branch.
  • Your workspace has enough storage and bandwidth capacity.

​
Guided workflow

1

Select Upload a build

Start from the CLI main menu.
2

Select workspace and game

Choose from the resources available to the authenticated account.
3

Select the branch

Confirm whether the release belongs to stable, beta, testing, or a private channel.
4

Enter version and release type

Provide the version and select STABLE, PATCH, or HOTFIX.
5

Enter the changelog

Describe the player-visible changes.
6

Select the build folder

Choose the root directory of the packaged game.
7

Review and confirm

Verify every value before transfer begins.

​
File scanning and deduplication

LauncherForge calculates SHA-256 hashes to identify file content.
  • A STABLE release uploads the complete build as a new full baseline.
  • PATCH and HOTFIX releases use the manifest and hashes to transfer the files required for the new version.
  • Unchanged content can be reused when the platform already has the matching file.
Renaming or rebuilding files can change their hashes even when the visible game content appears similar.

​
During the upload

Keep the terminal open and maintain a stable network connection. Do not move or modify the selected build folder while it is being scanned or uploaded.

​
After the upload

Use View upload status and List versions, then verify the release in the dashboard and test it from the launcher.