Baldurs Gate 3 Build Planner: What It Actually Does

Numbers on a tooltip rarely tell you whether something is good, only what it does.

The community favourite is usually the safest choice rather than the strongest one. Weight, slots and stamina costs are the hidden half of every gear decision. If you are coming to this after a long break, the terminology has probably moved on.

Better alternatives

Upgrade costs are steep enough that committing to the wrong piece is a real setback. Anything acquired far later than intended is competing against gear you already have. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. Scaling decides whether something stays useful, and scaling is rarely shown in the tooltip.

Raw numbers matter less than how the effect interacts with the rest of your build. The community wisdom on this is roughly half right, and the half that is wrong costs the most time. A situational item that covers your worst matchup earns its slot more than a generically strong one.

The cost of getting it

Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Most of the disagreement you will find online is two people describing different builds. A single check up front replaces a lot of guessing later.

• Keep the alternative rather than selling it immediately.
• Check the scaling before investing upgrade materials.
• Stop and reassess after two failed attempts rather than repeating the third.
• Consider how much of the game is left when you get it.
• Compare against what is already in that slot, not against nothing.
• Read the whole sequence once before doing the first step.

What to pair it with

Where something depends on your platform or region, that is called out rather than glossed over. Screenshots age faster than text, which is why this describes rather than shows. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Nothing here assumes a particular playstyle beyond wanting the thing to work.

Do the cheap check before the expensive one — that ordering alone saves most of the frustration. The short version is near the top on purpose; the reasoning is there if you want to know why. Where two approaches both work, the one with fewer moving parts is the one to keep.

When it is the right choice

There is no hidden trick here that the game is keeping from you. What follows assumes you are on a current install and have not modified it. If your result differs from what is described here, note what is different first rather than starting over.

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. The developers have changed their mind about this at least once, which explains the older advice.

What it does in practice

Baldur's Gate 3 is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. Anything that behaves differently on console than on PC is flagged where it matters. Treat anything stated without a version number as provisional.

Where people go wrong

• Rushing the last step, which is usually the one with the actual requirement in it.
• Ignoring the platform-specific note and then wondering why the steps do not line up.
• Grinding a method that was patched months ago because a thread still ranks well.

BG3 FAQ

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.

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.

How long does this take?

Minutes if it goes cleanly, an evening if you hit the edge case in the caveats list. Neither is unusual.

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.

Come back to the caveats list if it does not work first time — the answer is almost always in there.