Launch Fallbacks

When a registered executable cannot be launched directly (for example because a game uses a separate launcher), applanch can automatically redirect the launch through the correct launcher instead.

Built-in fallback rules are in Config/launch-fallbacks.json. Custom rules should be added under Config/UserDefined/launch-fallbacks/*.json.

Built-in Rules

Enabled by Default

Rule	Trigger	Method	App ID Source
Riot VALORANT	Always	Launches via RiotClientServices.exe	—
Riot League of Legends	Always	Launches via RiotClientServices.exe	—
Steam library executable	Always	Launches via steam://rungameid/{appId} URI	steam-manifest

Samples (Disabled by Default)

The following rules are included as examples. Enable them and replace placeholder values to use them.

Rule	Launcher	URI Template
Epic Games sample	Epic Games Launcher	com.epicgames.launcher://apps/{appId}?action=launch&silent=true
Ubisoft Connect sample	Ubisoft Connect	uplay://launch/{appId}/0
EA app sample	EA app	ea://launchgame/{appId}
Battle.net sample	Battle.net	battlenet://{appId}

Adding a Custom Rule

To add a rule for a game launcher not covered by the built-in entries:

1. Create a JSON file under Config/UserDefined/launch-fallbacks/ (for example ubisoft.json).
2. Add your rule(s) under the rules array.
3. Set "enabled": true for active rules.
4. Fill in the appropriate matchFileNames and template fields.
5. Restart applanch.

Example — Ubisoft Connect (enabled):

{
  "rules": [
    {
      "name": "My Ubisoft Game",
      "kind": "uri-template",
      "enabled": true,
      "matchFileNames": ["MyGame.exe"],
      "uriTemplate": "uplay://launch/{appId}/0",
      "appIdSource": "registry:HKEY_LOCAL_MACHINE:SOFTWARE\\WOW6432Node\\Ubisoft\\Launcher\\Installs\\12345:UplayId"
    }
  ]
}

Replace 12345 with the registry key for your specific game.

For a full reference of all rule fields, template placeholders, and App ID sources, see Launch Fallback Format.