Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
I want to play this hero in the Immortals campaign, not in custom battles.
As already described several times, this hero is not displayed in the heroes in this campaign!
She's a legendary hero, not a legendary lord. You don't see her as a choice when starting a campaign.
You recruit her by completing a quest chain DURING the campaign when playing as a Kislev or Empire faction.
So far, nothing from SEGA support.
Been trying for several days now. Is it just broken, or what?
Ah ok, wich Quest start this?
Unlock condition: playing as any Kislev or Empire faction, reach level 11 with your Legendary Lord. This will trigger Ulrika's personal quest chain. The first quest requires to build a Frozen Outpost, which requires a Tier 3 main settlement. The second quest requires to amass 15,000 Gold. Completing both quests will trigger a dilemna which will allow you to recruit Ulrika.
---
Balek de vos tickets d'assistance sur votre site buggé ! Vous poster sur Steam, alors vous répondez sur Steam !!!
Sounds great, in theory.
Unfortunately, I'm a few days now into not being able to link my accounts, and SEGA's only support response is for me to send them the error message--which I already did in the original support request--and have done again--and have ♥♥♥♥♥♥ absolutely nowhere.
Clearly, they have no clue how to properly consume the authentication request, and the JSON formatted "error message", containing a collection of user_id values, is hardly enough information for them to fix the issue.
It shouldn't take a week to validate the information in my support ticket and fix the problem, but here we are. Color me "unimpressed".