No. XLGAMES develops ArcheAge Chronicles, and the November 2, 2026 Steam listing also names XLGAMES as its publisher. Pearl Abyss is not listed as the developer or current Steam publisher for this game. The official Chronicles website identifies XLGAMES as well.
The relevant change is self-publishing: XLGAMES announced that it would publish Chronicles directly. That announcement changes how the development team describes responsibility for delivering the game and communicating with players. It does not announce a transfer of development to Pearl Abyss.
Confirm that you are checking the right game
Use the full title ArcheAge Chronicles when checking a company credit. Searching for ArcheAge alone can lead to the original game, an older service, a private server, or a discussion covering several different projects. A company named beside one of those results does not automatically belong to Chronicles.
The Chronicles Steam App ID is 3218230. The current developer and publisher fields on that product both read XLGAMES. Matching the product identifier is particularly useful when a page title has been abbreviated, translated, or shortened in a screenshot. It gives you a second identity check beyond recognizing the game's logo.
The official website provides another check: its company information identifies XLGAMES Inc. Use that together with the product credit rather than relying on a search-result thumbnail. The company responsible for a website article, a video upload, or an advertisement may be the publisher of that piece of media, not the developer of the game it discusses.
Read the developer and publisher labels separately on the correct product.
Developer and publisher describe different responsibilities
A developer credit identifies the studio making the game. A publisher credit identifies the organization listed for publishing that product. The same organization can hold both roles, as XLGAMES currently does on the Chronicles Steam listing. Reading the two fields separately prevents a publishing update from being mistaken for a change in the studio making the game.
Self-publishing is the useful term here. The producer's update says XLGAMES will handle Chronicles directly rather than leaving the publishing role separate from the development team. The stated aim includes more direct responsibility for service and communication with players.
| Label you encounter | What it answers for Chronicles | What to check |
|---|---|---|
| Developer | Which studio is credited with making the game | XLGAMES on the current product listing |
| Publisher | Which organization is currently listed for publishing it | XLGAMES on the same Steam product |
| Official website company information | Which company identifies itself on the game's website | XLGAMES Inc. |
| Video uploader or article author | Who published that particular piece of media | The account or byline, separately from game credits |
These labels are useful because a single search page can display all of them together. Read the label attached to a name before deciding what relationship that name establishes.
What the self-publishing announcement actually changes
The September publishing update presents XLGAMES self-publishing as a deliberate decision. It describes the team taking responsibility for both development and service, making communication more direct, and using player feedback while preparing for Early Access. That is a statement about the operating approach for Chronicles.
The Global Project Manager's introduction reinforces the communication side of the change. Don describes bringing players more insight into development and bringing their feedback back to the team. For a player, that makes the official development updates useful places to understand what XLGAMES says it is prioritizing.
Neither statement supplies a basis for replacing XLGAMES with Pearl Abyss in the developer field. Nor should you read a company credit as a guarantee that a particular requested feature, balance change, or support outcome will happen. Studio identity tells you who is making the commitment; the contents and timing of each commitment still need to be read individually.
Read older announcements in their original context
Chronicles has been discussed across several development stages. A reveal announcement, a network-test notice, a demo update, and an Early Access listing answer different questions. When an older article names a company or target date, check which stage it describes before using it as a current product summary.
The 2024 PlayStation reveal is historical material. It can establish what was announced at that time, but it does not override a later self-publishing statement or the current Steam publisher field. A reader looking for today's publishing identity should prioritize the later explicit update rather than choosing whichever company name appears first in a search result.
Keep the date attached to the statement you are evaluating. The date a search engine retrieved a page is not necessarily the date the underlying announcement was written. Likewise, a newly uploaded discussion video may be describing an older reveal. What matters is when the actual company statement applied and whether a later statement changed it.
Separate studio identity from comparisons with other games
Comparisons can help describe how a game looks or feels, but they are not company credits. An article can compare combat, presentation, or open-world exploration across several games without establishing that the same studio makes them. Treat a comparison as a description of the author's experience or expectations.
The same applies to a video that groups several upcoming games together. Names appearing beside one another in a title or thumbnail identify the subjects being discussed. They do not establish a shared development team, a publishing arrangement, or a transfer of responsibility between the companies involved.
If a claim says that Pearl Abyss is developing Chronicles, look for an explicit current credit or a dated announcement naming that relationship. A resemblance argument does not replace either. The current product credits support the direct answer: XLGAMES is the developer, and XLGAMES is the current Steam publisher.
Use the company credit to choose the right next action
For development priorities, look for a Chronicles update issued by the game team. Those updates explain the scope and timing of a change more directly than a general company comparison. A studio name alone cannot tell you whether an announced improvement belongs to the launch build or to a later update.
For a Steam purchase, confirm the exact product on the account you intend to use. The developer field helps establish identity, while the store's current availability and purchase information govern that transaction. The existence of a correct company credit does not mean the game has already unlocked.
For a gameplay problem, use the game's designated communication or support route and identify the relevant build. The official Discord and Steam Community discussions are named as feedback channels. A store credit is an identity check; it is not a promise that a particular employee reads every discussion or that a company mentioned in a comparison article can resolve an account issue.
Verify a company claim in a repeatable order
- Write down the exact game title attached to the claim. Keep Chronicles in the title so another ArcheAge product does not enter the comparison accidentally.
- Open the corresponding product listing and confirm App ID 3218230 when using Steam. This establishes that the credit belongs to this game.
- Read the developer field independently from the publisher field. Both currently name XLGAMES, but each field answers its own question.
- Compare the result with the official game's website identity. A matching company name across those locations provides a practical cross-check.
- If an article reports a change, locate the dated company statement it describes. Identify whether the change concerns development, publishing, service, or only a platform announcement.
- Keep historical and current statements separate in your notes. A later direct update can change the present answer without making the earlier announcement a statement about a different game.
This order is useful when a confident headline conflicts with the product listing. It narrows the disagreement to a specific field and date instead of turning it into a debate about visual similarities or unrelated projects.
Keep the release-stage question separate from the studio question
As of November 2, Steam lists Chronicles as coming soon to Early Access on November 3, 2026. That release-stage information sits alongside the XLGAMES credits, but it serves a different purpose. It describes planned availability, while the company fields identify who develops and currently publishes the product.
Consequently, confirming XLGAMES does not establish that the game is already playable, that a full-release build is complete, or that every feature mentioned in a development update has shipped. Use the release notice for availability and the relevant update for feature timing. Keeping those questions separate produces a more accurate answer than treating an entire store page as one undifferentiated promise.
When sharing the developer answer with someone else, the useful wording is precise: ArcheAge Chronicles is developed by XLGAMES, which currently also lists itself as publisher on Steam. Its self-publishing update explains the publishing direction. There is no supported basis in these current credits for attributing its development to Pearl Abyss.
Company names can also appear with different capitalization in a store credit and a signed message. XLGAMES and XLGames in these materials refer to the same credited studio; the typographic variation is not a second developer. Preserve the wording of the role when summarizing it, and avoid turning a formatting difference into a claim about a separate organization.