On this page
OVERVIEW
Who this page is for
This page is for PC players who can access the current endgame Atlas and want a disciplined way to verify the Expedition Atlas before committing points. The official 0.5.4 preview identifies a Runes of Aldur Atlas Passive Tree and expanded Expedition customisation, but it does not justify copying a route from an unverified screenshot or older Patch guide.
PREPARATION
Before choosing a point
- Confirm that the client is on the 0.5.4 baseline and record the installed Hotfix.
- Open the Atlas in the PC client and capture the exact Expedition Atlas title, point total, node names, and node text.
- Save the matching official announcement URL beside the capture. A community database can help discover a term, but it cannot replace the original source.
- Check whether the character meets the current in-game unlock condition. Do not infer the condition from a previous Patch.
VERIFICATION STEPS
Verification route for the first points
Record available choices
Start by recording the available choices rather than allocating for a claimed "best" outcome.
Document each candidate node
For each candidate node, record its exact text, the content it changes, and the intended test area.
Test one change at a time
Test one change at a time in a repeatable Expedition or Grand Expedition context. Record the map/area, character state, and observed result.
Compare with official notes
Compare the result with the official notes and mark any mismatch as pending-verification.
Publish only after repeatability
Only after the observations are repeatable should a future published guide explain a route, its tradeoff, and the player profile it serves.
DECISIONS
Decisions this page does not make yet
This page does not name a required node order, a point total, a farming strategy, or an optimal reward target. Those conclusions require the current node text, a reproducible Steam PC test, and a stated build/gear context. They must also be revisited if a later official announcement lists a related interaction change; the cited 0.5.4d notes do not do so.
COMMON MISTAKES
Common mistakes to avoid
- Treating a previous Patch's Atlas image as current evidence.
- Assuming a node effect from its name instead of reading the live tooltip.
- Combining several variables in one run and then claiming that one node caused the outcome.
- Presenting a route as universal without recording its cost, build requirements, and failure cases.
SOURCES & CHANGELOG
Sources and verification
Related content
Information is compiled from public web sources and in-game observations; some visuals are original editorial diagrams. External information and images remain the property of their authors or platforms; contact us for removal requests.