Conquest of AzerothCore: A Public Test Realm That Publishes Its Own Bug Count
By Indie Kings | October 21, 2026
Updated October 21, 2026: Conquest of AzerothCore is a public bug-test realm for the AzerothCore emulator core, and its website treats bug fixing as the product. The site's own tracker API reports 3,859 fixes against 6,983 reports since September 7, 2026, with 1,300 commits, 1,254 pull requests and 56 contributors. The GitHub repository behind it, jealous-sound/azerothcore-wotlk-coa, had 272 stars and 193 forks at the time of check, and GitHub counted 1,564 open items against it once its open pull requests are included.
What makes it unusual is the disclosure. The front page says, in its own words, that this is testing only, that accounts and characters and progress can be wiped at any time without notice, and that it is not a permanent or live server. The site publishes a live changelog written from the development commits, a roadmap with per-day fix counts, a mirror of the GitHub issue tracker, an Armory that ranks characters by class, and a talent calculator for every class. It is a private server project that shows its own bug backlog as a feature.
Image: the Conquest of AzerothCore social card. Image credit: coa-development.org.
What the site actually is
Conquest of AzerothCore describes itself as a public bug-test realm for the AzerothCore emulator core. AzerothCore is the open-source server emulator that the large World of Warcraft private server community runs on. This project takes that core, adds a large layer of custom content on top, and then runs the result as a place where players are expected to break it.
The site's own warning is the clearest statement of purpose anywhere in the project, and it is worth reading in full rather than skimming:
Conquest of AzerothCore is a public bug-test realm for the AzerothCore emulator core. It exists purely to help find and fix bugs before changes ship. It is not a permanent or "live" server. Because of that, accounts, characters and progress on this realm can be wiped or reset at any time, without notice, whenever it's useful for testing. Please don't treat anything you build here as permanent.
That is a deliberate trade. The team gives up the retention that makes a private server worth joining and gets something more valuable in exchange: a large, motivated group of testers who are already logged in and already have characters. A confirmed bug report counts towards a Bug Hunter badge in the site's Armory, and the top testers panel ranks players by confirmed and fixed reports, with a currency called Groot Coins attached to the leaderboard.
Behind the site sits a fork of AzerothCore maintained under the GitHub account jealous-sound. The repository description is simply "Conquest of AzerothCore", the language is C++, and the licence is GPL-2.0. The account also hosts smaller pieces: a volumetric fog and light shaft project for the 3.3.5a Direct3D 9 client with 24 stars, a bug-report helper, and forks of the playerbots module and a project called Ascension Extensions that reconstructs a DLL function by function.
| Item | Detail |
|---|---|
| Project | Conquest of AzerothCore, a public bug-test realm for the AzerothCore core |
| Repository | jealous-sound/azerothcore-wotlk-coa, C++, GPL-2.0 |
| Stars and forks | 272 stars, 193 forks, and 1,564 open issues and pull requests at check |
| Repository created | September 7, 2026 |
| Last push | October 21, 2026 |
| Client | World of Warcraft 3.3.5a, build 12340 |
| Realms listed | Conquest of Azeroth, Wildcard, Warcraft Reborn, Area 52, Freepick, Hero |
| Test policy | Accounts, characters and progress can be reset at any time |
The numbers, straight from the API
The site publishes its own metrics as JSON, which makes verification unusually easy. The roadmap API reports the following totals at the time of check.
| Metric | Value |
|---|---|
| Fixed | 3,859 |
| Reported | 6,983 |
| Still open | 1,516 |
| Closed as other | 1,608 |
| Commits | 1,300 |
| Pull requests | 1,254 |
| Contributors | 56 |
| News posts | 47 |
| Days tracked | 45, from September 7, 2026 |
| Best single day | 461 fixes on September 21, 2026 |
The bug API adds the split between the two trackers. It reports 1,517 confirmed bugs, 3,860 fixed and 355 fixed in the last week. On the GitHub side it reports 1,516 open issues, 3,794 fixed and 600 listed, and it links most website reports back to the GitHub issue they came from, with two placeholder entries that carry no link.
The changelog is generated from the development commits, one entry per day, and the pace is visible in the feed. October 20 recorded 57 changes, October 19 recorded 63, October 18 recorded 76, and October 17 recorded 51. The largest day in the feed is October 7 with 141 changes. The entries are not release notes in the marketing sense. They read like a work log, and the October 21 entry was still filling itself in as we checked, adding tooltip text fixes on the Starcaller and a fix that lets Lunar Cascade mark full-health allies.
Not every entry is a bug fix. A standalone October 17 post announced Manastorm Endless, an SQL-driven endless dungeon mode with floor-by-floor progression, gadgets, affixes and depth-scaled rewards, narrated by Millhouse Manastorm. It requires level 10 or above, works solo or with a party of up to 5, and is entered with a command or through a native queue in the client.
The website as a bug dashboard
Most private server sites are marketing pages. This one is closer to a status page with a game attached.
The realm status page polls every 30 seconds and keeps 30 days of history, with a stated rule that a break of up to 15 minutes counts as a restart and anything longer counts as an outage. It tracks the login server separately from the realms, because a realm can be up while nobody can log in. When the site was checked, three realms answered, with player counts moving minute to minute: CoA with 31 players, Warcraft Reborn with 10 and Wildcard with 3. The site states plainly that bots and game masters are not counted.
The changelog page carries filters for realm, for class, and for fix versus new, with a class picker that filters the whole history down to one class's changes. The roadmap page archives every week and every month, with a running total of fixes, and it keeps two hours of finished periods as they were so later edits to the changelog do not rewrite history.
The known bugs page mirrors the GitHub tracker and adds a website-reported layer on top, with a search box and filters for all bugs, not fixed and fixed. The Armory looks up any character on the realm and shows gear, stats, professions and achievements, and its leaderboard API returns the top character per class at a maximum level of 60, along with achievement counts, top professions, guild sizes with average levels, and the top bug hunters with their report counts. The talent calculator is per class, with one specialization and the class tree, and it produces a shareable link.
Account features are the sort a hosted service would have and a home-kept server usually would not: two-factor authentication with an authenticator app, recovery codes, a bug reporting panel inside the account page, and a message when the realm still thinks an account is online after a crash.
The class roster and where it came from
The site's own metadata advertises 21 custom classes, and the class roster echoes the 21-class Conquest of Azeroth roster this site covered on October 17, with the same named classes such as the Necromancer, the Chronomancer and the Runemaster. The two projects are run by different maintainers, and this is a different deployment: the October 17 coverage described a Phase 1 launch with a level 20 cap, while this is a bug-test realm for the AzerothCore core, running three live realms and a 60 level cap.
The site ships a class map in one of its JavaScript files, and it says where it came from: extracted from the custom client DBCs for characters, classes, races and areas, and regenerated when those change. That map holds 32 class IDs in total. Ten of them carry the stock 3.3.5a names, from Warrior through Druid, and the remaining 22 are custom, running from Hero and Barbarian through Witch Doctor, Felsworn, Witch Hunter, Stormbringer, Knight of Xoroth, Guardian, Templar, Bloodmage, Ranger, Chronomancer, Necromancer, Pyromancer, Cultist, Starcaller, Sun Cleric, Tinker, Venomancer, Reaper, Primalist and Runemaster, each with its own colour. That is one more custom class than the site's own 21 headline figure, which is the kind of gap a changing roster produces.
The client also carries extra races in the same map, including Zandalari Troll, Worgen, Kul Tiran, Vulpera and Pandaren, plus a long tail of custom identifiers such as Thin Human, Fel Orc, Naga, Broken, Skeleton, Vrykul, Tuskarr, Forest Troll, Taunka, Northrend Skeleton, Ice Troll, Drakkari Troll, Leper Troll and Troglodyte.
The changelog shows what a class roster like this costs in maintenance. The October 21 entry alone carries Starcaller fixes, including tooltip text for the Scattered Stars effect in Aspect tooltips, Lunar Cascade marking full-health allies, an explanation of Eclipsing Arrows inside Stellar Convergence, restoring the visible healing area of Elune's Cradle, and keeping the Nightborne Armaments buff off above 35 percent health. The October 20 entry, all 57 changes being fixes, ranges across vendor gossip, creature spawns, a Crossroads dungeon, item vendor scaling, and a set of class-specific corrections.
Why a test realm tells you to expect a wipe
The FAQ is unusually blunt about the deal. It says to expect bugs, restarts and changes, and that restarts are announced in the site banner and on Discord. It says the launcher is not signed with a code-signing certificate, so SmartScreen will warn, and that antivirus products that flag file-patching launchers are a common false positive, with instructions for restoring the file and for excluding the game folder rather than switching protection off. It says the game needs a Wrath of the Lich King 3.3.5a client, build 12340, and that other versions cannot log in.
It also says that if a game is still downloading from the launcher, the client files may not match the realm, so the launcher should be run again, the cache folder deleted, and addons disabled for a moment to rule them out. The site also warns that school, work and hotel networks block game ports, and that a firewall rule for the game's executable may be needed.
One detail stands out: the front page still says the launcher download link is coming soon, even though the FAQ and the step-by-step guide both point at a launcher. Anyone planning to test this needs to check whether the download is live before they start.
FAQ
What is Conquest of AzerothCore?
A public bug-test realm for the AzerothCore World of Warcraft server emulator, run from the GitHub fork jealous-sound/azerothcore-wotlk-coa. It exists to find and fix bugs before changes ship to the wider private server community.
Can I keep my character there?
Do not plan around it. The site says accounts, characters and progress can be wiped or reset at any time without notice, whenever it is useful for testing, and tells players not to treat anything they build as permanent.
What client does it need?
World of Warcraft 3.3.5a, build 12340, per the FAQ. The launcher adds the project's files on top of that client, and other client versions cannot log in.
How do I report a bug?
Through the Bug reports panel in My Account, or as an issue on the GitHub tracker. Reports the team confirms or fixes count towards the Bug Hunter badge in the Armory.
Is my bug already known?
Each class page lists the open issues for that class, the changelog records what was fixed, and the known bugs page mirrors the full GitHub tracker with filters for all bugs, not fixed and fixed.
Does it cost anything?
The site does not publish a price. The related CoA Server Manager project this site covered in October was community tooling for a private server, and this repository is licensed GPL-2.0.
Our take: Publishing your bug count is unusual and it cuts both ways. It proves the project is doing real maintenance work at a real pace, and 3,859 fixes in 45 days is not a rounding error. It also tells any prospective player that this is a laboratory, not a destination, and the wipe policy makes that unambiguous. For a community that has spent years watching private servers promise permanence and deliver chaos, that honesty is worth more than a player count.
Bottom Line
Conquest of AzerothCore is a GPL-2.0 C++ fork of the AzerothCore emulator core, maintained at github.com/jealous-sound/azerothcore-wotlk-coa, that runs a public bug-test realm for its own project on a site that publishes its own bug backlog. Its tracker API reported 3,859 fixes against 6,983 reports since September 7, 2026, with 1,300 commits, 1,254 pull requests, 56 contributors and a best day of 461 fixes. The repository had 272 stars and 193 forks at the time of check, and the site's mirror of the GitHub tracker listed 1,516 issues still open. The site advertises 21 custom classes, mirrors the GitHub tracker, and states plainly that accounts and characters can be reset at any time.
Sources
The Conquest of AzerothCore website at coa-development.org, including the front page, the FAQ, the known bugs page, the roadmap, the changelog and its RSS feed, verified October 21, 2026.
The site's own JSON endpoints for server status, bug tracking and the roadmap, and its class map script, for the totals, the per-realm player counts, the leaderboards and the class and race names, verified October 21, 2026.
GitHub repository metadata for jealous-sound/azerothcore-wotlk-coa, verified October 21, 2026: 272 stars, 193 forks, C++, GPL-2.0, created September 7, 2026, last push October 21, 2026.
Related: Conquest of Azeroth: 21 Original Classes Headline a Launch Capped at Level 20 | Run Your Own Conquest of Azeroth Server in 5 Clicks: CoA Manager [2026]