Epic Games Launcher Invites

Facilitate game invites by linking Epic Games Store artifacts to Epic Online Services deployments.

1 min to read


To promote an optimal player experience, the Epic Games Store supports session invites from Epic Online Services (EOS) integrated games via an explicit opt-in system. This allows users from outside the store ecosystem to invite Epic Games Store users to their game session.

This functionality is facilitated by mapping your deployments to your Epic Games Store artifacts. In the context of the Epic Games Store, an artifact represents your product's downloadable content, such as game clients. By mapping deployments to your artifacts, EOS-initiated invites are routed through the Epic Games Store ecosystem to users in the Epic Games Launcher.

Leveraging your artifacts to expose game invites on the Epic Games Launcher requires use of the EOS SDK 1.11 or higher.

Mapping Artifacts to Deployments

To map your artifacts to deployments, follow the steps below.

  1. In the Dev Portal, navigate to Your Product > Product Settings and select the Sandboxes tab.
  2. Locate the appropriate sandbox to work in and click Deployments.
  3. Next to the appropriate deployment, click the menu (...) icon and choose Link Artifacts.
  4. Select each artifact you wish to link with the specific deployment. Then, use the grip icon to arrange the artifacts in priority order.
    • Note: When multiple artifacts are mapped to a single deployment, the Launcher routes the game invite to the first locally-installed artifact it finds following the priority order specified.

Additional Notes

  • Your production artifact should always be mapped to your Live deployment to ensure that invites are deliverable to your users in the Epic Games Store.
  • Do not map DLC artifacts to a deployment. Only base game launchable artifacts should be mapped to deployments.
  • While numerous artifacts may be displayed in Dev Portal, enabling internal test artifacts along with the production artifact should not result in issues handling invites as users will only have the production artifact installed. This allows multiple internal test artifacts to be validated using the same deployment.