PoE2 Expedition Atlas Tree: Points, Bosses & 0.5.5d Guide

What the Expedition Atlas tree changes

The Expedition Atlas tree changes the Expedition experience: its encounter frequency, remnants, monster modifiers, and reward opportunities. It is not the same system as the large Atlas tree that shapes general mapping, and neither tree is the character passive skill tree. Think of it as a mechanic-specific point pool attached to one endgame activity.

That distinction is the fastest way to solve two common search problems. If you want to change damage, defences, attributes, or weapon-set passives, use a character planner. If you want to alter how Expedition appears or behaves in endgame content, inspect the Expedition branch in the Atlas. The site's main planner is for character routes; the general Atlas guide covers map progression and farming choices.

The official 0.5.5 notes do not republish the full Expedition branch, so this guide does not freeze a node count or claim one route is universally best. Confirm the available points and current tooltip text in your client before allocating; this is especially useful when a tree screenshot or guide may predate a patch.

What changed from 0.5.4 to 0.5.5d

Patch 0.5.4 introduced a dedicated Expedition Atlas Passive Skill Tree and expanded Expedition customisation. The official preview shows the feature in context. Patch 0.5.5 then moved Farrow, Dannig, and Expedition content into the core Atlas for Standard and the new Forbidden Rites league; the official notes say Expeditions can appear from Act 4 onward. Those are two different changes: the tree arrived in 0.5.4, while 0.5.5 changed where core Expedition content is available.

The 0.5.5 notes also list how multiple Expedition Tablets affect one map: one adds an Expedition; two add a Verisium Remnant and 35% Expedition density; three add another Expedition; four add another Verisium Remnant and another 35% density. This is a map setup layer. It does not replace the quest-boss source for Expedition tree points.

The official follow-ups reviewed here run through 0.5.5d. Patch 0.5.5b fixed natural Expedition spawns in endgame and increased Expedition, Temple, and Delirium Tablet drop rates. Patch 0.5.5c requires the Boat Charter to be turned in to Makoru to access Act 4 Islands (characters that already completed this step are unaffected) and fixed Farrow’s access to Verisium stored in Expedition stash tabs. Patch 0.5.5d fixed controller currency use during a Barren Atoll Expedition and improved feedback when a Tablet is placed in an unavailable map slot. These notes address encounter availability, access, and UI behavior; they do not list a change to the Grand Expedition boss requirement for this tree’s points. Recheck later official notes and the live client after October 2, 2026.

How to unlock Expedition Atlas points

The official 0.5.4 announcement says to defeat each boss in The Grand Expedition questline to earn its Atlas points. The practical route starts with a Logbook, which reveals an ocean area; from there, find a Grand Expedition and progress its questline. Regular Expedition encounters and unrelated main-Atlas objectives are not interchangeable with those boss kills.

Recent guides list four Grand Expedition leaders: Medved, Vorana, Uthred, and Olroth. Use the boss and island names shown by your current client, because translations and patches can change labels. If a point does not appear after a kill, check the correct tree's point counter, quest state, and whether you defeated the required quest version rather than a similar encounter.

Before you run a Logbook, decide whether you are progressing a new point, farming an already unlocked branch, or testing a specific reward loop. These goals are different. A point unlock is a progression task; a map Expedition is an encounter choice; and a Grand Expedition can add more planning and boss difficulty. Keeping that distinction prevents spending currency on runs that do not answer your question.

Choose a first Expedition route that fits your build

There is no universal best Expedition Atlas tree for every character. The better starting route is the one that produces repeatable clears without turning each remnant chain into a failure. First decide whether you want more Expedition opportunities on ordinary maps, more remnant or monster density per encounter, or an option that supports Verisium use. Then compare each node's written benefit and added encounter pressure.

If you are still unlocking points, favour readable, controllable choices and leave large difficulty multipliers until you know how your character handles the mechanic. If you already clear safely and want more targets per run, test one reward-density change at a time. If you are saving Verisium, the community-documented node Feeling Lucky? unlocks Farrow's sale of Liquid Verisium; confirm the tooltip and vendor inventory in your current client before building around it.

Extreme Archaeology is a clear example of a convenience-versus-control choice: community references describe it as replacing multiple explosives with one large blast. Covering more ground can make setup faster, but it can also select more remnants and stack more modifiers into one encounter. Try it after you can handle the ordinary route, not as the first answer to a low-damage or fragile build.

Do not use currency per hour claims from a guide as the decision rule. League markets, map quality, character damage, deaths, and the time needed to sell all change the result. A more useful test is to record several runs: Logbooks used, boss progress, deaths, time per encounter, and the materials you actually wanted. Keep a node only when the change helps that goal without breaking the clear.

A safe point-allocation workflow

1. Read the branch in the current client and note its own available-point counter. 2. Write down the run you are trying to improve: map appearances, remnants, Verisium, Logbook progress, or another explicit goal. 3. Select the shortest useful branch and avoid adding unrelated difficulty modifiers at the same time. 4. Run a small sample of comparable encounters. 5. Keep, change, or refund based on repeatable results rather than one lucky drop.

For a progression character, the first useful investment is often access to a route that makes the next boss attempt practical, not maximum reward density. For a stable farmer, the best next node depends on whether the bottleneck is encounter supply, remnant count, clear speed, or survival. If you cannot kill the spawned monsters reliably, extra density can reduce rather than improve the value of a session.

Check the Expedition Atlas separately from the main Atlas after every unlock. A character can have spare passive points while the mechanic tree still lacks points, or the reverse. The site's character planner helps audit the class start, damage, defence, and weapon-set allocation that determine whether your character can clear the encounter; it does not allocate Atlas tree nodes.

Common mistakes and when to revise the route

The most common error is allocating the wrong pool: Atlas mechanic points, main Atlas points, character passive points, and weapon-set points have different sources and effects. Another is copying a 0.5.4 node priority into a 0.5.5 league without checking which mechanics, tablets, and vendor options are available there. A third is increasing encounter difficulty before confirming that the base version is reliable.

Revisit your allocation when a patch changes a node, when you move from point progression to farming, or when your character's damage and defences improve enough to handle more modifiers. Change one meaningful variable at a time. If the route adds deaths, skipped rewards, or longer encounters without improving the materials you value, step back to the last stable allocation.

The exact best tree is therefore a decision that depends on your goal and character, not a permanent tier list. Use the official patch notes for stated changes, current tooltips for exact node wording, and your run notes for personal performance. When a community guide makes a market or currency claim, treat it as an example from that author's setup rather than a guaranteed outcome.

How to verify an Expedition Atlas tree guide

Check the patch date, league or realm, exact tree name, point source, and the tooltip for every named passive. A guide that only says “0.5” may predate the 0.5.4 tree or the 0.5.5 core transition. A guide that says Runes of Aldur may be describing its dedicated league rules rather than Standard or Forbidden Rites. The same mechanic label can hide different assumptions about Tablets and progression.

This page was checked on October 2, 2026 against the official PoE2 0.5.4, 0.5.5, and 0.5.5b–d notes. Those notes establish the point source and recent availability, drop, access, and UI changes; use the in-game tree for current node text and point totals.