The difficulty here is rarely mechanical — it is a decision made twenty minutes earlier that closed the door.

Short answer

Prepare first, then work through it in the order below. Nothing here rewards rushing the opening.

Difficulty settings change numbers here, not the sequence. A save immediately before the decision point costs nothing and occasionally saves hours. Everything below is framed around the current state of Baldur's Gate 3 rather than a launch-week impression.

If it goes wrong

Optional preparation is what separates a ten-minute attempt from a two-hour one. Some outcomes are locked behind an earlier conversation rather than behind performance. The short version is near the top on purpose; the reasoning is there if you want to know why. Reading ahead spoils some of it; going in blind costs some of it. Pick which you mind less.

The game signals the requirement once, quietly, and never mentions it again. Most of the disagreement you will find online is two people describing different builds. A failed attempt usually leaves the world in a state you can still recover from.

The part people get stuck on

Nothing here assumes a particular playstyle beyond wanting the thing to work. The community wisdom on this is roughly half right, and the half that is wrong costs the most time. The awkward part is rarely the step itself, it is knowing which step comes first.

  • Check your inventory against what the section demands.
  • Save manually before the first irreversible step.
  • Expect one number in every guide to be out of date; the method is what matters.
  • Complete the optional preparation — it is the actual difficulty setting.

Before you start

Do the cheap check before the expensive one — that ordering alone saves most of the frustration. Screenshots age faster than text, which is why this describes rather than shows. If your result differs from what is described here, note what is different first rather than starting over. What follows assumes you are on a current install and have not modified it.

A single check up front replaces a lot of guessing later. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about.

Choices that matter later

There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. There is no hidden trick here that the game is keeping from you. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see.

Treat anything stated without a version number as provisional. Where two approaches both work, the one with fewer moving parts is the one to keep. Anything that behaves differently on console than on PC is flagged where it matters.

Working through it

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Where something depends on your platform or region, that is called out rather than glossed over.

Where people go wrong

  • Trusting a video thumbnail that promises a result the video never actually shows.
  • Rushing the last step, which is usually the one with the actual requirement in it.
  • Skipping the prerequisite because it looked optional in someone else's summary.
  • Assuming a guide from an older season still describes the current version.

BG3 FAQ

Is this still accurate after the latest Baldur's Gate 3 update?

The method is; individual numbers may not be. If a value on your screen differs, trust the screen and keep the sequence.

Does this work the same on console and PC?

The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

What if none of this works for me?

Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.

If you only take one thing from this: the answer near the top is the part that matters, the rest is context.