Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
Beyond that, I don't know how purchasing different packs on different 3rd-party platforms plays out. One would assume that, for example, an Epic purchase and a Steam purchase of the same game will mash together on UPlay, so you end up with the combined content from both purchases. Whether or not that translates back to launching a game from Steam and seeing the DLCs you've bought on Epic, I don't know.
You should be able to always launch via the UPlay client directly, to get whatever Ubisoft knows you have. Along the same lines, you cannot launch a game through the Steam client if you've never bought the Steam version of it. UPlay is not actually integrated into the Steam client to access both libraries, it's still an entirely separate thing.
Have you actually tried any of these things, if you actually have this case? Why not just look at what happens when you launch the game via the various platforms?
For example: if you own the dlc on Epic, then you gotta launch the base game on Epic to access.
I don't own any Ubisoft games through Epic, but the ones I own on Steam that use the Ubisoft client all show up with a Steam tag in my library on there. I suspect (and you can check this by launching the Ubisoft client) that the EGS ones will have an EGS label on them. So it sees them as separate entities.