Why Some Buffs Are Not Enabled

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.

Why Path Of Building Leaves Them Off

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.

The tool knows everything about your build and nothing about your fight. Leaving conditional buffs off is how it admits that, instead of guessing in your favour.
Conditions PoB will not assume for you
Power, frenzy and endurance chargesNeeds: charges up
At full life bonusNeeds: life threshold met
Enemy is shocked and cursedNeeds: debuffs applied
Damage flask activeNeeds: flask uptime
Onslaught from a killNeeds: recent kill

Illustrative. Each stays off until you confirm you actually hold it. Here only the flask you keep up all fight is switched on.

Conditional Versus Always-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.

Counted automatically

Always-On Buffs

Auras, passive bonuses and permanent modifiers that are true in every moment. PoB includes them without asking, because there is nothing to verify.

Waits for you

Conditional Buffs

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.

The Kinds Of Condition

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

ChargesNeeds power, frenzy or endurance charges active. Easy to hold on some builds, unreliable on others.
ThresholdsNeeds you at full life, on low life, at full energy shield, or a similar state that you may or may not be in.
Enemy stateNeeds the target shocked, cursed, chilled or at a certain range. Common against packs, harder to guarantee on a lone boss.
UptimeNeeds a flask active or a buff recently triggered. Realistic only if you can actually keep it running through the fight.
Recent actionNeeds you to have moved, hit, or killed recently. Fine while clearing, often false in a long single-target fight.

Off Is A Feature, Not A Bug

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.

How To Enable Them Honestly

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.

  1. Set A Boss Target First

    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.

  2. Enable What You Reliably Hold

    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.

  3. Leave Off What You Cannot Guarantee

    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.

  4. Read The Figure That Results

    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.

A Rule Of Thumb

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 Mistakes That Cost People

  • Enabling everything for a bigger number. It rebuilds the fantasy figure and tells you nothing useful.
  • Assuming a conditional buff is always up. Charges drop, flasks lapse, debuffs fall off. Enable only what you truly sustain.
  • Reading the number before setting a boss target. Pack-clearing conditions rarely hold on a lone boss, which is the fight that matters.
  • Treating default-off as a bug to override. It is the honest default. Overriding it blindly is how the number lies to you.
  • Comparing two builds with different buffs enabled. Match the toggles, or the comparison is meaningless. See build comparison.

Buffs And Conditions In Path Of Exile 2

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.

Keep Going

Reading the Config tab honestly is one skill. These carry it into real decisions.

Questions People Ask

Why are some buffs off by default in Path of Building

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.

Should I just enable everything

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.

Which buffs are safe to enable

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.

Why did my damage jump when I enabled a buff

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.

Is the default-off behaviour a bug

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.