PATH OF EXILE · COMMUNITY PLANNER

PoE 3.30 Atlas Tree Planner

Plan a 150-point PoE 3.30 Atlas tree. Compare the 3.29.1 and 3.30.0 datasets, understand Threads, and open the planner with the exact 3.30.0 version selected.

Updated

Open the 3.30.0 planner

A planner for the 3.30.0 Atlas dataset

This page is the version-specific starting point for a PoE 3.30 Atlas tree. Its launch button requests the registered 3.30.0 Normal Challenge dataset instead of relying on the last patch selected in your browser. Check the patch selector once the workbench opens. The general PoE 1 tool remains available for comparing registered versions, while this page keeps the context of the 3.30 release explicit.

The linked snapshot has a 150-point base budget. That is the ceiling of the registered dataset, not your account's current progression. Set a smaller planning budget if you have fewer points available. Opening the selected dataset restores a local plan for that dataset when one exists; it does not overwrite a plan saved against a different version.

3.29.1 versus 3.30.0: compare the data, not just the picture

The registered 3.29.1 snapshot has a 138-point base budget, compared with 150 in 3.30.0. Those twelve extra points are only one part of a version comparison. Reaching familiar names may require different connections, and a familiar notable may serve a different purpose. Rebuild the route against the selected dataset rather than assuming that adding twelve nodes produces a current allocation.

One concrete example is Chittering Champions. In the retained 3.29.1 export it affects an additional Scarab drop from the final map boss; in the 3.30.0 export the corresponding reward is a Thread. Unwavering Vision also has different wording and tradeoffs between those snapshots. Search the node and read every line of the current effect before carrying over assumptions from a previous farming strategy.

Registered Normal Challenge datasets
DatasetBase point budgetOfficial export
3.29.1138View source
3.30.0150View source

Threads change the assumptions behind a farming tree

The official 3.30 update replaces Scarabs with Threads and rebuilds the Atlas tree around the revised systems. The planner displays the published passives; it does not implement a Map Device or simulate random Thread outcomes. Use the official release notes for the rules of the encounter itself.

The 3.30.0 data distinguishes effects on finding Threads from effects on spending them. For example, Subtle Manipulations affects whether the Map Device consumes Threads, while Chittering Champions concerns a boss reward. These bonuses solve different problems. Decide which part of your strategy needs support before taking a cluster simply because its name contains Thread.

Game rules source: Grinding Gear Games' 3.30.0 update notes

A concrete 3.29.1 to 3.30.0 migration checklist

A migration is ready for use only when the destination allocation still expresses the original strategy. Work through these checks against the two registered Normal Challenge snapshots; keeping a familiar name is not enough to preserve its effect.

  1. Keep the 3.29.1 source separate. Preserve the original allocation and the assumptions behind it before reviewing a destination copy. Record the source dataset, its mode, and the encounters it was designed around so that the comparison does not silently turn into a different strategy.
  2. Verify the destination identity. Confirm that the candidate uses the registered 3.30.0 snapshot and the intended mode. A screenshot labelled 3.30 or a similar plan name does not identify the underlying graph. The destination's base limit is 150; your personal unlocked budget may be lower.
  3. Audit the named effects. Compare Chittering Champions' Scarab reward with its Thread reward, then review every line of Unwavering Vision. Do not carry its old twenty-point grant into the new version. Note any changed restriction that would undermine the inputs assumed by the plan.
  4. Recheck the entire connection. Confirm the route from the destination start to each important cluster, including connecting passives. Investigate missing or disconnected nodes instead of treating a partial migration as complete. Familiar node IDs do not establish that the old path is still suitable.
  5. Review conditions and opportunity cost. Check which bonuses depend on Thread use, particular encounters, or other assumptions you actually intend to meet. Compare the full cost of reaching each goal with the alternatives nearby. Twelve extra base points do not make an unnecessary detour valuable.
  6. Compare the result before replacing a working plan. Review the destination's point count, modifier sources, and notes together. Resolve allocation errors and explain any deliberate change in strategy. Keep the source available until the new route has been assessed under the maps and inputs it is intended for.

Build a progression plan before a finished 150-point tree

Begin with the number of points you have unlocked and connect a core route for one main mechanic. Add a second goal only when its full connecting cost fits. Name the intermediate plan so that you can distinguish what is usable now from the finished tree you hope to play later. The point counter includes the passives needed to reach your destination, not only the highlighted notable.

Before committing the remaining points, compare completing a nearby cluster with travelling to a distant one. Keep the version-specific modifier summary beside your assumptions about maps and inputs. A route can be connected and within budget while still relying on a condition your actual setup does not satisfy. This planner helps with allocation and review; it does not guarantee a strategy's profitability or verify your in-game unlocks.

Keep the 3.30 identity when saving and sharing

A saved plan and a shared snapshot refer to an exact dataset identity. If you want someone else to review a revised allocation, generate another link after editing; previously copied links retain their earlier snapshots. Include notes about the intended encounters and inputs so that the recipient can interpret the route rather than just its shape.

Export a JSON backup for important plans. Local browser storage is convenient for returning to a tree, but clearing site data or changing browsers can remove access to those local saves. The 3.30 landing page is an explanation and an entry point, not a public library of other players' private plans.

Frequently asked questions

Does the 3.30 button open the correct patch?

Yes. It links to the PoE 1 workbench with the registered 3.30.0 dataset identity selected. If that dataset is not part of a future release, the tool reports that it is unavailable instead of silently using another patch. A share snapshot still takes priority over a dataset query because it already identifies its own exact version.

Can I add twelve points to my 3.29.1 tree?

Do not assume that is sufficient. The registered base limit rises from 138 to 150, but node wording and connections also need review. Open each dataset explicitly, compare the important effects, and treat a migration as a new allocation to validate rather than an automatic extension.

Is this page a PoE 2 Atlas planner?

No. Version 3.30.0 on this page identifies the registered PoE 1 Atlas export. It is not a PoE 2 patch or an allocation that can be imported into PoE 2. Use the general PoE 1 tool page for the distinction between the supported planner and future modules.

Will this site spend my in-game points or Threads?

No. Planning happens in your browser and does not connect to your game account. You choose which decisions to reproduce in game, using your actual unlocked points, the matching patch and mode, and the current wording of any conditions or tradeoffs.