PoE2 0.5 Route Lab
This page summarizes the most important PoE2 0.5 passive tree changes before you update a route from 0.4. The interactive planner remains the best place to inspect exact positions, but the tables below give a crawlable overview of what changed, why it matters, and when an older Path of Exile 2 build should be rechecked.
The main search intent for PoE2 0.5 passive tree changes is practical: players want to know whether a saved build path can still be trusted. A change count alone is not enough. A moved travel node may only cost one extra point, while a removed notable or changed ascendancy notable can invalidate the reason the route existed in the first place. Treat this page as a triage view: use it to decide what needs review, then open the planner to check the exact route.
The comparison behind this page reads the bundled 0.4 and 0.5 passive tree data. It groups differences into added passives, removed passives, stat changes, renamed entries, and moved nodes. The planner overlay uses the same categories so you can move from this summary into the working tree without changing terminology.
Planning advice: do not copy an old 0.4 route into 0.5 until you have checked the class start, ascendancy start, notable stat text, weapon-swap budget, and nearby alternatives.
| Change | Example passive | Why it matters for planning |
|---|---|---|
| Added | Bond of the Ape | Area of effect and companion-adjacent routing should be rechecked for builds using nearby clusters. |
| Added | Bond of the Cat | Companion movement speed changes can affect minion and companion planning paths. |
| Added | Knight of Tarcus | Armour conversion into elemental mitigation creates a new defensive comparison point. |
| Added | Left Ventricle | Recoup effect speed can change whether a recovery cluster is worth the travel cost. |
| Removed | Thirst of Kitava | Builds relying on instant life leech from empowered attacks need a new recovery assumption. |
| Removed | Calibration | Energy shield routes using this notable need a replacement defensive cluster. |
| Removed | Reformed Barrier | Minion and energy shield recharge interactions should be reviewed before reuse. |
The 279 stat-changed entries are the biggest reason to avoid relying on screenshots or old route notes. A familiar passive name can still exist while its value, condition, or supported mechanic has changed. Prioritize any notable or ascendancy notable that defines the build's damage engine, ailment chance, recovery loop, mitigation layer, or resource economy.
| Category | Example | Review action |
|---|---|---|
| Stat changed | Heatproof, Chillproof, Dependable Ward | Check whether defensive values still justify the same number of travel points. |
| Ascendancy stat changed | The Catha's Balance, Hollow Form Technique, The Mhacha's Gift | Recheck the ascendancy plan before importing an older build file. |
| Moved | Wellspring, Stars Aligned, Rapid Strike | Open the overlay and confirm whether the route still connects efficiently. |
| Renamed | Energy Shield Mastery to Mana Mastery | Search by both old and new concepts when updating notes from an older planner. |
This comparison is built from local passive tree exports bundled with the planner. It is designed for theorycrafting, route review, and practical build planning. It is not an official Grinding Gear Games service. For patch confirmation and official game context, check the Path of Exile website. For additional community data references, many players also cross-check databases such as PoE2DB.
The current bundled comparison finds 129 added passive entries, 21 removed entries, 279 stat changes, 6 renamed entries, and 205 moved nodes when comparing PoE2 0.5 against 0.4.
Yes. Open the planner and enable the 0.5 change overlay. Added, removed, moved, renamed, and stat-changed passives use different colors in the interactive tree.
Not always, but you should review any route that depends on a removed node, a changed notable, an ascendancy notable, or a cluster that moved far enough to alter travel cost.
No. This page is a crawlable summary. The planner is still the correct place to inspect exact node position, search terms, class starts, ascendancy starts, and exportable build routes.