Building PLAYER'S CODEX: an AION 2 guide you can actually use
How I turned a collection of AION 2 research into a bilingual guide with an interactive map, skill reference and animated boss mechanics.
There are plenty of game guides that tell you what to do. I wanted to make one that helps you see what to do.
That’s the idea behind PLAYER’S CODEX, an independent English-and-Korean game guide platform. AION 2 is its first game hub. Instead of putting everything into a long wall of text, I organized information into tools you can open while figuring out your next step in the game.
It’s already available to use in a browser. Here’s what went into building it, and what still needs improving.
Starting with a different kind of guide
When looking through game tips, a practical problem kept coming up: a useful answer might be buried inside a video, a discussion in Korean, a detailed table or a page aimed at someone with more experience.
I broke the site into a few questions a player can ask right away:
- Where should I go after the story?
- Which class and skills should I look at?
- Where is the quest, dungeon or travel point I’m trying to find?
- What happens when this boss shows a particular attack cue?
That led to separate beginner, endgame, skills, map and dungeon sections, rather than one crowded page.
Try it: Open PLAYER’S CODEX · Starting guide.
A map should be something you can use, not just look at
The interactive map is one of the parts that makes the project feel like a small application rather than an article.
Its published implementation documents 384 quest, travel and dungeon markers across four regions. You can move and zoom the map, search for locations, inspect markers and keep track of completion locally in your browser.
The interesting engineering choice here is that it works as a two-dimensional web map. It doesn’t need a heavy 3D scene just to help someone find a waypoint. Some background map tiles and location data are attributed to external sources, rather than represented as original game assets.
Try the feature: Explore the AION 2 map.
Animating a boss mechanic instead of describing it three times
A boss guide often tells you to move left, stand behind the boss or avoid a marked area. Those words are helpful, but a small animated diagram can make the sequence clearer.
The published guide contains 16 animated mechanic lessons across six dungeons. Its diagrams focus on the cue, the required response, where to move and what a failed response looks like. You can pause, replay, scrub and change playback speed, which matters when you are learning rather than simply watching.
The diagrams use original SVG-style representations; they are explanatory animations, not captured game footage or measured distances. That distinction is important. A simplified animation can teach a concept, but it should never pretend to be proof that a mechanic has been tested in the live game.
Some supporting sources were created for Korean or other regional editions. Where global-version behaviour hasn’t been verified, the guide is meant to mark that uncertainty instead of silently presenting it as fact.
Try the feature: Browse the boss and dungeon guides.
Building the skill library
The skill reference covers a documented set of 280 base skill entries across eight classes, with bilingual terminology and class-oriented navigation.
One detail that took deliberate care was separating a translated explanation from an official in-game string. Korean community advice may contain useful concepts, but the Korean recommendation is not automatically a tested optimal build for the global client.
I’d rather show the source and its applicability than label an unmeasured setup “best in slot”.
What I used to build the site
The public repository explains the workflow: Python source modules organize the guide content and diagrams, a build script generates static HTML pages, and the published output is deployed through GitHub Pages.
The website uses JavaScript for interactions such as map controls, class exploration and boss-animation playback. Saved checklist state stays in browser storage; no visitor account is required to try those features.
Static generation was a deliberate fit for a guide like this: each topic has its own address, search engines can read the content and the pages do not need a paid server to answer every visit.
The less glamorous work is validating that the generated pages, language links, source attributions and browser interactions all stay consistent as the site changes.
What still needs work
It is an independent, AI-assisted guide—not an official NC site or a claim that every mechanic was verified through my own live play. The repository openly tracks those limits. New patches and regional differences can make a recommendation stale.
The next meaningful improvement isn’t more words for their own sake. It’s better evidence: real, permission-cleared gameplay clips, version-specific demonstrations and corrections based on actual testing.
If you’d like to see what currently works, visit PLAYER’S CODEX, then try a map marker or pause a boss animation yourself.
Independent fan-made guide. AION 2 and associated game assets belong to their respective rights holders. The guide’s linked third-party material remains with its original sources.