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
Considering what you say, and that I found no one in the whole building (except those two guards scratching the floor upstairs), I definitly think my quest was bugged.^^ I will try again with a new game.
I've done it a few times and it's never worked right. I doubt it will work until a patch comes out that fixes it. It's a bummer, but not much to be done except wait. That's what we get for playing EA, I guess.
Other one is the Dukes adviser who tell you he was kidnapped by DROW.
Both are behind doors upstairs you need to demolish.
Its possible they burned up I guess.
You want to do the Dukes adviser first. Very last door. Will be straight in front of you if you run the "horseshoe" upstairs.
That, can cause the issue... because it causes a further part of the quest to complete, before the part that leads to, and triggers it...
*Edit: that's directed at Sawbrandt and Bloodonmoon
Hmm. I've always done the guy under a beam first. Does that make a difference? Have you actually gotten a quest to rescue the Duke in the quest log here? I only get the quest for the guy looking for his wife.
The fire spreads if you do the beam guy first. and he wants to follow. It still works but I find it easier to do him on the way back
OK, but do you know if the Councillor's scene and quest are still buggy or do they show up like they're supposed to?
I don't mean quest completion, I mean getting the quest at all. There's nothing in my quest log.
Yeah, that's what I figured too. I'm just wondering if I can find a workaround.