Aion 2 guide hub

Builds, pets, crafting, map routes and database guides

Practical AION 2 guidance connected to the database: 14,096 item records, 227 pets, 330 indexed player skills and every major planner in one place.

Guide

AION 2 builds

Start with class role, weapon slot and fixed gear stats, then layer skills, pets, Daevanion, Pantheon and buffs only after the base equipment is stable.

Build Planner
Guide

AION 2 classes

Use database records as starting evidence, then confirm region-specific behavior in the current client before publishing hard claims.

Class guides
Guide

AION 2 pets

Pet progress is long-term: separate ownership, individual Understanding and genus options before deciding what to farm.

Pet Collection
Guide

AION 2 crafting

Crafting is best planned backwards from the final item so direct materials and intermediate craftables are not double-counted.

Crafting Calculator
Guide

AION 2 enhancement

Enhancement value depends on item grade, item level, success cost and whether Soul Binding lines can change the final comparison.

Enhancement Calculator
Guide

AION 2 interactive map

Map usage is strongest when database pages link to the exact monster, gathering node, quest or event marker instead of forcing players to search twice.

World Hub
Guide

AION 2 event timer

Use database records as starting evidence, then confirm region-specific behavior in the current client before publishing hard claims.

Event Timer
Guide

AION 2 item database

Use database records as starting evidence, then confirm region-specific behavior in the current client before publishing hard claims.

Item Database

Frequently asked questions

What should I use first in AION 2?

Start with class and item pages, then move into the Build Planner once you know your weapon, role and gear slot priorities.

Are these guides copied from another wiki?

No. The guide text is original and is connected to local database records, official client exports and internal tool outputs.

Why do some records still show internal names?

Some localized string tables are still blocked by the current client encryption. When that happens, the database keeps the official ID and internal key instead of inventing a name.