PoE1PoE2Améliorations d'équipementCovens newsDiscord
FR
Avis
Version préliminaire. Vérifiez les gros achats dans Path of Building, et dites-le-nous si quelque chose semble faux.

← All guides

What Path of Building can't see (and what we do about it)

Where Path of Building's numbers for Path of Exile run too high or too low - flasks and conditions, cooldown supports, extra projectiles, triggered skills, Fury Valve, close-range bonuses - and how PoE MVP handles each one in its upgrade suggestions.

6 min read

Path of Exile art by Grinding Gear Games
In short
  • Path of Building is a calculator: it assumes every condition is met and every skill is used non-stop.
  • Flasks, conditions, cooldowns and close-range bonuses are the places it is most often too generous.
  • Extra hits from projectiles, repeats and triggered skills are where it is often too stingy.
  • PoE MVP flags these on the card and keeps them out of Start here - the number is shown, the warning comes with it.
On this pageA calculator, not a simulation of you playingToo generous: things counted as always onToo generous: skills used non-stopToo stingy: hits that aren't countedFury Valve with skills that bounce or chainThings only the item itself can tell youHow to use this

Written in November 2026, for patch 3.30 (Covens of Umbra).

A calculator, not a simulation of you playing

Path of Building is the best tool the game has, and everything PoE MVP does stands on it. But it answers a narrower question than people think. It doesn't play your character. It takes a snapshot - your gear, your tree, your gems, a list of ticked boxes - and works out the numbers for that instant, as if the instant lasted forever.

Most of the time that is exactly what you want. It goes wrong in two directions: things it counts that you don't really have all the time, and things you really have that it doesn't count. After reading a lot of reports and a lot of feedback, these are the ones we now handle on purpose.

None of this is a complaint about Path of Building. Each of these is a place where the honest answer is "it depends how you play", and a calculator has to pick one.

Too generous: things counted as always on

Flasks are the clearest case. A flask that is switched on in the build is counted as active all the time. In a map with enemies to kill that can be close to true; in a long boss fight it isn't. It cuts both ways: an export with its flasks switched off undersells the character, and one with every flask on assumes perfect uptime.

Conditions in your own configuration work the same way. Maximum power charges, an enemy that is always shocked, a buff with perfect uptime - if the box is ticked, every number assumes it. We use your build as it was exported, so an optimistic configuration gives optimistic gains. It's worth opening the Configuration tab once and unticking what you can't actually keep up.

Essayez it - a bonus that isn't always on
Counted
On average

The default enemy is another one. Path of Building's standard target is a pinnacle boss, so anything that says "against Rare and Unique Enemies" is counted in full. Against the normal monsters that make up most of a map it does nothing at all. If you spend your time mapping, pick Mapping on the report and those bonuses stop being counted.

Bonuses that depend on the enemy being close - Close Combat is the usual one - are counted as if the enemy is standing next to you, unless your build sets an enemy distance. On a bow or a spell cast from across the screen that's rarely true, so we flag them on ranged builds.

Too generous: skills used non-stop

Path of Building's damage figure assumes you press the skill again the moment it finishes. A support that gives the skill a cooldown breaks that assumption in a way the number can't show: the bigger hit is still multiplied by your full attack or cast rate, so on a main skill the result can be several times too high. We don't suggest cooldown supports for your main skill at all; they're listed as left out, with the reason.

Too stingy: hits that aren't counted

The opposite mistake is just as common, and it makes good supports look bad.

For most projectile skills Path of Building works out the damage of one projectile hitting. Add three more projectiles and the number often goes down, because the support that adds them also lowers damage per projectile. In game, some of those projectiles hit the same target. We count each extra projectile as landing on a single target half the time. That is a middle estimate: against a pack, or point blank, it's worth more, and at long range less.

There's one case where extra projectiles really do add nothing to a single target: a skill whose damage is all damage over time that can't stack. The enemy carries one copy of the debuff however many projectiles delivered it, so we don't count the extras there.

Supports that add hits in other ways - seals, cascades, repeats - are often only partly counted. The report marks them "(not all counted)" and won't suggest swapping one out on its number alone, because the number is missing the reason you socketed it.

Some supports trigger a separate skill of their own. Path of Building scores that skill on its own line, so against your main skill the support can read as roughly 0% while adding real damage. Same treatment: shown, flagged, not offered up as dead weight.

Fury Valve with skills that bounce or chain

One combination deserves its own warning, because Path of Building's answer for it is very probably too high. Fury Valve turns modifiers to the number of projectiles into split targets. Skills like Poisonous Concoction of Bouncing turn them into extra bounces instead. Path of Building applies both at once, so every extra projectile is counted as a full extra hit.

In the game they most likely become splits, and a projectile that hits the ground - the flask - can't split. If that's right, a support like Greater Multiple Projectiles adds nothing there except its less-damage penalty, and the damage figure for the build is too high.

We haven't been able to confirm this in game, so the report doesn't change the number. It adds a warning, and adding or replacing a projectile support on such a build is treated as a caution.

Things only the item itself can tell you

A few lines on unique items aren't simulated at all - Path of Building shows them in red. A unique with a red line can be worth much more or much less than its number, and no calculator can say which. The unique's card names the lines that weren't counted so you can judge them yourself.

Uniques with a fixed number of sockets are a smaller example. When your slot holds more gems than such a unique has sockets, we skip it: Path of Building would go on counting the gems that no longer fit.

Vaal gems carry two skills in one gem. When the part selected in the build does no damage, the report scores the damaging part instead, so the gem isn't written off as doing nothing.

How to use this

You don't need to memorise the list. The practical rule is short: when a card carries a caution, read it before you buy. It's one sentence and it says which assumption the number rests on.

Then ask the question the calculator can't: how often is that true for me? If the answer is "nearly always", the number stands. If it's "during the first two seconds of a boss fight", it doesn't.

If you find a case we don't handle - a support that looks far too good, an item that looks far too bad - the feedback box at the bottom of every report goes straight to the developer. Several of the rules above started as one player's thumbs-down.

A note from the developer: I'm not a professional guide writer or a top Path of Exile player - these guides are written to help, and some details may be wrong or out of date. If you spot a mistake, please let me know and I'll fix it.

Art: Grinding Gear Games (press kit).

Check your own character - PoE MVP simulates your gear, support gems and passives in Path of Building and ranks the upgrades, with trade searches that keep your resistances and Spirit intact. Collez votre personnage. It's free.