Artifacts represent your downloadable, playable content such as game clients and DLC, and are a concept specific to the Epic Games Store (EGStore).
The Epic Games Store can receive game invites from EOS-integrated games via an explicit opt-in system. This allows users outside of the store ecosystem to invite EGStore users to their game session.
You must map your deployments to your Epic Games Store artifacts to route the EOS-initiated invites through the EGStore ecosystem to your users in the Epic Games Launcher.
Leveraging your artifacts to expose game invites on the Epic Games Launcher requires the EOS SDK 1.11 or higher.
To map your artifacts to deployments:
Go to the Environments tab of the Product Settings for your product in the Developer Portal.
Click the Deployments button for the specific sandbox to work in and click More Options to Link Artifacts.
Select your artifacts to link with that specific deployment and arrange them in order by priority.
When you have multiple artifacts mapped to a single deployment, the Launcher client routes the game invite to the first locally-installed artifact that it finds in the order you specify in the Developer Portal.
Do not map your DLC artifacts to a deployment; only "base game" launchable artifacts should be mapped to deployments.
Having multiple artifacts is typically a scenario for you as a developer because your end users should only have the production artifact installed. This allows multiple internal test artifacts that you can independently validate against the same EOS deployment.
Your production artifact should always be mapped to your production deployment to ensure that invites deliver to your users in the EGStore.