Skip to main content

​
Publish your first build

Launcher Forge publishes game builds through an interactive CLI. You do not need to write a deployment command or remember command-line flags. The CLI guides you through the entire process using menus and prompts.
Publishing a game in the Catalog only makes its game entry visible in the launcher. It does not upload the game files. You must publish at least one build through the CLI before players can install and run the game.

​
Before you begin

Confirm that:
  • The game exists in the Catalog.
  • The game status is Published.
  • The game has at least one branch.
  • CLI access is enabled.
  • You have a packaged build that runs correctly.
  • Your account has permission to publish builds.
  • Your workspace has enough storage available.
  • You know which executable starts the game.
Accounts created through Google or GitHub may need to create a Launcher Forge password before signing in to the CLI with email and password.

​
1. Open the CLI section

Sign in to the Launcher Forge dashboard. In the left sidebar, select CLI. Launcher Forge displays the games available for publishing. Select the game card or use Open CLI.
Launcher Forge CLI page with the game card and Open CLI option highlighted

Open the CLI section and select the game

The CLI only retrieves games and permissions available to the authenticated account.

​
2. Download the CLI executable

The game-specific CLI page shows:
  • Application ID.
  • Number of branches.
  • Default branch.
  • CLI access status.
  • Executable version.
  • Download size.
Select Download CLI.
Launcher Forge game CLI page with the Download CLI button highlighted

Download the Launcher Forge CLI executable

The downloaded file is a ready-to-run Windows executable. You do not need to install it. You can:
  1. Save it on your desktop or another folder.
  2. Double-click the executable.
  3. Start using the CLI immediately.
Download the CLI only from the official Launcher Forge dashboard. Do not run copies received from unknown sources.

​
3. Sign in

When no active session exists, the CLI displays:
Enter the email address associated with your Launcher Forge developer account. The CLI then requests your password.
Launcher Forge CLI requesting the developer account email

Sign in with your Launcher Forge email and password

Signing in to the dashboard does not automatically sign in to the CLI. The CLI keeps its own local session.
After a successful login, the CLI displays:
  • Account email.
  • Active plan.
  • Account status.
  • Storage usage.
  • Bandwidth usage.
  • Number of games allowed and currently created.

​
4. Select Upload build

The main menu contains the available interactive actions. Select Upload build.
Launcher Forge CLI main menu with Upload build selected

Select Upload build from the interactive menu

The menu can also include:
  • Account / usage.
  • List games.
  • List versions.
  • Version info.
  • Logout.
  • Exit.

​
5. Select the game

The CLI loads the games available to your account. Select the game you want to publish. The game is displayed with its Application ID.
Launcher Forge CLI game selection showing the game name and Application ID

Select the game that will receive the build

​
6. Select the branch

After selecting the game, the CLI loads its available branches. Select the destination branch.
Launcher Forge CLI branch selection with the main branch available

Select the destination branch

Common examples include:
  • main
  • stable
  • beta
  • development
  • An authorized private branch
Review the selected branch carefully. Publishing a test build to a production branch can expose it to players.

​
7. Enter the version and release type

Enter a new version number. A semantic version format is recommended:
Examples:
Do not reuse a version that already exists for the selected game and branch. The CLI then asks for the release type.
Launcher Forge CLI version number and STABLE, PATCH, or HOTFIX selection

Enter the version and select the release type

Publishes a complete new version of the game.All files are uploaded, even when some files already exist.

​
8. Add release notes and select the build folder

Enter optional release notes or a changelog. Write a short player-facing description. Example:
The CLI then requests the path to the packaged game folder.
Launcher Forge CLI release notes and packaged game folder path

Enter release notes and the packaged game folder path

Select the root folder containing the packaged game files. Example:
Do not select:
  • The Unreal Engine or Unity project folder.
  • Source code.
  • Editor cache.
  • Intermediate files.
  • Temporary build files.
  • Folders containing credentials.
Do not move, rename, or modify the selected folder while the CLI is scanning or uploading it.

​
9. Confirm the main executable

Launcher Forge scans the selected folder and generates the manifest. The CLI reports:
  • Number of files.
  • Number of unique hashes.
  • Detected executables.
When one or more executables are found, select the main game executable. Launcher Forge can mark one option as Recommended.
Launcher Forge CLI showing the generated manifest and recommended main executable

Confirm the main game executable detected by the CLI

The selected executable is the file Launcher Forge will use to start the installed game.
Confirm this value carefully. Selecting the wrong executable can allow the game to install correctly while preventing it from starting.

​
10. Wait for the upload

Before transferring files, the CLI displays the release mode and estimated upload. For a STABLE release, Launcher Forge forces a complete upload of the packaged version. The CLI then uploads the files and displays the current progress.
Launcher Forge CLI uploading the files of a STABLE release

Wait while the game files are uploaded

Keep the CLI open and maintain a stable internet connection until the operation finishes.

​
11. Confirm the successful publication

When the process completes, the CLI confirms:
  • Build created successfully.
  • Version number.
  • Release type.
  • Destination branch.
  • Main executable.
  • Successful upload.
Launcher Forge CLI confirming a successfully published STABLE build

Confirm that the build was published successfully

Press Enter to return to the main menu.
Your first game build has been published successfully.

​
What happens after publishing?

After the build is published:
  • The version appears in Launcher Forge.
  • The release belongs to the selected branch.
  • The launcher can use the selected main executable.
  • Players can download or update the game when the release is available to them.
Review:
  • Version number.
  • Branch.
  • Release type.
  • Release notes.
  • Main executable.
  • Build status.
  • Installation and game startup from the launcher.

​
If the upload fails

The CLI displays the cause and should return to a usable menu instead of closing unexpectedly. Common causes include:
  • Invalid or expired session.
  • Missing game or branch permission.
  • Duplicate version.
  • Invalid packaged folder.
  • Storage limit reached.
  • Network interruption.
  • No executable detected.
  • Files changed while the upload was running.
Correct the reported cause before retrying.

​
Next step

Continue with Test your launcher.