Version-aware launcher
The launcher can compare the installed state with the release assigned to the selected game branch.
Game auto updater
Keep player installations aligned with your latest game release.
LauncherForge connects versioned publishing with launcher-side update checks so players can move from an installed build to the release assigned to their current branch.
- ✓Launcher-side update checks
- ✓Version and branch awareness
- ✓Release history for teams
Automatic Delivery
LauncherForge
Updates should follow your release state, not a manual checklist.
The launcher needs to know which game, branch and release the player should run. LauncherForge keeps those concepts explicit so update decisions are tied to versioned publishing.
Automatic game updates
Updates should follow your release state, not a manual checklist.
The launcher needs to know which game, branch and release the player should run. LauncherForge keeps those concepts explicit so update decisions are tied to versioned publishing.
Branch-specific updates
Production users, private testers and internal teams can follow different release branches without needing separate launcher products.
Manifest-driven delivery
Published build metadata and file manifests provide the release state required for the launcher update workflow.
Patch notes and release context
Keep player-facing release information close to the update that delivers the new game version.
Repeatable publishing
Use the CLI workflow to make the source release deterministic before the launcher ever checks for an update.
No marketplace dependency
Operate a branded launcher and update channel for communities, private testers or direct distribution workflows you control.
Update lifecycle
Publish once, resolve the correct release at launch time.
The updater follows the release model your team defines instead of requiring developers to manually distribute replacement folders.
- 01PUBLISH
Publish the next game version.
Create the versioned release from the packaged build and target the intended branch.
- 02CHECK
The launcher checks release state.
When the player opens the launcher, it resolves the current release for that game and branch.
- 03SYNC
Bring the local installation forward.
The update workflow uses the published manifest and stored objects needed by the target release.
- 04PLAY
Launch the expected version.
Once the installation is current, the launcher starts the game through the normal player-access flow.
Release state
Make “latest version” an explicit branch decision.
Production, beta and internal users do not always need the same build. Branch-aware publishing lets the launcher resolve the right version for each audience.
Update check
game: Project North
branch: production
installed: 0.9.4
available: 0.9.5
manifest resolved
installation updated ✓
Build the complete updater stack
Connect updates to the patch pipeline and launcher experience.
Automatic update checks become more useful when releases are versioned and each player is mapped to the right branch.
Game auto updater FAQ
Questions about launcher-driven game updates.
The updater works on top of LauncherForge releases, manifests and branch state.
Can production and beta users receive different versions?+
Yes. Different branches can point to different releases, allowing production and private testing audiences to move independently.
Does the launcher know which version is installed?+
The launcher update flow is built around comparing local installation state with the release assigned to the selected game and branch.
Do I need a separate launcher for every testing channel?+
No. Branches are intended to keep release channels separate while still operating within the same branded launcher ecosystem.
Can patch notes be shown with updates?+
LauncherForge supports release-facing content such as patch notes and news so players can understand what changed around a new version.
Is the updater tied to Unreal or Unity?+
No. File distribution and release state are engine independent. Engine integrations are used where runtime authentication or engine-specific setup is required.
// Reduce release friction
Make the launcher the reliable entry point to the current game build.
Keep versions, branches and update checks connected so players spend less time figuring out which build they should install.