We publish a lot of Forever material, and a fair question from a reader is which of it is worth reading. This is a ranked map of the sources, with the checkable content in each named.
1. Class deep dives: the densest material anywhere
Highest value by a wide margin, because they contain numbers.
Level gates, baseline ability lists, talent milestone positions, pet families. The 30 September posts for Hunter and Druid and for Priest and Warrior are the only first-party Forever documents that let you argue with a design.
Read them for: Shadow Word: Death at level 32, the 16-point talent milestone, and which abilities moved from talents to baseline.
Limit: four of ten classes, and Blizzard says the numbers will move.
2. The Legacy System post: one number decides it
The 23 September breakdown is the second densest, and it turns on a single figure: 16 Legacy Points per character at launch.
Sixty-five challenges across six categories, points account-wide, perks in three trees. Read it for the cap and for Well Rested, and note that Legacy Rewards is named and never described, which is the largest gap in Blizzard's own documentation of this system.
3. The named explainers: useful, thinner than they look
Blizzard's Wow Weekly on 25 September indexed six of them: choose your ruleset, name your character, create your hero, the Skyborne, the Legacy System, and podcast episode 1.
The naming explainer is worth reading for one sentence: character names get a two-name structure for "a larger, realmless Azeroth". Realmless is the single most consequential word Blizzard has published about Forever's structure and it appears in a naming post.
4. Our CDN watcher: precise, and not about content
Build numbers, sequences, and the config fields that let us tell a genuinely new build from a CDN re-point. Four builds in five days, all four regions in parity across six pushes.
Read it for: whether a build is real, and whether a region is behind. It cannot tell you what changed and we will never claim otherwise.
5. Fan references: behind, and one is useful
All three references we track sit on 70009, the last build any of them wrote about, from 25 September. That is four builds and about forty hours stale.
The exception is classicwowforever, which published genuine notes for 70009: two talents cut, two renamed, Wrath and Holy Strike buffs, a flat Eureka! discount, easier campfires, quest fixes. That is the kind of writing worth having and it needs catching up.
6. Retail coverage: adjacent, and dated
Midnight's 12.1.5 arrives 13 October, three weeks before Forever launches. Retail uses Mythic, Season, Keystone and a Tier 11 solo challenge. Forever publishes Legacy talents, a 16-point milestone, 65 challenges and Dual Specialization at 40.
Two design vocabularies, three weeks apart, from one studio. Useful context, not the same game.
The gap worth knowing about
There is no public hotfix channel for Forever.
Blizzard's October 1 hotfix post covers Midnight, MoP Classic, Season of Discovery, TBC Classic, Classic Era and Hardcore. Forever is not in the list, and that is expected, because the beta runs on its own manifest and has a separate tester feedback channel.
The consequence is real: a player who wants to know what was fixed has to read beta development notes or ask a tester Discord. There is no equivalent of a retail hotfix log for this branch, and we do not know of a public one. That is a gap in the information a player can get, not evidence that no fixes are shipping.
What we would read first, in order
The Legacy System post (one number, one guide to write), then the Priest and Warrior deep dive (the most concrete class document), then classicwowforever's 70009 notes (the last real written account of a client).
And on launch day itself, our build report, which will be the freshest Forever information anywhere and will tell you almost nothing.
SOURCES: all sources listed above were read from their own publishers on 2 October 2026. Build data is from the wowdev2 manifest via the blizztrack API. The ranking is our own judgement about information density, not a claim by any publisher. Related: what our build reports mean, the Legacy System guide, and the 33-day launch guide.