Nobody Announced It. A Bot Caught Blizzard's Unannounced Warcraft Build Leaving the Building at 05:23 UTC.

Nobody Announced It. A Bot Caught Blizzard's Unannounced Warcraft Build Leaving the Building at 05:23 UTC.

Riot MMO · News · August 7, 2026 · By entgrove
RumorRiot MMOWorld of WarcraftDatamineProject CamelotMMO Development
Heads up: the news here is real and sourced. The read on what it means for the unannounced Riot MMO is ours, and speculative where labelled. RuneGrove covers everything through one lens: what it tells us about the MMO.

Source: Wowhead. Verified against multiple sources; datamines and reports are labelled as such, not stated as fact.

Wowhead's report on the Project Camelot build moving to a vendor server. The project itself is unannounced and no footage of it exists. (Wowhead / Blizzard Entertainment)
Wowhead's report on the Project Camelot build moving to a vendor server. The project itself is unannounced and no footage of it exists. (Wowhead / Blizzard Entertainment)

The Signal

A build tracker logged Blizzard's encrypted 1.60 branch moving to a vendor server, and Wowhead reads that as preparation for outside testing.

The first hard proof that Riot's MMO exists as something you can actually play probably won't come from Riot. It will come from a version string, logged by a bot, at an hour nobody was watching.

Blizzard just demonstrated the mechanism. On July 30, 2026, the Warcraft build tracker @algalon_ghost logged a line that looks like nothing at all: "Vendor 6 (wowv6): 1.15.8.64858 --> 1.60.0.69014", found at 07-30-2026@05:23:47 UTC.

World of Warcraft Classic art used to illustrate coverage of the Camelot build. The 1.60 branch sits on a July 2006 client lineage, not modern retail code. (Blizzard Entertainment)
World of Warcraft Classic art used to illustrate coverage of the Camelot build. The 1.60 branch sits on a July 2006 client lineage, not modern retail code. (Blizzard Entertainment)

Wowhead reported the same day that the 1.60 branch, codenamed Project Camelot, had moved off Blizzard's internal development servers and onto a vendor server. The word carrying all the weight there is vendor.

A vendor server is where outside parties, hardware and software partners, run compatibility tests against a build. Wowhead reads the move as Blizzard preparing for external testing, and raises BlizzCon 2026 as a possible venue for a playable version, comparing it to Blizzard showcasing Season of Discovery in 2023.

None of that is an announcement. The build is still encrypted, Blizzard has said nothing about Project Camelot, and everything above is a datamine plus an inference drawn from server infrastructure.

The Evidence

What is on the record about the 1.60 branch since October 2025, and what is still only a community guess.

Wowhead has followed this branch since October 24, 2025, when the same tracker caught its first appearance on an internal server: "Internal 2 (wowdev2): 5.5.0.60481 --> 1.60.0.63979", found at 10-24-2025@07:54:33 UTC. Wowhead says it has taken weekly updates on Blizzard's encrypted dev servers ever since.

MMOs.com reported in June 2026 that at least 29 encrypted 1.60 builds had appeared on Blizzard's CDN in that window, on a branch tied to July 2006 client builds associated with patch 1.6 rather than modern retail code. That lineage is why the community calls Camelot a Classic+ project. Blizzard has not.

Oct 24, 2025

First 1.60 build

Caught on an internal dev server. Encrypted from the first sighting.

Jun 2026

29 builds counted

MMOs.com tallies the branch stacking up on Blizzard's CDN, on an old client lineage.

Jul 30, 2026

Vendor server

The last infrastructure step before anyone outside the studio runs the build.

Then there is the empty column. Riot's MMO has no public build tracker, and nothing has ever leaked off its servers for one to catch. Builds caught in the open so far: none.

05:23:47UTC, build loggedThe vendor-server jump was stamped to the second.
29Encrypted buildsCounted on Blizzard's CDN since October 2025, per MMOs.com.
1.60The branchCodenamed Project Camelot. Still encrypted.
NoneRiot MMO builds caughtNo public tracker watches Riot's servers.
The record, sourced:
  • @algalon_ghost logged on July 30, 2026: 'New #Warcraft build found: Vendor 6 (wowv6): 1.15.8.64858 --> 1.60.0.69014', found at 07-30-2026@05:23:47 UTC
  • The same tracker logged the first 1.60 build on October 24, 2025: 'Internal 2 (wowdev2): 5.5.0.60481 --> 1.60.0.63979', found at 10-24-2025@07:54:33 UTC
  • Wowhead reported July 30, 2026 that the 1.60 build, codenamed Project Camelot, moved from an internal development server to a vendor server
  • Wowhead: the move 'indicates that Blizzard could be planning to allow external parties, such as tech companies and other partners, to test this game and ensure its compatibility with their hardware and software'
  • Wowhead says the build has received weekly updates on Blizzard's encrypted dev servers since October 2025
  • Wowhead raises BlizzCon 2026 as a possible venue for a testable version, comparing it to Blizzard showcasing Season of Discovery in 2023
  • The build remains encrypted; Blizzard has made no public statement about Project Camelot
  • MMOs.com reported in June 2026 that at least 29 encrypted 1.60 builds had appeared on Blizzard's CDN since October 2025, on a branch tied to July 2006 client builds associated with patch 1.6 rather than modern retail code
  • Community speculation that Camelot is a 'Classic+' style project is unconfirmed by Blizzard
  • Riot's MMO has been publicly dark since the March 2024 reset announced by Marc Merrill

