Desktop updates

Desktop game updates

Publish signed desktop updates or let the store update its installation.

Source: module-kits:wrappers/launcher/usage/en.mdView Markdown source

Also read offline — CLI: grip-forge docs desktop-launcherMCP tool: gripforge_docs { "topic": "desktop-launcher" }

The launcher starts your compiled game on Windows and macOS. Direct installations offer signed updates in a native dialog; store installations use the store updater, including offline mode.

Prepare the launcher and game with the site CLI’s game-release prepare command. Package and sign on the target platform, then use finalize, publish and promote. Supply an Ed25519 key for direct distribution, or your app and depot identifiers for store distribution. Keep private keys and store credentials outside the game folder.

Stable is the default channel. Start the installed launcher with --update-channel beta to opt into beta releases; use --update-channel stable to return. A newer beta is never automatically downgraded.

The game receives GRIPFORGE_SAVE_DIR outside its installation. Your engine must use that directory for saves. Existing saves and cloud synchronization need their own configuration.

Updates download while you play and install after the game closes. An interrupted download leaves the installed version playable and can be attempted on the next launch. Version 0.1.0 transfers full packages; it does not migrate saves, rotate signing keys or implement store achievements. The configuration schema is gripforge.launcher/1.