Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I did some trial an error , saving before the Minthara fight and runing to moonrise towers afterwards.
This is what I discovered.
- You MUST knock Minthara out in the Goblin Fortress
- You CANNOT knock her out after temporary hostile flag is gone.
- The Goblins CANNOT hit the war drums to sound the alarm, both before and or after she is knocked out. I believe this causes the temporary hostile flag to be removed.
- You will know this is done correctly if you long rest and Minthara Respawns.
I really hope this is an oversight in the fix and this process is made clearer/better.
Please fix this LARIAN we love you!
:HEART
Also the comunity has made this realy good guide wish I saw this earlier
So Minthara has to be saved before getting to Nightsong. Though if she wasn't in Moonrise even before that then I have no idea why she wouldn't spawn after siding with her.
I didn't even make it that far. I walked into the tower and just had the goblins who said take it up with Minthara. I assumed that meant she was around somewhere, so I took a look around the towers and didn't see her anywhere. I'm fairly positive the issue is the borked condition of her needing to be 'temporarily hostile' when you knock her out. Most people will end up making her permanently hostile by declining her demands, or getting into combat and one of the drums gets hit, making everyone hostile. This seems like a bug to me.