Baldur's Gate 3

6246 readers

189 users here now

All things BG3!

Baldur’s Gate 3 is a story-rich, party-based RPG set in the universe of Dungeons & Dragons, where your choices shape a tale of fellowship and betrayal, survival and sacrifice, and the lure of absolute power. (Website)

Spoilers

If your post contains any possible spoilers, please:

Use the text [SPOILER] at the beginning of your title, do not include any spoilers in the title.
Use the appropriate spoiler markup to conceal that content in the body of your post.

Thank you!

founded 1 year ago

MODERATORS

[email protected]

Is there an ETA for a fix on the Lift the Shadow Curse bug? (self.baldurs_gate_3)

submitted 1 year ago by LopensLeftArm to c/[email protected]

7 comments fedilink hide all child comments

(Spoilers for Act 2)

So I advanced through the quest line until Halsin says to meet him at the lake side by the Last Light Inn. Go to pick up that quest, and he's nowhere to be found. In my camp, he was just standing there where he always is, had the quest maker over him on the map, but no quest advancement dialog options.

I proceeded through the rest of Act 2, checking back at Last Light Inn area after every quest finished, still no Halsin. I go their the whole Moonrise Towers bit and fight Ketheric, and there he is in the lobby at the end. I talk to him and he's all, 'Oh, I can't come with you because I have to stay behind and try to lift the curse.' I even follow the prompt offering to help him, and he says, 'No, you've got to go on to fight the big bads, I'll stay here, this is my fight.'

I eventually just proceeded on to Act 3. It's really disappointing to have to leave a huge story aspect unfinished because the quest NPC never shows up where he's supposed to.

Does anyone know when this is planned to be fixed? I'm hoping to be able to get this on my next playthrough.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] -1 points 1 year ago (1 children)

I've never had this happen.

[–] LopensLeftArm 1 points 1 year ago

When I'd first noticed it, I scoured the internet for fixes, tried all of them and nothing worked. Apparently it's a relatively common bug, I just seem to have had it so bad that it was never fixable.