How to integrate launcher with Steam

How it works

Cross-platform flow

You can integrate your game with launcher in Steam. It allows you to promote your other Steam games via Xsolla Launcher.

If your launcher is integrated into Steam, it is installed on the user’s computer as a separate application when Steam is launched for the first time. Subsequent launcher behavior depends on how it is launched:

• Via Steam:
  • The launcher only displays games for which the Steam AppID is specified in Publisher Account.
  • The Buy button leads to the game’s page in the Steam application.
  • The Install button initiates game installation through the Steam SDK in the Steam application.
  • The launcher redirects the user to Steam for in-game purchases.
  • If you have enabled the store in the launcher project settings for a specific game and provided its Steam AppID, the launcher will retrieve information about available DLCs for that game from Steam and create cards for these DLCs in the Xsolla Launcher store. When users click the Buy button, they are redirected to the items’ page in the Steam application.
  • Xsolla Login automatically creates a user account within the Xsolla ecosystem using the user’s data from Steam. This allows you to see all launcher users in the Publisher account in the Xsolla Login database. Users can use the same account when launching the launcher outside Steam and make in-game purchases through the Xsolla Launcher store. Therefore, even when launched from Steam, you can check the user’s ownership of items purchased through the Xsolla Launcher store using Xsolla API methods.
  • If the user clicks the Play button on a game other than the game through which the launcher was started, the launcher closes, and the selected game is started in Steam in the background. The launcher immediately starts the game without displaying the launcher UI. After the user closes the game, the launcher UI is displayed.

• As a standalone application through the launcher's executable file or its desktop shortcut:
  • The launcher displays all games added to the launcher project, regardless of whether their Steam AppID is specified.

• • The Xsolla Launcher store displays in-game items that have been added to it through Publisher Account.

• • The launcher has access to information about locally installed games through Steam. If a game distributed through Steam is locally installed, the Buy button is replaced with a Play button. When the user clicks the Play button, the launcher restarts through Steam.

Prerequisites

To set up Steam integration, you need:

• a Steam AppID
• an account and game in Steamworks
• a game build for publication on Steam
• a ready-to-use Launcher configured in Publisher Account

You can find your Steam AppID in your game administration panel in Steamworks. Go to the Steamworks > App Admin section and you will see it next to the name of your project.

Integration steps

Set up Steam platform and download files

1. Open your project in Publisher Account.
2. Click Launcher in the side menu.
3. Find the launcher on the dashboard, and click Edit launcher.
4. Go to the Settings section and click Set up to the right of the Steam platform logo.
5. Enter your Steam Web API Key.
6. Enter Steam App ID of your game.
7. Click Download launcher host to download the LauncherHost.zip archive for Windows or macOS.
8. Click Download config to download the game’s configuration files.
9. Go to the Launcher behavior tab and select what the launcher should do when a user runs the game from Steam (optional):
   • Run the launcher (default)
   • Run a game

10. Go to the User login tab and select a login method (optional):
    • Automatically via Steam account (default).
    • Manually via login widget. The widget uses the login project selected during launcher creation.

Generate and download launcher installer

Prepare the game build for Steam

1. Unpack the LauncherHost.zip archive (should be downloaded at step 1) to any directory. This archive contains the GameBuild directory for preparing the game with a launcher to be uploaded to Steam. Folder structure for Windows:
   • LauncherHost.exe — an executable file for the LauncherHost utility
   • Qt5Core.dll, vcruntime140-140_1.dll, msvcp140-140_1.dll — service libraries for the LauncherHost.exe utility
   • installer — a folder for the launcher installer

1. Folder structure for MacOS:
   • LauncherHost — a executable file for LauncherHost utility
   • Frameworks — a system folder for the LauncherHost utility libs
   • installer — a folder for the launcher installer

2. Create a new folder in the GameBuild folder.
3. Copy and paste your game build into that folder.
4. Set up the game executable file name (Windows / macOS) in the Game > Build > Executable files section and specify the relative path to the game executable file.

5. Copy and paste a stand-alone launcher installer (Windows / macOS) to the installer folder.
6. Copy and paste the Steam configuration files in the GameBuild folder.
7. If you already have your game on Steam, replace the LauncherHost.exe file name with the name of your game’s executable file. You can find this information in your game administration panel in the Executable field of the Apps & Packages > All applications > Steamworks admin > Installation > General installation section.

8. Enable using ISteamApps::GetLaunchCommandLine() in your game administration panel.

9. Click Prepare for Publishing to check if there are any conflicts between your work and that of other users.

Upload Windows game build files to Steam

1. Log in to Steamworks and download the Steamworks SDK.
2. Unpack the SDK archive.

3. Go to the steamworks_sdk_151\sdk\tools folder and unpack the SteamPipeGUI utility for uploading game builds to Steam.

4. Run the SteamPipeGUI utility.

5. Fill out the following fields in the settings window:
   1. In the App ID field, specify your game’s Steam AppID.
   2. In the Build description field, enter a short description of this build to make it easier to identify in your Steam admin panel.
   3. In the Steamworks SDK ContentBuilder Path field, specify the path to the Steamworks SDK ContentBuilder.
   4. In the Steam Login and Steam Password fields, enter your Steamworks login and password.

5. 5. Click Add Depot. In the Build Path field, specify the path to GameBuild with the game build and the Launcher installer.

5. 6. Click Upload and wait for the uploading to finish.

Upload macOS game build files to Steam

1. Copy and paste launcher.dmg in the GameBuild/installer.
2. Copy and paste hostArgs.json in the GameBuild folder.
3. Upload files to Steam:
   1. Open the unpacked SteamSDK folder.

5. 2. Go to the tools/scripts folder.
   3. Create a vdf script named app_build_<steam_id>.vdf, where <steam_id> is your project’s Steam ID and the following content (replace xxxxxx in line 3 with Steam ID, yyyyyy in line 11 with Depot ID - this is Steam ID + 1:

	"AppID" "xxxxxx" // your AppID
	"Desc" "This is a simple build script 1" // internal description for this build

	"ContentRoot" "../content/" // root content folder, relative to location of this file
	"BuildOutput" "../output/" // build output folder for build logs and build cache files

	"Depots"
	{
		"yyyyyy" // your DepotID
		{
			"FileMapping"
			{
				"LocalPath" "*" // all files from contentroot folder
				"DepotPath" "." // mapped into the root of the depot
				"recursive" "1" // include all subfolders
			}
		}
	}
}

5. 4. Save changes.
   5. Copy the contents of the GameBuild directory and paste them into the tools/ContentBuilder/Content folder.
   6. In the terminal console, go to the tools/ContentBuilder/builder_osx folder.
   7. Call the ./steamcmd.sh command to start initialization and configuration.
   8. Call the following command to run the script that uploads the build to the Steam servers:

cmd.sh +login <username> <password> +run_app_build_http ../scripts/app_build_{Steam_id}.vdf

Publish game build on Steamworks

1. Go to your game administration panel in Steamworks.
2. Click Steamworks Admin to open the application admin page.

3. Go to the SteamPipes > Builds section.

4. Create a new branch or use a default branch.
5. Find the uploaded build by its build ID, uploading date, or description, and place the build in your branch.
6. Click Preview change and view your changes.
7. Click Set Build Live Now.