AION 2 MAP
☰
GLOBAL
English
GLOBAL · Explore

Choose your faction

Choose a faction to begin

Recorded client positions, not live spawns. Unconfirmed local names remain in English.

Map legend

Empyrean tracesHidden cubesPet sourcesGathering nodesKibelisksEntrancesMonstersNamed bosses

Matching locations

0 locations

Choose a faction to begin

Your progress

0 Pets owned · 0 Collected · 0 Checked this run

Your route

    Start with the right AION 2 Empyrean Trace map

    The AION 2 Empyrean Trace map currently represents 559 traces in Verteron, 559 in Altgard and 200 in Lower Reshanta. Together, those regional files contain 1,318 recorded positions. Other supported regional maps may contain monsters or travel points without trace records. A region being available in the menu therefore does not mean every category has coverage there. Select your destination before comparing the count or planning a collecting session.

    Choose the exploration task to start with traces, teleport points and entrances visible. These surrounding references help you decide where to approach the next collectible. If other categories make the map hard to read, switch them off while working on the checklist. Keep enough context to recognize the terrain rather than reducing the view to an isolated dot with no useful landmarks.

    Set a small objective on the AION 2 Empyrean Trace map, such as checking the next few points around an accessible area. A regional total is helpful for coverage, but it is too large to serve as a practical instruction. Complete one patch, verify its marks, then decide whether to continue into the next terrain section.

    Search names or areas without losing context

    Search matches the trace's recorded name and area text. Empyrean Trace finds the category by name, while a recorded area name can narrow your search geographically. Try Dawn Legion Base in Verteron or Safe Haven in Altgard, then open individual results to inspect them. Area labels come from the imported records and may not align perfectly with a boundary or wording on another website.

    On the AION 2 Empyrean Trace map, the query also applies to other enabled layers. Searching for a trace or a specific area can hide teleport points whose records do not contain that text. Clear the query when you need to compare travel anchors. If no results remain, check the region, selected categories and hidden-found option before concluding that the area has no recorded traces.

    The location list displays matches in batches of thirty. Selecting a name focuses its point on the map, which is useful when several icons overlap. The identical name on many trace records does not mean they are duplicates; each position has its own identity and collection mark. Confirm the selected location before checking it.

    Read altitude as a clue about the approach

    A top-down marker gives horizontal position, while the detail panel's recorded altitude adds vertical context. Compare that altitude with nearby terrain and any source information you can inspect. A trace may belong above the surface you are standing on or below a ledge that looks close on the map. The AION 2 Empyrean Trace map does not measure your character's current height or calculate the climb between the two.

    The underlying regional data distinguishes Ground, Air and Water trace records. Verteron contains 386 Ground, 123 Air and 50 Water records; Altgard contains 442, 100 and 17 respectively. Lower Reshanta contains 102 Ground and 98 Air records. These are source classifications, not separate terrain filters in the current interface. They explain why inspecting only the nearest ground surface can leave a substantial portion of the checklist unresolved.

    Use altitude on the AION 2 Empyrean Trace map to ask the right next question: which accessible layer matches this point? It is not a tested movement instruction. Check paths, ledges and water in the game, and leave a difficult approach unresolved if you cannot yet establish how to reach the intended position.

    Compare three concrete regional records

    A reviewed Dawn Legion Base record in Verteron has a height of 224.92 metres and is classified as Air in the source. A Pamos Farm record is also classified as Air, at 107.57 metres. The two heights describe different locations, so they are not steps of one route. Open each point and judge its approach within its own surroundings instead of using a height figure as an absolute difficulty rating.

    An Altgard example at Safe Haven has a recorded height of 364.87 metres. In Lower Reshanta, a Black Fragments Area example is at 264.76, while a Black Fragments Area - Abandoned Island example is at 154.66. The AION 2 Empyrean Trace map includes these distinct positions so you can inspect the specific point you are missing rather than repeatedly searching a broadly named area.

    These examples are dataset records, not claims that every approach has been played through. If the point seems inconsistent, first compare the regional background, landmark and altitude. A screenshot that includes the terrain and selected marker is more useful for investigating the mismatch than the numeric height by itself.

    Build a collecting route that you can revise

    Add the next few candidates to your route after comparing their location and altitude. Start from a travel point you can use and order the stops according to the approach you expect to take. The AION 2 Empyrean Trace map retains that chosen sequence and lets you move stops up or down. An awkward point can be removed from the immediate route while remaining uncollected on the checklist.

    The connecting line is a planning aid. It does not find a safe path through terrain, identify locked passages or calculate flight requirements. If your first approach fails, revise the order based on what you see in the game. Collecting a reachable neighbour and returning later is a valid plan; a line on the website is not an instruction to force the original route.

    Keep regional routes separate when comparing destinations. The route list follows the currently selected region, and shared route links communicate selected stops rather than a tested walkthrough. A companion following your link still needs to confirm access and terrain on their own character.

    Mark a trace after collecting it

    Use the collected action after confirming the trace in the game. The AION 2 Empyrean Trace map stores that exact point's mark and updates the regional trace meter. Hide found entries when you want the map to show the remaining recorded positions. This is most useful when the marks represent real collection progress, rather than locations you merely passed or intended to visit.

    A trace check is different from a cube or gathering visit. Repeatable objects use a checked record because they can return; trace marks belong to the collection checklist. The clear-run control affects checked repeatable locations, so it is not the same as clearing your trace collection. A full progress reset has wider effects and should be used only when you intend to remove the saved collection state.

    The website does not maintain separate named character profiles. If you use the same browser for multiple characters, decide which character the saved checklist represents and keep separately named backup files when switching contexts. Do not assume that logging into another game character automatically changes the marks on the AION 2 Empyrean Trace map.

    Interpret the completion percentage correctly

    The progress meter divides collected trace records by trace records in the selected regional dataset. For example, collecting ten represented Verteron points means ten out of the site's 559 recorded positions. It does not inspect your in-game collection or count every possible reward source. A complete website checklist therefore establishes completion against these records, not an official audit of your character.

    Different community sources can report different totals or assign points to areas differently. The reviewed evidence has not established a resolved cause for every count difference. Before treating a discrepancy as a missing marker, compare the specific records and what each total measures. The AION 2 Empyrean Trace map keeps its own denominator visible so you can see the scope of the percentage.

    A later dataset revision may change that denominator. Your percentage can move when records are added or corrected even if your saved marks have not changed. Export progress before major changes or device transfers, and use an exact marker report when a saved entry appears inconsistent. Avoid resetting everything just to make two unrelated totals match.

    Investigate a missing or invisible trace

    Work through the simplest checks first: correct region, exact point, visible terrain layer and the character whose collection you are tracking. Temporarily show found entries if you may have marked the trace already. Compare the current game's collection information with your local checklist. A website mark cannot prove collection, and an empty location cannot establish an access rule without further evidence.

    For an invisible Abyss feather, the AION 2 Empyrean Trace map does not supply a verified universal explanation. Do not convert a single missing observation into a definite quest lock, rendering bug or server issue. Record the marker, region, approximate time, character context and what you could inspect. If multiple visits reveal the same mismatch, preserve those observations for a focused review.

    Use the correction form on the selected point to download a report with its identity and data version. Add a screenshot showing surrounding terrain and the relevant game version. The form saves a report file rather than automatically sending it. This lets you review the evidence before sharing it with the maintainer.

    Keep a reliable record between sessions

    The AION 2 Empyrean Trace map saves progress locally in this browser and uses the same intended location identities across English, Brazilian Portuguese and Spanish. Changing the website language does not create another copy of a trace. Changing browser profiles or devices, however, does not bring your checks with you automatically. Use the export and import controls to transfer a compatible backup.

    Save a fresh file after finishing a region or resolving a difficult group of points. Give the file a name that helps you identify its date and character context. A marker link can preserve a position for discussion, and a route link can preserve a plan, but neither replaces your collection backup. Before importing another file, keep a copy of the current state in case the older checklist is not the one you intended.

    Questions

    Does 100% prove that my game collection is complete?

    No. It means every trace represented by the selected regional dataset has been marked. The site cannot audit your character or establish that no source placement is missing. Compare the scope of the website count with the in-game collection before treating them as equivalent.

    Are feathers and cubes the same checklist?

    No. Empyrean Traces are treated as one-time collection entries, while cubes are repeatable search locations. Mark a trace after collection and use a cube check to record a visit. Their progress meanings should remain separate.

    Why did a trace vanish after I marked it?

    If hide found is active, collected positions are removed from the visible results. Turn that option off to inspect or unmark the point. This changes your display; it does not delete the underlying source record.

    Can the map explain every invisible Abyss feather?

    No verified universal explanation is available here. Check region, point identity, height and prior collection first. Report a persistent mismatch with a specific marker and supporting evidence instead of assuming a universal quest requirement.

    Related pages

    Explore other regions

    Sources