PoE 1 versus PoE 2: choose the matching game data
This workbench uses PoE 1 Atlas exports. It is not a PoE 2 simulator. Similar names across the games do not establish matching node identities, connections, or allocation rules. In particular, the 150-point PoE 1 dataset is not a statement about PoE 2's point budget.
| Context | PoE 1 | PoE 2 |
|---|---|---|
| Atlas planner | Available here | Not released here |
| Allocation data | Registered PoE 1 official snapshots | Requires separate data and rules |
| Character passive planner | Not released here | Not released here |
When you open a shared allocation, its exact dataset selects the context before your browser's last-used patch. Keep the game, patch, and mode with a plan instead of treating a familiar tree screenshot as a transferable build.
Why a PoE 1 tree cannot be applied to PoE 2
A passive allocation is meaningful only inside the graph that defines it. The graph supplies the starting point, which nodes can connect, what a node costs, and the conditions attached to its effects. Copying a list of node numbers into a different game's data does not carry those relationships with it. Even if a number happens to exist in both datasets, it is not a cross-game identifier for the same decision.
Visual similarities are equally unreliable. Two wheels can use familiar artwork or describe a similar encounter while occupying different positions in their respective trees. A route that is short in one graph may be unreachable from the other game's starting point. Its surrounding small passives, available budget, and nearby alternatives also contribute to its value. A screenshot preserves a shape, but does not prove that the shape represents a legal or useful allocation elsewhere.
The rules around the allocation matter as much as the picture. A bonus can refer to an item, encounter condition, or progression system specific to its own game. Importing the words without those conditions would create a misleading result. This workbench therefore uses registered PoE 1 exports and keeps other game modules separate. PoE 2 support is not released here, and changing a page label cannot turn an existing PoE 1 plan into a PoE 2 build.
138 points versus 150: two concrete node comparisons
The retained Normal Challenge snapshots provide a useful example of why a patch identity matters even within PoE 1. Their base point limits are 138 for 3.29.1 and 150 for 3.30.0. However, the same named passive can retain its identifier while changing its purpose. Treat the extra twelve points as a budget difference, not as evidence that an older collection of node IDs still expresses the strategy you intended.
Chittering Champions keeps node ID 53876 in both registered exports. In 3.29.1, the final map boss has a 25% chance to drop an additional Scarab. In 3.30.0, the additional reward is a Thread, with the same listed chance. The numerical percentage survives, but the reward system it refers to changes. An older note describing this node as part of a Scarab strategy would therefore be misleading if carried into the newer plan without review.
Unwavering Vision, node 65225, illustrates a larger change. The 3.29.1 snapshot grants twenty Atlas points alongside restrictions on fragments and Scarab drops. The 3.30.0 snapshot instead restricts applied Threads to one type, adds two Threads to Threaded maps with an exception to the usual eight-Thread limit, and gives Threads found in your maps a 75% chance to become Gold. Those are different tradeoffs, not a renamed version of the earlier point bonus. Neither the old conditional grant nor the new Thread exception should be confused with the dataset's base budget.
These examples come from the two pinned exports linked below. They demonstrate changes in effect text, rather than claiming that every old node is removed or every connection is different. A sound comparison checks the particular passives the strategy depends on and then evaluates the connected route needed to reach them in the destination snapshot.
Common mistakes that make a plausible tree misleading
A highlighted mechanic is not necessarily an allocated mechanic. Centre icons identify related clusters; they do not consume points or activate all nearby passives. Confusing a bright highlight with a paid route can make an empty or partial plan look complete. The allocation counter and the effects of actual selected passives are the relevant evidence when assessing what a plan currently contains.
A refund can have a larger effect than removing the one icon under the pointer. If that node is the only connection to another branch, the branch also needs to be considered. The confirmation explains the connected refund rather than treating the downstream nodes as freely attached. The reverse mistake is counting only a desired notable and forgetting the connecting passives that must fit inside the budget.
Repeated text also needs interpretation. A summary count records how many allocated sources share a modifier; it does not establish a final drop rate or multiply every nearby reward. Conditional wording, the source of the bonus, and the encounter being modified still matter. A connected allocation can remain a poor fit for a particular map setup even when it passes the planner's basic budget checks.
Finally, distinguish a shared preview from your own working copy. A link describes a fixed dataset and allocation, not a live subscription to its author's edits. It also does not prove that the recipient has earned the listed points or uses the same game mode. These distinctions prevent a valid snapshot from being mistaken for a current, personally applicable recommendation.
1. Select a patch and set your current budget
Choose a registered version in Patch, then set Point budget to the points you intend to allocate now. The 3.29.1 and 3.30.0 base budgets are 138 and 150 respectively. After changing patches, check the version label and the local plan restored for that dataset.
2. Inspect the route, then allocate or refund
Hover a passive for its complete effect and connecting cost. Click to allocate its connected route, or inspect it in the details panel first. Paths over budget are flagged. Right-click to refund; when other nodes would become disconnected, the page asks before refunding them together. Use Undo and Redo to compare recent changes.
3. Use search, mechanic highlights, and the stats panel
Search by name or modifier. Click a mechanic centre to highlight related locations, and click the same mechanic again to clear it. Direction controls identify matches outside the viewport. Stats lists allocated modifiers and their source passives; ×N counts repeated sources, not a final drop probability.
4. Save a copy or generate a share snapshot
Plans save automatically in this browser. Share tree creates a fixed allocation snapshot; a recipient can Save a copy. Generate a fresh link after making edits. Export important plans as JSON because clearing site data can remove local saves. This tool does not spend points or items on your game account.
Frequently asked questions
Can a matching node ID make a PoE 1 plan valid in PoE 2?
No. Node IDs are interpreted inside a particular game's dataset. A matching number does not transfer its connections, cost, effects, or allocation conditions. This release supports the registered PoE 1 Atlas data, so it should not be used to validate a PoE 2 build.
Why does the same notable behave differently between 138-point and 150-point trees?
The budgets describe two different snapshots, not two sizes of the same unchanged tree. For example, Chittering Champions keeps its ID while changing its additional boss reward from a Scarab to a Thread. Inspect the effect in the selected version before assuming an older strategy still applies.
Does the old Unwavering Vision bonus raise the 3.30 base budget?
No. Its twenty-point grant belongs to the retained 3.29.1 wording. The registered 3.30.0 version has Thread-related effects instead. The base budgets shown for those datasets and the effects of a conditional passive are separate facts; an older bonus should not be added to a newer dataset by assumption.
Why does refunding one passive also involve other nodes?
That passive may be the only connection between the start and another allocated branch. The confirmation identifies the dependent refund so that the remaining allocation stays connected. Cancelling leaves the allocation unchanged. A branch reached by an alternative allocated route need not depend on the same connecting node.
Will a shared preview change when its author edits the original plan?
No. The link encodes a snapshot and an exact dataset identity. A later edit requires a new link. A recipient can save a separate copy, but should still check their own unlocked points, mode, and relevant conditions before treating the snapshot as a plan to reproduce in game.
Registered datasets: 3.29.1 · normal · challenge · 138 points; 3.30.0 · normal · challenge · 150 points
The interface supports English and Simplified Chinese; node text uses the source game data. Connectivity and budget checks do not replace reviewing in-game conditions and your actual unlocks.
Choose your next step
- PoE 3.30 Atlas planning guide →
Check the 150-point dataset, Thread changes and version migration checklist.
- PoE 3.30 starter builds →
Compare documented starting routes and the requirements for later transitions.
- PoE 3.30 tier list →
Compare starter readiness and understand the tradeoffs behind each editorial tier.
- PoE level calculator →
Calculate XP remaining, time to your target and estimated maps from your own net gains.