What This Means for the Riot MMO

Riot's project has been dark since March 2024, so the only things anyone has learned about it came from forensics rather than announcements.

Riot's Runeterra MMO has been dark on purpose since Marc Merrill announced the reset in March 2024. Everything anyone has actually learned since arrived through forensics: job listings that named Unreal Engine and a Sydney server-tech studio, a LinkedIn title change, and a designer's playtest tweet that was deleted within hours.

That is the same diet Warcraft players were on until a bot noticed a number change. Riot gets to control the reveal right up until the moment a build leaves the building.

Project CamelotThe Riot MMO
AnnouncedNo. Blizzard has said nothing about it.Yes, then reset in March 2024. Quiet since.
First caughtOctober 24, 2025, on an internal dev server.Never. No build has surfaced.
Latest moveTo a vendor server, logged 07-30-2026@05:23:47 UTC.Nothing equivalent.
Build tracker@algalon_ghost, logging every version bump.None exists.
What it isUnconfirmed. The community says Classic+; Blizzard has not.Not revealed
SettingWarcraft, on a July 2006 client lineage.Runeterra. That is the only confirmed detail.
Scope and eraNot revealedNot revealed

We have already covered the inside-out version of this, when a Mythic+ boss died at 90% health and the combat log named the spell "Area Death (TEST)". Studios leak through their own plumbing long before they leak through a press release.

The table is not kind to anyone hoping for a Riot reveal this year. Camelot has nine months of encrypted history, a branch number, a bot watching it, and now a vendor-server move. Riot's MMO has a reset announcement and a careers page.

Riot gets to control the reveal right up until the moment a build leaves the building.

What Camelot actually is stays unconfirmed. The Classic+ guess has weight because Classic players have been specific about what they want: a quarter-million survey answers came back asking for more raids and no flying. Reaching back to a 2006 client lineage is also its own quiet verdict on what happened after someone put a number on the world.

The read for the MMO, and it is ours:
  • The Riot MMO's first genuine leak will probably come from infrastructure, not marketing
  • A vendor-server move is the last step before outside hands touch a build; nothing equivalent has surfaced for Riot
  • Blizzard kept a project encrypted for nine months and still got caught by a version string
  • Riot's MMO has no public build tracker, which leaves job listings as the only reliable telemetry
  • A studio's control over its own reveal ends the moment a build leaves the building

Strip the infrastructure story down and the thing inside a build is a world. Riot has an odd advantage here: it has been rendering Runeterra in public for years while saying nothing about the game set in it, so you can already look at the place. Watch Ryze cross it.

0:41. Ryze, a purple speck, walking into the mouth of a hollowed stone giant. The shot is there to give you the scale of the place.
0:41. Ryze, a purple speck, walking into the mouth of a hollowed stone giant. The shot is there to give you the scale of the place.
1:22. A carved relief under fallen leaves. Runeterra leaves its history lying around for whoever bothers to look.
1:22. A carved relief under fallen leaves. Runeterra leaves its history lying around for whoever bothers to look.
2:20. Ryze on a ledge above a landscape that rune magic has torn open, red arcs hanging over the ruins.
2:20. Ryze on a ledge above a landscape that rune magic has torn open, red arcs hanging over the ruins.
2:54. Something enormous walking in the desert while Ryze skids clear of its foot.
2:54. Something enormous walking in the desert while Ryze skids clear of its foot.
5:01. The runes lit under Ryze's skin. He is the only one in frame who knows what he is carrying.
5:01. The runes lit under Ryze's skin. He is the only one in frame who knows what he is carrying.

Call of Power sends Ryze across that world chasing World Runes. He crosses a petrified forest, reads a relief carved by people long dead, and ends up on a ledge above ground that rune magic has ripped apart.

Our Atlas holds the places he is chasing. The World Rune Archives sit in Shurima and are tied to Ryze in canon. Icathia is the ruin of the first city to fall to the Void, still torn open in the east. Beneath the Howling Abyss in the Freljord, the Watchers lie sealed in a tomb of True Ice, and the wind across the bridge wails.

That is the fiction, and it is the same fiction behind the arguments we keep making: a map already cut for three-way conflict rather than two, and a world specific enough that a yeti in the Shurima desert breaks it.

Runeterra, the world the Riot MMO is set in.
Runeterra, the world the Riot MMO is set in.
Shurima
Shurima
Ixtal
Ixtal
Bilgewater
Bilgewater

One thing about the Riot MMO is confirmed: it is set in Runeterra. Which regions it opens with, how much of the map above is in it, where it sits in the timeline, what it runs on, and how it is paid for are all unrevealed. The map and the crests are the fiction Riot is drawing on, not a starting zone, and anyone who tells you otherwise is guessing.

Your Take

Reader poll

Will the Riot MMO's first real gameplay leak come from a datamine rather than an official reveal?

What's Next

There is no date to put on any of this, so here is the signal worth watching instead.

Nobody has a date for the Riot MMO and this piece is not going to invent one. Three things would change that, and none of them need Riot to say a word.

  • A version string. Riot has no public build tracker today. The moment someone stands one up and it logs a branch bump, the blackout is over on Riot's behalf.
  • A vendor-server move, or the Riot equivalent. That is the last infrastructure step before people outside the studio run a build.
  • Job listings. Until something leaks, they are still the most reliable telemetry the project has.

Reported from Wowhead and corroborating coverage. The MMO read is ours and clearly speculative. Analysis by RuneGrove.

More Riot MMO News