On October 29, 2026, Blizzard published an episode of the World of Warcraft: Forever podcast devoted to a single subject: technology and the development process behind the game. It is called All About Tech, and it is the most technically framed piece of official podcast material for the game so far.
This is an independent site and is not endorsed by Blizzard Entertainment. World of Warcraft: Forever launched globally on November 4, 2026 and is still in beta, so details can change before the game leaves beta.
What the Episode Is
All About Tech is presented as an episode in which the discussion centres on technology and the development process. The official page states that this episode will discuss technology and development, and that World of Warcraft: Forever launches globally on November 4 at 3:00 pm Pacific time.
That framing is worth pausing on. The launch date is repeated on the page, which is a reminder that the podcast schedule and the launch schedule are deliberately coordinated: content drops into the window where players are actively evaluating a new release.
Our launch week recap covers the launch window itself, and the End of Beta special guide covers the previous episode in the series.
The Lineup: Host, Special Guest, and Three Developers
The panel combines people from outside Blizzard with people inside it, which is what gives the episode its shape.
The host is Countdown To Classic. The special guest is Shobek. The development team is represented by three members:
- Josh “Aggrend” Greenfield, Senior Game Designer.
- Ana Resendez, Lead Software Engineer.
- Frank Williams, Principal Software Engineer.
The composition matters. Two of the three Blizzard guests are engineers, which is a notably different balance from the earlier end of beta special, where the panel was led by a game designer, a production director, a software engineer, and a combat systems designer. The same Ana Resendez appears in both episodes, which makes the pair a useful comparison of a technical conversation with and without an engineer majority.
Frank Williams also appears as a guest in the October 30 WoW Weekly episode, which lists the podcast topic as technology and development, alongside Josh “Aggrend” Greenfield and Ana Resendez.
Why a Standalone Technology Episode
Blizzard has a long history of making technology the subject of its own broadcast rather than a footnote inside a design conversation, and doing it here at launch serves several purposes at once.
For the audience, it answers a question the launch itself provokes. A rebuilt version of the original Azeroth running on modern hardware raises obvious questions about how it is built, and players have been asking those questions since the project was announced.
For the studio, it is a controlled venue. A technical conversation can be genuinely candid about process without making commitments about the product. Talking about how you build something is very different from talking about what you will add to it, and the latter is subject to change, marketing, and disappointment. This episode lands five days before launch, which is an efficient moment to set expectations about craft rather than content.
It also connects to a live need. Anyone playing the game is running it on their own hardware, and technical expectations are set by whatever they have read elsewhere. Our GPU requirements guide covers the practical side of running the game.
Designers and Engineers in the Same Room
The most valuable configuration in this episode is the mix itself.
A senior game designer in the room gives the engineering discussion a purpose. When Josh “Aggrend” Greenfield is present, questions about tooling, pipelines, and iteration speed are anchored to player-facing outcomes, which makes the conversation legible to people who do not build games. Engineers without a designer tend to talk about systems, and designers without an engineer tend to talk about outcomes, and neither framing survives contact with an audience that wants both.
The two engineers, Ana Resendez and Frank Williams, add the other half. A lead engineer and a principal engineer can plausibly speak to different layers of a codebase, and a host who knows how to ask about process can get a meaningful answer from each about where the hard parts were.
What the Official Page Does Not List
This is the part worth being precise about, because the temptation with a tech episode is to fill the gap with plausible-sounding detail.
The official page does not list any specific engine, architecture, performance optimisation, toolchain, or other technical detail. It does not provide a transcript. As a result, any claim about which engine the game runs on, how its world streaming works, what its content pipeline looks like, or what was actually discussed in the episode cannot be verified from the official source.
That limitation is not unusual. It matches what Blizzard has published elsewhere: our Deep Dive panel guide covers a panel where the engine architecture was not disclosed, and the roadmap article covers the shape of what has and has not been said publicly.
The right conclusion is not that information is being withheld. It is that the officially published material about this game currently sits at the product and systems level, not the implementation level. Design intent, feature scope, and process are being communicated; internal architecture is not, and no third-party article can substitute for a source that does not exist.
How to Listen For Something Useful
Editorial advice: treat this episode as an orientation piece rather than a reference. The most transferable thing in any developer podcast is a description of a problem and how a team approached it, because that reasoning transfers even when the specifics do not.
Three things worth noting down as you listen. What the team says was hardest, because that usually tracks where future changes concentrate. Whether iteration speed came up, because that is the honest limit on how quickly content can change. And whether the designer and engineers agreed in front of you, because a visible agreement between a design lead and an engineering lead about a tradeoff is a real signal about direction.
For the roadmap side of the picture, and what the studio has actually committed to publicly, see the launch week recap.
Frequently Asked Questions
Does the All About Tech episode reveal the game engine?
No. The official page does not list any engine, architecture, performance optimisation, or toolchain detail, and it provides no transcript, so engine details cannot be verified from the official source.
Who appears in the episode?
Host Countdown To Classic, special guest Shobek, plus Senior Game Designer Josh “Aggrend” Greenfield, Lead Software Engineer Ana Resendez, and Principal Software Engineer Frank Williams.
How does this differ from the End of Beta podcast?
The End of Beta special ran with a production director and a combat systems designer and focused on the test period. All About Tech narrows to technology and development, and features two engineers rather than one.
Is a transcript available anywhere official?
No transcript was published with the episode listing. The episode itself is the primary source, and third-party summaries should be treated as interpretation rather than reporting.