WebWoW November 2 update: ten classes, thirty specializations
The WebWoW November 2 update expands the developer’s stated playable selection to ten classes and thirty specializations. Its Arena Journal entry is dated November 2, 2026. The main preparation change is straightforward: read your current specialization, available abilities and talent prompts before reusing an older nine-choice or single-specialization control guide.
On November 3 we observed ten class choices in the current entry screen, including Death Knight. Priest exposed Shadow, Discipline and Holy choices. That visible selection supports an updated description of the interface. It is not our independent test of all thirty specializations, every talent prerequisite or a full match on each role.
| Source change | Player task it affects | Check before relying on it |
|---|---|---|
| Ten classes and all three trees per class | Choosing a role and specialization | Current character and specialization labels |
| Native-style 71-point talent trees | Preparing a build | Rank, prerequisites, next-rank tooltip and any remaining-point display |
| Import/export and saved favourites described | Reusing a setup | Source and specialization of the code; do not assume compatibility |
| Learn outside combat and queues described | Applying a selection | Current client prompts and whether you are in combat or a queue |
| Warsong allied and enemy UI changes | Selecting teammates and reading opponents | Actual current frame labels and input method |
WebWoW talents: selecting and learning a build
The developer describes native talent artwork, prerequisite arrows and tooltips that distinguish your current rank from the next rank. It describes left click to add and right click to remove a point, with presets, build-code import/export and favourites. These are the project’s release instructions, not a verified talent calculator hosted on this guide.
Read the selected tree and constraints in the current client before learning. A code from another game, specialization or old release is not automatically a valid selection. An imported display does not by itself prove that every prerequisite was satisfied or that the game account has changed.
The source says learning happens outside combat and queues, and can dismiss a pet or remove an off-hand the new specialization cannot use. Plan to inspect equipment and current action labels afterward. This is a reason to review your keybinding sheet, not a reason to copy unverified official WoW numerical values into a browser guide.
Our site does not send a build to WebWoW, store a game account or claim to validate all of those trees. A future on-site calculator would need the game’s own current dataset and rule evidence before it could make that promise.
WebWoW Warsong UI needs input-specific checks
The announcement describes four selectable allied frames using F2–F5 and five stable enemy cards in the five-versus-five mode. It also mentions a timer layout adjustment for phones with a full roster. These details identify specific things to inspect; they do not establish that every desktop shortcut or phone gesture was tested by this guide.
If you use function keys, check how your keyboard and operating system deliver them. A browser or hardware shortcut may intercept an input. If you use touch, inspect the actual targeting and action controls on that device. The device guide keeps developer mobile claims separate from our still-incomplete physical-phone match testing.
We have not measured a Warsong queue, active-player population, complete match or sustained phone frame rate. Seeing the mode in a source announcement is different from reproducing it in a live session.
Collision and audio changes do not define a new meta
The same release discusses pillar collision and several sound or projectile fixes. A movement bug that places a character inside geometry can affect a fight, but an announcement of the fix is not a precise map dataset. This guide cannot derive arena dimensions, line-of-sight paths or collision coordinates from that paragraph.
Likewise, a visible or audible effect behaving differently does not necessarily mean a damage coefficient changed. Keep interface, collision and balance claims separate when comparing an old replay with a new session. The October 31 balance analysis explains why its earlier duel statistics cannot rank all thirty current specializations.
A build-change example after the November 2 release
Suppose an old screenshot shows Shadow controls but you are now preparing another Priest specialization after the WebWoW November 2 update. Confirm the selected specialization first, then inspect the current tree and learning prompt. An imported code is a proposed selection; do not treat its appearance as proof that the intended build was learned or that its actions are available in the current stance.
After applying a change through the client’s own controls, inspect the action bar and relevant equipment or pet state before entering a queue. Record a label that differs from the old screenshot rather than assuming every missing action is a keyboard failure. The source describes a learning restriction during combat and queues, so that client state matters to the report. This example explains how to review the announced feature; it is not an independently tested import-and-save procedure for all thirty specializations.
Review your first session after the update
- Read the original source and date. Check the selected class and specialization in today’s entry screen.
- Inspect the current talent and equipment prompts before learning or importing anything.
- After a build change, re-read the action bar and distinguish an unavailable stance or ability from an undelivered key.
- Practise a small sequence in an appropriate context before a competitive queue. Record what was actually completed.
- Read the November 3 follow-up for the later pet and Death Knight fixes rather than assuming the November 2 note is the final state.
Primary source: WebWoW original site → News & Updates → the November 2 article about ten classes and thirty specializations, viewed November 3, 2026. No independent numeric build identifier or full thirty-spec test is claimed. Return to the journal or practical guides.
