AION 2 Monolith Locations

What Is Confirmed About Monoliths

NC’s Chapter 1 update confirms that Monoliths exist in the operating Korean and Taiwanese version and can provide growth rewards. This is direct evidence for the system name in an English NC news release. It does not include a coordinate table, route, prerequisite list, or map screenshot.

Steam describes a large global world built around exploration and flight, but it does not name Monoliths or locate them. Combining those two facts can show why a future location guide needs navigational context, yet it cannot place a marker. Every location row therefore remains TBD until observed in the global client.

The regional system may be relevant to future global progression, but its launch status is not confirmed in the reviewed global material. A page can responsibly exist now as a verification ledger and update destination. It cannot responsibly pretend to be a completed walkthrough.

Why This Page Does Not Publish a Map Yet

The collected P0 source supplies no map, coordinates, named regions, or approach path. Two directly related community videos were accessible as leads, but neither provided a usable verified transcript and one offered no location detail in its description. Their titles alone cannot support a route.

Copying coordinates from another region also risks wrong English names, different terrain states, different prerequisites, or a changed object layout. A marker can look precise while sending players to the wrong place. Precision without a reproducible source is more harmful than a visible TBD.

This page uses official screenshots only as atmosphere and labels them accordingly. No landmark in those images is identified as a Monolith. The first real map image must come from a traceable global-client capture with region, patch, and route evidence.

How Each Location Will Be Verified

A valid entry needs the global English region name, nearest official map label, visible Monolith, and a repeatable start-to-finish route. It should also record faction, story state, level or content requirement, flight dependency, and any interaction prompt shown by the client. If one field is unknown, it is labeled TBD rather than left blank.

The route should be tested from a stable landmark instead of relying on a floating coordinate alone. Screenshots need accurate alt text and a caption stating that they come from the global client, along with the capture date and patch. A second pass should confirm that the object remains available under the stated conditions.

Reward evidence must be captured separately from navigation evidence. NC confirms growth rewards regionally, but the global reward name, quantity, reset behavior, and account scope may differ. A route is not proof of a reward table unless the corresponding result screen is also verified.

Planned Location Entry Format

Each future card will begin with region and sub-area names copied from the global English map. It will then list the nearest stable landmark, prerequisite, and a short route written from that landmark. Coordinates will be included only if the global client displays a coordinate system that can be reproduced.

The next block will identify whether the route uses walking, gliding, flight, an instance entrance, or another confirmed traversal method. It will describe obstacles only when they are directly observed. General Steam language about flight cannot prove that a specific Monolith requires it.

The final block will show the interaction result and verified reward status. A “not found” report will include patch, faction, and prerequisite context rather than declaring the location removed. This structure supports future corrections without silently mixing regional versions.

What Players Can Check Safely

If you are in the global test or live client, first confirm that the interface itself uses the word Monolith. Record the English region, map label, quest state, and visible prompt before interacting. Do not spend a rare item or trigger an irreversible action merely to fill this guide.

Capture a wide map view, a local landmark view, and the object itself so another player can reproduce the route. Remove personal account details from any shared capture. A single cropped marker without context is not enough to validate a location.

Compare the result with the current global patch rather than a Korean or Taiwanese video date. If the object is absent, report the conditions instead of assuming the guide is wrong or the content is removed. Version boundaries are part of the evidence.

Regional Version Boundary

The Chapter 1 article describes a live-service update for Korea and Taiwan, including Monoliths, Stigma level changes, Brawler, and other regional progression content. The global launch materials separately confirm an eight-class PC release. Those contexts must remain distinct on every location entry.

A regional location can be a candidate for testing, but it cannot be written as a global destination before verification. English translations can also vary from official localization. The final guide will use client strings rather than fan translations for names and prompts.

This page was last checked August 30, 2026, before the October 5 global launch. Its pending state is intentional and should not be replaced by filler coordinates. When global routes are confirmed, they can populate this URL without creating competing pages for the same search intent.

Official World and Flight Footage

This verified official trailer provides global world imagery, not a Monolith route. No visible object in the footage is labeled as a Monolith on this page. Location claims will come only from a reproducible global-client map and route.

Location Ledger Awaiting Global Verification

Every practical field is still open because the official regional news confirms the system, not its global navigation. Empty values are displayed as TBD to prevent map-shaped guesswork. The ledger will be filled only from the global English client.