The most dangerous POB number in POE1 is the one that looks perfectly believable. You import a build, see enormous DPS, and start pricing the POE currency needed for its gear-then discover the character only reaches that number with every charge, flask, enemy effect, and temporary proc active at once. POB is brilliant, but it reports the situation you describe, not the fight you actually play.

Start With the Fight, Not the Screenshot

A useful POB review begins by defining the encounter. Mapping, a stationary boss, and a movement-heavy endgame arena demand different settings. A six-second burst window can be valid for a damage phase, yet it shouldn't represent ordinary single-target output. Create separate configurations for baseline mapping, sustained boss pressure, and short burst. Keep the baseline conservative: remove effects that require perfect timing, constant proximity, or an enemy already suffering from a special state.

Read the Number Behind the Number

POE1 damage isn't delivered by a spreadsheet. Attack speed, cast time, projectile travel, area placement, target movement, channel interruptions, and time spent dodging all reduce practical uptime. For skills with overlapping areas or secondary effects, ask how often the target actually remains inside the overlap. For melee skills, ask how much time you lose reaching the target. My own rule is simple: compare the clean baseline first, then add burst layers one at a time.

Defence Is a Loop

Don't judge a POE1 character by life, energy shield, or one impressive maximum-hit line. Survival comes from the loop between taking damage and recovering: resistances and mitigation reduce the hit, avoidance or block lowers contact frequency, and regeneration, leech, recovery on hit, or guard effects help you remain functional afterward. A character that survives one huge strike may still fold to several smaller hits if recovery depends on hitting packs. Test single-target resource flow separately, especially when the main skill has a high cost or reservation setup.

Build the Path, Not the Trophy Case

The biggest gap in shared POB files is often progression. Perfect rares, expensive jewels, and fully optimized links may describe the destination while saying nothing about the first red maps. Build item sets and passive trees for at least three stages, then mark the point where each major mechanic becomes practical. Before buying an upgrade, check what it fixes as well as what it adds. A small damage gain that frees resistance suffixes or removes an attribute problem can be better than a larger DPS increase that makes the rest of the loadout impossible.

A Five-Minute Audit

Before copying a POE1 build, run this quick check.

Confirm the file's ruleset and read its notes before changing gear.
Disable charges, flasks, enemy states, and short-duration buffs one by one.
Check whether mana, life, or energy shield remains stable against one target.
Compare movement-heavy play with a stationary damage test.
Inspect the cheapest workable item set before viewing the luxury version.
Write down the first failure point: weak recovery, attribute pressure, poor range, or missing mitigation.

That last note matters more than another decimal place on the DPS panel. POB is strongest as a question machine: what happens when the boss moves, a flask expires, a charge drops, or your rotation breaks? From what I've seen, builds that answer those questions honestly are far easier to improve than flashy imports built around a single peak state. Spend your POE orbs on solving the weakest link first, and the character usually feels stronger long before the headline number catches up.