Mining the Aion 2 Client: What We Can (and Can't) Know
How Aion2.gg extracts its database from the Aion 2 TW client — what client data reliably tells us, what stays server-side, and how future patch diffs will work.
On this page
This explainer was written in July 2026 against the Taiwan client 1.0.38. The method is unchanged, but the source is now the EU/NA client 2.0.3.0 (Steam app 4972320), in eight client languages. The changelog lists what the EU dataset contains.
Every number on this site should be checkable. This explainer documents where our data comes from, what it can and cannot prove, and how we will report changes between client versions — so you never have to take a stat on faith.
Where the data comes from
Aion 2 (like most Unreal Engine games) ships its game rules as structured data tables inside the client: item stats, skill scaling, drop tables, enchant costs, quest chains, spawn placements. Our importer reads the Taiwan client v1.0.38.0 pak files and decodes those tables into a database of 178 tables — the same source of truth the game client itself renders from.
That means our numbers are not crowdsourced, scraped from screenshots, or estimated from kill logs. When an item page says a stat value or a drop probability, it is the literal value the client carries.
What client data reliably tells us
- Definitions — every item, skill, NPC, quest, recipe, title and status effect, with exact stats, scaling and costs.
- Loot structure — which reward tables reference which items and at what listed probabilities, including pity ("ceiling") counters on dungeon reward cubes.
- Economy rules — enchant success chances and material costs per step, crafting trees, vendor price lists.
- World layout — 189,458 placed spawn points powering the interactive map: mobs, gather nodes, reward cubes, named bosses.
- Schedules as rules — event cadences and season calendars are stored as recurrence rules (TW server time). We label these as TW throughout: EU/NA will run their own calendar.
What stays invisible to us
Honesty requires the flip side. Client data cannot show:
- Server-side tuning. Live drop-rate multipliers, event bonuses or hotfix nerfs applied on the server without a client patch will not appear in our data.
- Unreleased-content status. Data can exist in the client and be disabled server-side. We flag content that looks gated (for example, the empty Mythic rarity tier at v1.0.38) instead of presenting it as live.
- The live economy. Auction prices, server population and rankings are runtime data — tools on this site that involve prices use your own inputs, clearly labeled.
- EU/NA specifics. Until a western client exists, everything here describes the TW build. We never present TW dates, prices or rates as EU/NA facts.
How patch diffs will work
Our import pipeline records every run in a manifest (version, region, timestamp). Today it holds one game version — 1.0.38.0 — so there is nothing to diff yet. When the next TW client build ships, we will:
- Retain the v1.0.38 database as a frozen baseline.
- Import the new build into a fresh snapshot.
- Compute a field-level diff — added, removed and modified entities, down to the individual stat — and publish it as a browsable change list with links to every affected entity page.
That turns patch notes from hand-written summaries into verifiable data: instead of "some skills were adjusted", you will see exactly which skill changed, from what value, to what value.
Corrections
If you find a number on this site that disagrees with in-game behaviour, the likeliest causes are (in order): server-side tuning we cannot see, a display convention (we document our rarity naming and percentage handling), or a genuine bug in our pipeline. We would rather fix it than argue — tell us on Discord.