Blizzard published "Hotfixes: October 1, 2026" on 1 October. The page is enormous, 107,444 characters of rendered text, and worth reading for one reason: the products it covers.
The list, verbatim
"Here you'll find a list of hotfixes that address various issues related to World of Warcraft: Midnight, Mists of Pandaria Classic, Season of Discovery, Burning Crusade Classic, WoW Classic Era, and Hardcore."
Forever is not in that sentence. Six products, and the branch that launches in 33 days is not one of them.
What is in it, for comparison
Dated subsections for October 1, September 29, September 24 and September 23, covering:
- Midnight: Druid Feral Rampant Ferocity triggering incorrectly against a single target; Hunter Survival Wildfire Bomb periodic damage up 20%, with the developers' note that "the tuning hotfix from the week of September 22 did not properly increase the periodic damage of an untalented variant"; the Venomous Abyss boss Ula'tek, including a fix for Venomous Heart sometimes meleeing a player and for Mother's Wrath being castable at a non-current target; Brewfest items from Coren Direbrew now getting the required level of the recipient.
- TBC Classic: the Honorary Brewer Hand Stamp can now be purchased.
- Earlier entries: the Shadow Enclave delve variant Infiltrate and Ameliorate, a set of PvP movement-speed reductions with explicit was-values (Wing Clip 40% in PvP, Chrono Shift down from 50% to 30%, Consecrated Ground down from 50% to 20%), and a Death Knight Blightfall fix.
The developers' notes and the explicit "was" percentages are what make hotfix posts worth reading. A hotfix log with no prior values is a list of changes; this one tells you what changed from what, which is the only form in which a tuning figure is auditable.
Why the absence matters, carefully
It is evidence that Forever hotfixes ship somewhere else, not evidence that Forever has no bugs or no fixes.
Three things make that the honest reading. The beta has a separate client branch on its own manifest, which is how every build number we report is scoped, so its fixes would not appear on the retail hotfix page. The beta is open to testers with a feedback channel, which is a different mechanism from a public hotfix log. And Blizzard publishes dated development notes during beta separately, which is what our verification hit list has been tracking.
What we can say is narrower and still useful: there is no public hotfix channel for Forever, and a player who wants to know what was fixed has to read the beta notes or ask the testers' Discord. For a launch in 33 days that is a real gap in the information a player can get, and it is one more reason the published record on this branch runs behind the client.
What we cannot tell you
Whether Forever received hotfixes on 1 October that we cannot see. The answer is very likely yes, given the build cadence, and we have no way to read them. That is the gap, not an absence of fixes.
SOURCES: Blizzard's own post "Hotfixes: October 1, 2026", dated 1 October 2026, read from the official news page on October 2 2026. The product list is quoted verbatim from the post's opening paragraph; every hotfix item above is transcribed from it. Related: the 70170 build report, the verification hit list, and our source grading scale.