Which WoW Forever class changes should you check first?
Long development threads contain earlier builds, replies and later corrections. Start from the final staff post and keep its timestamp with the claim you are checking. The title's November 2 date and the displayed November 3 UTC post time can describe the same update context. Do not turn that difference into an extra patch that has no source. Earlier class deep dives remain useful for design intent, while later notes take priority when they change a specific mechanic.
Changes that alter a build deserve a fresh look
Two clear examples show why a saved tree needs a version. The final notes replace Paladin's Twist of Light with Unsealed Wrath and move Druid Lacerate into the Feral tree. Those are changes to a player's point decisions, not merely a new headline. Open the matching class in the planner, inspect the node and its prerequisite, then decide whether an old guide still describes the same build. A familiar class name does not guarantee an unchanged path.
What our snapshot can and cannot confirm
The local reference file identifies build 1.60.1.70755 and a generation date of November 3. It contains the newer Paladin nodes and Feral Lacerate, so those should not be described as universally missing from the data. A build label alone still does not validate every field. One concrete conflict remains: the export's Riptide description includes an initial heal, while the final notes say the spell becomes healing over time only. That field needs an explicit source-conflict label until resolved.
Apply a change to the task you actually play
Check whether the update changes the normal action loop, access to an important node, resource recovery or the tools your group expects. A talent move may affect an early leveling route more than a full-level build; a utility change may matter even when no damage number is quoted. Compare options within the same role and activity. Our tier letters are provisional editorial judgements, so a patch mention by itself is not evidence that a class must move a whole tier.
Keep old builds useful without silently rewriting them
Save the source build and the intended level with a shared plan. If the tree changes, reopen the original as a reference and show the points that require review before offering an updated copy. Do not overwrite a visitor's saved configuration merely because a new version exists. For a guide, record the actual changed recommendation and why it changed. For the reader, the useful outcome is knowing what to recheck before spending points, not memorizing every unrelated bug fix.
Common questions
Where are the official WoW Forever patch notes?
Use Blizzard's development-notes thread and read the final staff post, keeping its date with the relevant claim.
What build does the reference talent data use?
The retained export identifies 1.60.1.70755 and generated 2026-11-03. That metadata is not a full client verification.
Are September class deep dives still useful?
Yes, as design context. A later explicit adjustment takes priority for the mechanic it changes.
Does every buff imply a higher tier?
No. A recommendation depends on role, activity and the remaining conditions, not the word buff alone.
Is Riptide's export text fully consistent with the final notes?
No. The initial-heal wording conflicts with the later notes and needs to remain flagged rather than silently presented as settled.
Are these live damage measurements?
No. This is source-checked change guidance and editorial interpretation, without live level-60 samples.
Sources
- Blizzard forums — Beta Development Notes, updated November 2 · Checked 2026-11-04
- WoW Forever — public talent-tree export · Checked 2026-11-04