Will Classic+ be announced at this year’s BlizzCon on September 12 and 13? With about a month to go, the massive Camelot datamine remains the strongest evidence that a major new Classic project exists. Last week, however, we saw unusual movement in Blizzard’s internal development setup, suggesting that work on Camelot is continuing ahead of BlizzCon.
Blizzard Deploys First Build to wowdev5
Blizzard’s public product manifests offer a rare glimpse into its internal development setup. Last week, a channel called wowdev5 received its first publicly recorded game build:
According to BlizzTrack’s manifest timestamps, Blizzard deployed Patch 1.15.9 to wowdev5 and switched it to Patch 1.60 less than two hours later – the patch level associated with Project Camelot!
Before this, wowdev5 had never carried a publicly recorded game version. The channel’s CDN-manifest history shows its first signs of life on December 20, 2024, followed by two further CDN-only updates in 2025. Its first publicly recorded version deployment only happened last week.
Similarities Between wowdev2 and wowdev5
wowdev2, Blizzard’s established internal environment for Camelot builds, has carried Patch 1.60 since October 24, 2025.
Five months earlier, on May 27, the Classic team explicitly said that it had decided to begin work on its “next major project in the original WoW design space.” Why Blizzard needs a second deployment environment carrying the same version as wowdev2 remains unclear – the timing is certainly intriguing.
The situation is different from last year’s Gamescom, when an 11.2.7 SHOW realm tied to wowdev3 appeared before the Housing demo became playable on the Gamescom show floor. The timing of the wowdev3 updates and the Gamescom-exclusive realm created a strong connection between the two. A similar signal could still appear for wowdev5 in the near future.
(Image by Marlamin)
Why Classic+ at BlizzCon Is Still a Possibility
So far, we have seen no SHOW realms or other public signals indicating that wowdev5 is being prepared for BlizzCon. Its activation six weeks before the event could be preparation for a public demo – or simply additional internal QA, regional testing, or environment isolation.
Ultimately, the manifest data establishes one thing: Blizzard now has two separately configured deployment environments carrying the same 1.60.0.69075 version, build ID, and CDN configuration. In the publicly visible manifest history, this appears to be the first time the same Classic build number has appeared simultaneously on two separately numbered wowdev products.
If Blizzard were preparing a BlizzCon demo, a second deployment environment would certainly be useful: one could remain in active development while the other was stabilized for the show floor. For now, however, that remains speculation.
