Path of Building cannot know what you keep up during a real fight, so conditional buffs stay off until you switch them on. That default is not a limitation to work around. It is the tool being honest about the one thing it cannot see, which is you playing the game.
Where this sits
This explains one habit of the Configuration tab in Path of Building, and it is the reason behind why the highest DPS build may not be best. If a build's damage jumped the moment you flipped a switch, this is why.
Path of Building models a character on paper. It knows your gear, your tree and your gems exactly, and it can calculate what they produce with real precision. What it cannot do is watch you play. It has no way of knowing whether your charges will be up, your flask active, or the enemy shocked at the exact moment you land a hit. So for any buff that depends on a condition it cannot verify, it makes the honest choice: it leaves the buff off until you tell it the condition is met.
Illustrative. Each stays off until you confirm you actually hold it. Here only the flask you keep up all fight is switched on.
Not every buff defaults off. The difference is whether the buff is always true or only sometimes true. An unconditional bonus, a passive aura or a permanent modifier, is counted automatically, because it applies no matter what is happening in the fight. A conditional buff depends on a state, and until that state is confirmed, its contribution is unknown. Those are the ones that wait for your input, because their truth belongs to the fight, not to the build.
Auras, passive bonuses and permanent modifiers that are true in every moment. PoB includes them without asking, because there is nothing to verify.
Anything that needs a charge, a threshold, a debuff or an uptime. PoB leaves these off, because only you know whether you hold them in a real fight.
Conditional buffs fall into a few recognisable families. Knowing them makes it obvious why the default is off and easy to judge which you can honestly turn on.
What a conditional buff can depend on
It is tempting to read the default-off state as the tool being unhelpful, but it is doing you a favour. By leaving conditional buffs off, Path of Building forces you to opt in to each assumption rather than handing you a best-case number you never questioned. The figure you end up with reflects the conditions you consciously chose, which is exactly what makes it trustworthy. A number that assumed everything for you would look bigger and mean nothing.
The goal is not to leave everything off, it is to switch on only what is true for you. A short routine gets you to an honest number.
Point the calculation at a lone tough enemy in Path of Building, because that is the fight where conditions are hardest to hold and honesty matters most.
Turn on the charges, flasks and buffs you genuinely keep up for the whole fight. Those are true for you, so they belong in the number.
If a buff depends on something you will not always have against a single boss, leave it off. A number you cannot sustain is not your number.
What remains is your honest damage. Use it to plan and to compare builds, since it reflects the fight rather than a fantasy.
Enabling everything is the same mistake as trusting the tooltip
Flip every switch on and you rebuild the inflated best-case number, the one that looks huge and feels small in the fight. The point of the toggles is to include only what is real for you. Turning them all on defeats it entirely, which is exactly the trap described in why the highest DPS build may not be best.
When you are unsure whether to enable a buff, use this. If you cannot guarantee it against a single boss for the whole fight, leave it off. It is far better to be pleasantly surprised when a condition happens to be met than to plan your whole character around damage you only produce in a perfect moment. Build for the number you can always hit, and treat the higher one as a bonus.
The Path of Exile 2 version of Path of Building behaves the same way. It knows your build and not your fight, so conditional buffs default off there too, and the honest approach is identical: set a boss target, enable only what you hold, and read what remains. The specific buffs and conditions differ, so check them on the Path of Exile 2 view rather than assuming the original game's, as covered in the Path of Exile 2 guides.
Reading the Config tab honestly is one skill. These carry it into real decisions.
The full guide to the tool and its Configuration tab.
What happens when you trust the fully buffed number.
Why matched toggles are the only fair way to compare.
Read real characters and the setups behind their numbers.
Because they are conditional. They depend on a charge, a threshold, an enemy debuff or an uptime that PoB cannot verify, so it leaves them off until you confirm you actually hold them in a real fight.
No. Enabling everything rebuilds the inflated best-case number, the one that looks huge and disappoints in the fight. Turn on only what you reliably sustain, and the figure stays honest.
The ones you keep up for the whole fight against a lone boss, your permanent auras plus any charge, flask or debuff you reliably maintain. If you cannot guarantee it, leave it off.
Because that buff was conditional and off by default, so its contribution was not being counted. Turning it on added its effect. Just make sure it is one you actually hold, not a hopeful one.
No, it is the tool being honest. PoB cannot see your fight, so it declines to assume conditions in your favour. That default is what keeps the number trustworthy rather than flattering.
This is an independent educational guide to Path of Building and is not affiliated with or endorsed by Grinding Gear Games or the Path of Building project. Path of Exile and Path of Exile 2 are trademarks of Grinding Gear Games, and Path of Building is an independent community tool. Poe Ninja is an independent educational site, not affiliated with or endorsed by Grinding Gear Games or poe.ninja. Always confirm a build by testing it in game.
Sign in to your account