Where locations come from
The current dataset, aion2-demo-v1, contains 24 original interface fixtures: 12 for each sample region. Coordinates use a 0–100 illustrative plane. Region names provide interface context; settlement labels, terrain, paths and pin positions are not game geography. No competitor’s coordinates, screenshots or map tiles are included.
| Material | Origin & scope | Status |
|---|---|---|
| Site foundation | AstroWind by arthelokyo, MIT-licensed template | Used; original license retained |
| Terrain & markers | Original SVG schematic and synthetic UI fixtures | Demonstration only |
| In-game entrances & coordinates | No authorized, verified dataset supplied | Not published |
| Guide context | Linked community reports and resources below | Reported observations; not site-tested mechanics |
What we have checked
The interface is designed for filtering, location details, local checklist states, backups and shareable views. That is separate from checking a location in the game. A future verified location needs a stable ID, coordinate system, real basemap, source permission, client, region, approach evidence and verification date.
Future evidence labels should distinguish a community report, imported file record and site-tested route. “Verified” must mean a documented check against a named client; a data file’s existence alone is not enough.
Community references
- Player difficulty locating hidden cubes — supports the need for better approach notes.
- Corpus hidden-cube map resource — external comparison for group-based presentation.
- Missing feather in Western Gribade — a reported navigation issue.
- Collected-feather filtering discussion — a filtering request.
- Abyss feather sync question — an account-state question, not a verified workaround.
These references came from the project research dated 19 October 2026. We do not claim that they have been reproduced in a current client or that their content remains unchanged.
Client versions and availability
Global and Asian clients must be checked separately. We do not currently publish release timing, opening rules, collection totals, spawn timers or account-sync behavior. External maps can have different coverage and licenses; their presence on the web does not grant permission to republish their data.
Corrections and change history
19 October 2026: initial schematic preview, two sample regions, two layers and browser-local progress. No real-location verification is claimed.
Use the correction report builder to describe a data issue. The current builder downloads a report locally; a direct delivery channel will appear only when configured.