Path of Exile 2 / Path of Building
Start with the thing that catches most people: this is a different application, not the Path of Exile version with a toggle. After that, the interesting problem is that both the game and the tool are still moving.
A separate community project with its own repository, its own releases and its own calculation engine. This is the one that opens a Path of Exile 2 export code.
Free · open source · community maintained
The long-established version for the original game. Excellent, mature, and it will not do anything useful with a Path of Exile 2 character. Different game, different maths.
Also free · also community · wrong one here
Both are community projects rather than official tools, and neither is hosted here. Download from the project's own repository, not from a mirror.
This is the difference that matters most, and it inverts the usual troubleshooting advice. In the original game, the calculator has had many years to converge on the rules. When a number looks wrong there, the tool is very rarely the reason.
Path of Exile
A stable game and a mature tool. Mechanics change occasionally and the calculator catches up quickly, because most of what it models has been settled for years.
A discrepancy is nearly always your configuration.
Path of Exile 2
A game still being balanced and a tool still being written against it. Newer mechanics may be partially implemented, approximated, or not yet handled at all.
A discrepancy might genuinely be the tool, and assuming otherwise wastes an hour.
None of which is a criticism of the project. Volunteers reverse-engineering a game that changes under them are doing something genuinely difficult, and they are usually explicit about what is not yet modelled. Reading the release notes for what is unimplemented is worth more here than in any other version of this software.
Given a figure that looks wrong, there are three possible sources and they need different responses. Working out which before you start fixing saves most of the frustration.
Most of the configuration discipline transfers directly. Four things behave differently enough to be worth naming.
All the usual caution applies — a figure describes a configuration, not a fight — plus one more that is specific to this situation.
Treat the absolute number as provisional and the comparison as reliable. Even where the tool has not fully caught up with a mechanic, it is usually applying the same incomplete model to both sides of a comparison, which means the difference between two configurations survives an error that would ruin either figure on its own.
That is why comparing is the right use of this software here, and quoting a headline number is the wrong one. The build comparison guide covers doing that properly, and the DPS difference calculator tells you whether a gap is large enough to act on.
Damage numbers shown on build overviews are produced by running exported characters through a calculator under a standard configuration. So the figures you see there inherit whatever the tool currently models, including the parts still being worked out.
Which means a site figure and your own file can disagree for a reason that is neither's fault: they were generated by different versions of the same evolving model. Worth remembering before assuming either is authoritative. The pipeline page covers where in the chain that calculation sits.
Get the right application, expect the tool to lag the game occasionally rather than assuming you have misconfigured something, and use it to compare rather than to quote.
Everything else is the same discipline as the older game — identical settings on both sides, the same damage row read in both places, and the understanding that a figure assuming perfect uptime describes a fight you will rarely have. That last point matters more here than anywhere, because there is less accumulated community consensus about which assumptions are reasonable.
Sign in to your account