Building an ArcheAge Chronicles guide before the demo opens
How I expanded PLAYER’S CODEX, directed the AI work, published on GitHub Pages, and set up official-news checks every three hours—with a clear plan for future gameplay guides.
Last updated

Waiting for a new game usually means checking the official website, Steam announcements, and YouTube separately. Once a test opens, class explanations, early progression tips, and dungeon guides become another set of things to find. I wanted to build a home for that information before the ArcheAge Chronicles demo opened.
That became the ArcheAge Chronicles section of PLAYER’S CODEX. It is an early public guide with official video links, announced information, demo preparation notes, and an automatically refreshed official-news feed. Gameplay guides that still need testing are clearly presented as future work.
The cover is a screenshot of the public guide website taken on October 16, 2026. It shows the website I built, rather than gameplay. The captured page is the Korean edition; an English edition is available too.
First, give players a place to choose their game
The starting point was the existing AION 2 guide. I did not want every new game to leave visitors guessing which website to open, so I asked for one PLAYER’S CODEX hub that leads to a separate space for each game.
The main hub now has separate AION 2 and ArcheAge Chronicles cards. AION 2 opens its existing independent website. ArcheAge Chronicles opens the new section. This gives the brand a shared entrance while keeping each game’s information separate.
It also leaves room to add another game later without mixing its mechanics, maps, or news into an unrelated guide. The common part is finding your game; the useful details live inside that game’s own space.
What I actually asked the AI to do
I described the direction and requested changes through ChatGPT, and AI coding support helped turn those requests into pages and code. The table below summarizes the intent of the requests; it is not a reconstructed verbatim prompt transcript.
| My request | What it became |
|---|---|
| Let visitors choose a game from a shared PLAYER’S CODEX homepage | Separate game cards linking to the existing AION 2 site and the new ArcheAge section |
| There is not enough guide data yet, so link the trailers for now | Official video links alongside Steam and developer website links |
| Put the newer trailer first | A recent gameplay showcase leading the media section, with developer commentary and the original reveal identified separately |
| Keep collecting information when testing or release begins | Scheduled checks of the official Steam publisher feed and a dedicated news archive |
The work also included checking Korean and English routes, navigation on small screens, game-card links, and language switching. The most useful direction was deciding what the site should explain today and how it should label information we have not verified yet.
Where the site was made and how it is hosted
ChatGPT was the place for requirements and feedback. GitHub holds the code and its change history. The actual ArcheAge source is under player-codex/archeage-chronicles/ in the bumblev95/bumblev95.github.io repository. Like AION 2, it is operated through GitHub, although AION 2 has its own separate source repository.
| Tool or technology | Its role in this project |
|---|---|
| ChatGPT and AI coding support | Helping translate requests into page structure, code, and revisions |
| HTML, CSS, and JavaScript | Content, visual layout, responsive behavior, and status display |
| Python | Fetching and organizing official Steam announcements, then updating the news data and HTML |
| GitHub | Keeping source files and a history of changes |
| GitHub Actions | Running scheduled announcement checks and automated validation |
| GitHub Pages | Serving the public static website |
| Playwright and automated checks | Checking links, layout, and basic behavior at different screen sizes |
A static website serves HTML files that have already been prepared. The current guide does not require a dedicated always-running application server or a membership system. Scheduled news collection runs separately in GitHub Actions, which updates the files that Pages serves.
Built with BumbleV AI, where you are reading this article, is a separate promotional blog. Publishing a build journal here and deploying the game guide on GitHub Pages are different processes.
What visitors can use today
The current landing page brings together the official game website, Steam page, demo schedule information, official video links, recent publisher announcements, and the guide categories being prepared. The demo preparation guide organizes announced systems from developer communications and identifies things to check during play.
The video order is an editorial choice, rather than a single list sorted by upload date. A Quick Look at Auroria, a recent gameplay showcase, comes first. Developer commentary and the original 2024 announcement follow. A developer briefing can have a newer upload date while answering a different question from “What does the game look like now?”
The site links to the original providers instead of rehosting full videos or autoplaying them. Visitors can choose what to watch on the official platforms. The website has Korean and English navigation and explanatory pages; automatically collected news headlines and brief excerpts retain their original wording.
How the official-news automation works
The collector uses Steam’s public news API and accepts only this game’s official publisher announcement feed. GitHub Actions is configured to check every three hours. Scheduled jobs can be delayed, so this is periodic collection rather than a promise of immediate publication.
Each run checks the game identifier and feed, removes duplicates, and stores the publication date, original source link, and a short excerpt. The landing pages highlight the latest three announcements. The official-news archive provides access to more items. When publisher content changes, the workflow records the update in GitHub and explicitly requests a Pages build.
There is also a public-site check: it looks for the newest announcement’s identifier and individual source link on the published pages. A successful fetch alone is not enough to show that visitors received the update. If the external API fails, the job records a failure and preserves existing news. On October 16, I also checked that the newest collected announcement appeared on the public landing page.
This automation has a specific scope. It does not indiscriminately collect community posts, YouTube comments, or players’ personal data. An official announcement is evidence of what the publisher said; it does not independently verify damage numbers, boss behavior, or the quality of a build.
What I want to add after testing begins
The current release establishes the entrance, source links, preparation notes, and official-news flow. The next goal is to turn verified play observations into guides that help a beginner decide what to do next.
I want to start with class and weapon tooltips, early quest progression, and the places where new players get stuck. Combat notes should explain dodge, parry, and skill combinations with recorded context. Maps should contain locations and routes that have been checked. Dungeon guides should connect an observed boss cue to a useful response.
Interactive tools or explanatory animations may help later, drawing on the approach used for AION 2. These are possible additions, not completed ArcheAge features. The current section does not contain a finished skill database, measured DPS rankings, verified resource coordinates, or boss-pattern animations.
As guides grow, the source and tested version need to travel with the explanation. A test build can differ from the eventual release, so maintaining the site will include revising older pages as well as adding new ones. Automatic announcement collection can support that work, but gameplay conclusions still need evidence and review.
AI makes it easier to produce code quickly. This project has also made the direction of that work more concrete: show useful material that is available now, and build a structure that can accept checked information later. That was the purpose of starting before the demo rather than filling a guide with guesses.
You can explore the current ArcheAge Chronicles guide, choose a game from PLAYER’S CODEX, or read the earlier AION 2 build journal for the background to the wider project.
PLAYER’S CODEX is an independent fan project and is not affiliated with the developer or publisher. Game and video rights remain with their respective owners. Publisher announcements and independently checked gameplay findings are identified separately.
Sources & further reading
- https://bumblev95.github.io/player-codex/archeage-chronicles/
- https://github.com/bumblev95/bumblev95.github.io/blob/main/player-codex/README.md
- https://github.com/bumblev95/bumblev95.github.io/blob/main/player-codex/scripts/sync_official_news.py
- https://github.com/bumblev95/bumblev95.github.io/blob/main/.github/workflows/archeage-official-news.yml
- https://steamcommunity.com/app/3218230/allnews/