WoW Forever news & field notes

Updated October 28: Blizzard clarified on October 27 that entering a raid removes Charged, while death does not. The movement checklist now includes this condition alongside the earlier Tauren and Skyborne values.

Charged’s hour-long duration is not an hour of continuous speed: Skysight’s active burst still lasts 15 seconds. Check whether Charged is present before using the higher speed value in a travel plan.

A missing map and a boss away from its marker need different checks. The dungeon-map guide compares coverage, floor selection and patrol areas, with the author’s current commands and map-window controls.

The dated file targets Forever 1.60.1. Check launch-client compatibility separately; these markers do not supply newly verified entrance coordinates.

The current status now distinguishes Blizzard’s closure confirmation from the earlier planned end time. The world directory remains useful for choosing a destination and comparing prerequisites; old test observations do not establish launch-day route access.

The world departure table compares newer official guidance with dated testing records, then turns it into a party checklist: prerequisites first, meeting landmark second. The searchable directory now uses the October 20 dungeon ranges and includes returning Onyxia’s Lair.

The briefings describe launch content. They do not announce a higher Beta cap or provide entrance coordinates. For launch and beta dates, see the launch facts.

Before taking a detour for a missing service, open the grouped marker and identify the NPC. The map-layer checklist separates icon grouping, character-specific flight progress and the new mailbox diagnostics.

The dated file record and author guide describe addon behavior; they do not confirm live NPC availability or supply newly verified coordinates.

Before following a shortcut, check which client file is installed and whether the node is present now. The community navigation checklist explains the dated Forever changes and gives a pre-trip sequence.

This is addon guidance, not a new official transport route or a map of verified node coordinates.

Updated October 27: the OpenMap guide now covers the author’s 0.7.5 quest-click and pin-drawing fixes. Match the installed file before troubleshooting the view.

The October 17 release and its four community-drawn interior maps remain as a dated comparison. Transport-display switches still need to be distinguished from actual travel access.

A new community map announcement raises a useful navigation question: what does a room highlight actually tell you? Our explorer-map checklist explains the author's positioning method, the separate quest-marker requirement and how to regroup when the display disagrees with the room.

The features are author-documented; or imported its markers as verified coordinates.

Blizzard's new video connects dungeon locations with the way a group moves through them. Our timestamped checklist turns that briefing into meeting, visibility and regrouping checks.

The video describes launch content. Current Beta availability and Dalaran city-service access are checked separately; no entrance coordinates or tested route are inferred.

Sectimus's versioned documentation now explains separate instance switches and gamepad controls. Our map-setting checklist also separates optional world-map textures from exploration progress, so you can investigate the missing view before changing your setup.

These are community addon controls, still labelled beta, rather than a Blizzard access announcement or an in-game test by this site.

The HFWM author describes terrain and cave views; the Zonewise 1.3.2 announcement describes faction flight markers and dock destinations. These community displays do not establish current travel access.

Our map-layer checklist helps you compare a visible landmark, a cave depth and your character's learned flights. Check the installed version, and keep cave views separate from untested instanced-dungeon support.

Updated October 17: the official development notes supersede the earlier access reports. Our Dalaran checklist now separates the unaffected dungeon trip from an unsafe outdoor city stop for Horde characters.

The October 9 developer clarification and earlier Reddit observation remain as dated history, rather than current access instructions.

The October 6 Pacific-time official restart notice describes a chest quest-item fix. The staff follow-up adds occasional elevator/transport disconnects and join/leave-guild errors. This is an announcement of fixes, not a current service-status test.

Our dated Beta checklist separates server-side missing loot from client-side highlighting and shows which details to retain if a problem recurs. The boat guide keeps disconnect diagnosis separate from route and next-stop checks.

Blizzard's article, published October 7 UTC (October 8 in UTC+8), describes four bases and a central flag in a 15v15 battleground for levels 30–60. The first team to 2,000 points wins. Major-capital battlemasters and named faction bases provide announced queue options; this does not confirm current Beta availability.

Our map notes turn the objectives into a preparation question: who protects a base, who moves for the flag, and where does the party regroup? The map artwork, queue instructions and a live access check are separate kinds of evidence.

In the author post checked October 8, W3bDragon42 describes position and facing in supported approach areas, while interior dungeon maps remain static. The author also explains why Retail RFC art cannot simply stand in for the Forever layout.

Our dungeon map guide adds a selection table, a shared-floor party plan and diagnosis steps for a missing player marker or mismatched map. It does not redistribute addon maps or certify client testing by Forever Atlas.

Two October Reddit discussions describe Alliance and Horde quest-area choices and a player who ran into a Hillsbrad quest gap. A personal path does not establish fixed level brackets, a universal unlock level or the fastest route.

The new onsite guide uses those reports as a shortlist, then adds our journal-based selection table, prerequisite diagnosis, first-versus-repeat dungeon comparison and illustrative 60-minute worksheet. It follows the officially published level-30 Beta cap and labels unverified Wetlands quest-pickup reports rather than turning them into guaranteed prerequisites.

The project listing checked October 8 shows version 1.52 dated October 4 for Forever 1.60.1. Its author describes floor views, drawing and party/raid sharing. The October 6 check of the dated file notes flags missing boss labels on the Wetlands map; a blank label is not proof of an empty room.

Our Wetlands map checks explain how to communicate a floor, landmark and intended next action without inventing a boss pin. Record your actual addon file and client build before comparing screenshots.

Forever Loot Sparkles lists v1.1.1 for October 6. Tweaks Forever v0.11.0, released October 7, adds an optional sparkle feature that is off by default. The authors document outline-setting changes and a full restart when removing the visible effect.

Our onsite comparison starts with the same visible object, changes one tool at a time and includes how to undo the setting. It also separates a hard-to-see object from missing loot, so a server-side problem does not turn into repeated graphics adjustments.

The October 1 development notes now provide the published cap and dungeon ranges. This update supersedes our earlier planned-cap wording; it does not certify live service status. Read the return and build checklist before applying a saved allocation. The bonus-XP change concerns extra dungeon-quest XP, not all quest rewards.

Blizzard’s October 1 video covers Warrior rage generation and tank mobility, Shaman totem placement and movement, and Rogue energy and specialization changes. It is the first part of a three-part series.

Use the class comparison to read talent effects and requirements. Before a group run, discuss who handles interrupts, control and recovery; the Rogue preparation guide gives a practical checklist.

SimonizeShow’s Rogue demo analysis was published September 16; NOHITJEROME’s limited-time class video was published September 30.

The Rogue guide adds party roles, a point-budget check and a comparison sheet. The short-session guide adds time budgets, a travel example and a trial worksheet.

October 10 update: This entry retains its original publication date. See the launch facts for later developments.

Blizzard's September 29 notice includes Holly Longdale's opening Storytime and Clay Stone's Forever dungeon talk at PAX Aus. The published live window was October 8, 18:00–19:30 PDT, corresponding to October 9, 09:00–10:30 in Taipei and Beijing.

Our on-site schedule separates the presentation from game updates and explains what to record before revising a dungeon guide. No dungeon name, entrance, loot or new unlock time is established by this announcement.

Community manager Kaivax says the team is working on the Kyle quest request in the official forum reply. The reply is dated September 28 UTC, September 29 in UTC+8; it gives no completion date or client build.

The updated community answer explains which evidence would establish restoration and why older NPC coordinates or rewards should not become current Forever instructions. This is an acknowledged request, not a confirmed live quest.

Forever Quest Tint highlights quest IDs absent from its Vanilla reference list. The author warns that gaps can mislabel old quests. Its September 27 0.5.0 file is listed for Forever 1.60.1.

Our four-step comparison records a familiar quest, a suspected new quest, their IDs and the actual client details. A tint helps choose what to inspect; it does not prove a quest is newly added or currently available.

WhereYouAt adds the leader's current zone to LFG browser entries, according to its author. The listed September 27 file targets Forever 1.60.1. It does not reveal all party members or their arrival times.

The on-site preparation table explains what to ask before leaving, including a worked example of nearby versus farther applicants. Combine a location clue with each player's actual travel option, prerequisites and a named meeting landmark.

Blizzard has now published a dedicated explanation of the Legacy System. Its 65 challenges are divided among classes, tradeskills, PvP, adventure, dungeons and raids. A completed challenge grants one point across the Battle.net account; the launch spending cap is 16 points per character, and characters can choose different perks. Blizzard says a single character can earn enough points to reach the cap, so alts are optional rather than required.

Our Legacy guide turns the official categories into a practical first-character checklist. It also explains the access trigger, the three perk trees and the separate rules announced for Hardcore, which arrives after launch. The article describes launch plans; this is not a claim that every challenge or perk has been tested in the current Beta client.

Blizzard's dedicated Skyborne guide adds a clearer starting premise: the wind spirits have vanished from Zephras Isle, old structures are failing and communities are becoming isolated. At character creation, the Horde Windshapers follow elemental tradition while the Alliance High Order seeks lost arcane knowledge. Both variants can be Druids, with forms created for this race.

Our Skyborne guide now pairs that story with the confirmed level 1–12 starting range, class options, racials and appearance choices. The new article does not change the faction split already shown in our comparison tool. It is an announcement, not a verified catalog of every option available in the current Beta build.

October 10 update: This entry retains its original publication date. See the launch facts for later developments.

Blizzard’s staff update announces WoW Forever 1.60.1 Build 69977. Exit the Beta, update through Battle.net and confirm the client build before comparing results with older bug reports. The post is titled September 22 and appears on the forum with a September 23 timestamp.

The stated fixes are deliberately narrow: some Mac display and stability issues, improved character-select navigation when a gamepad is active at launch, and interaction with quest-starting items using a gamepad. It does not announce a general fix for every Mac graphics symptom or all controller menus.

The controller feedback thread raises other player-observed friction in bags, gear sets and map quest hover. Those reports explain what to retest; they are not confirmed features of this patch. Our on-site checklist separates what Blizzard announced from what still needs a fresh client check. The September 24 weekly notes followed this release; later updates are in the beta archive and launch facts. Build 69977 is a historical patch number.

Blizzard’s September 22 guide lists the full nine-class matrix for Horde and Alliance. Use the combination table to filter the options for your group.

Alliance High Order has Read Ley Line; Horde Windshaper has Skysight. Both share Walk on Air, Wind Blessed and Elemental Insight. Compare the faction utilities in the racial tool, or follow the race selection guide for specific character choices.

Blizzard’s naming guide explains the two-part character name used in Forever. The complete combination, rather than the first name alone, must be unique within a region. Two players can share a first name if their second parts differ.

Eligible upgrades have an early reservation window from October 27 to November 3, with up to three characters and names allocated first come, first served. Prepare several acceptable full-name alternatives. Blizzard warns that restricted terms and impersonation can still be rejected when split across the two parts.

For a simpler world display, Blizzard lists Escape → Options → Nameplates → My Secondary Name as the toggle. The secondary name still appears in chat. Our on-site name checklist keeps these rules beside the access and calendar details; it does not promise that a particular name is available.

More than one Reddit user reports addon settings returning to defaults after /reload or relogging in the Beta. A workaround author says a saved file may be written but not restored correctly on their tested setup. That is a useful diagnostic clue, not proof that all addons share the same defect.

Our on-site troubleshooting checklist walks through one-addon testing, a backup of WTF/SavedVariables, and separate reload, relog and full-restart checks. The third-party workaround changes .toc files and filesystem links; its author had not tested the Windows or macOS builds in-game when checked. Treat this file-modifying workaround as experimental; use the backup and single-addon checks first.

In a community-maintained leveling thread, players suggest grouping when a starter-zone kill objective is crowded, checking for follow-up quests before leaving, confirming gathering tracking and keeping room for useful materials. These are small decisions a player can test in the current build; the thread is not an official route guide.

Our four-step on-site checklist includes a check that both group members receive objective credit and reminds readers to agree on loot rules. We left out the thread’s exact resurrection, bag-size and XP-bonus numbers because those need separate client or official verification.

In a Reddit Beta discussion, one warrior likes gear made with mining and blacksmithing, another player favors herbalism and alchemy for potions, and another points to bag-space tradeoffs. These are early personal experiences, not class-wide performance results.

Blizzard’s system recap confirms that professions are part of Forever’s design. Our on-site decision table starts with the item you want to make, then checks current recipes, binding rules, materials and actual character benefit. Beta balance and market prices may move; there is no verified universal best pair here.

Blizzard has published a dedicated ruleset explanation. It covers grouping boundaries, PvP character creation, Hardcore exceptions and online language preferences.

Our ruleset guide turns those rules into a group decision table, two examples of incompatible character plans and the exact language-setting menu path. It also separates a battleground exception from normal dungeon grouping. This is a new official explanation, not a newly verified Beta hotfix.

Our new Ragefire Chasm guide organizes a first run into quest preparation, encounter positioning and the decision to repeat. The plan stays on this site and keeps the community source visible.

Our Beta addon guide starts with a missing function rather than a large addon pack. It includes the documented installation folder, useful commands and a way to check each tool before adding another.

The projects are community tools. An author’s compatibility statement is kept separate from an Atlas playtest, and a Retail category label is not treated as proof that every Retail addon works in Forever.

The community report distinguishes several graphics symptoms and records its author’s hardware and client builds. Its revised explanation says temporary visual improvement does not establish a lasting fix.

Our Mac preparation notes focus on reversible checks and when to stop testing. This is a player report, not a Blizzard announcement that Mac problems have been resolved.

September 24 update: Blizzard’s build 69977 note reports fixes for some Mac display and stability issues. Players in the same thread describe mixed results after updating. Keep the hardware, build and exact symptom in any new report; the older workaround list is not a guaranteed fix.

October 10 update: This entry retains its original publication date. See the launch facts for later developments.

Blizzard’s opening announcement, checked September 21, provides a concrete first-week program. Our Beta guide now separates the opening content from later testing, including the planned Server Slam whose date is still unannounced in that article.

For a useful evening, choose a single goal: explore your starting area, try a new dungeon with friends, or compare a changed class ability. Pick a stopping point before starting, so a queue or an unfinished quest does not derail the whole session.

The first-dungeon checklist covers quests, group expectations and how to decide whether another run is worthwhile. The known-issues table is available alongside the access steps if the client behaves unexpectedly.

A September 19 player thread on Blizzard’s forums reports large quest-turn-in gains in Ruins of Lordaeron. Replies disagree about the pace. In a separate Reddit discussion, the opening post welcomes the incentive to return outdoors, while replies question the value of repeat runs.

These are player observations and opinions, not patch notes or a measured leveling benchmark. No universal XP multiplier or guaranteed levels per run follows from them.

For your group, ask who still has dungeon quests, who wants equipment and who is joining to help. Those goals can justify different plans even with the same character level. Our on-site checklist turns that into a short pre-run discussion and an after-run decision.

September 24 update: A later Reddit thread argues both sides more explicitly. Some players welcome a reason to explore outdoors; others say repeated group dungeons matter for healer and tank play, socializing and character choice. Neither position establishes final tuning. The actionable distinction is first-run quest rewards versus repeat-run combat XP. Record both, along with group wait and travel time, before deciding what your party wants next.

In Jez Corden’s September 18 interview, Ion Hazzikostas positions Forever alongside Retail and Classic, with continued development intended for years. He also discusses the tradeoff between convenient matchmaking and the effort involved in forming social connections.

For returning players, the useful question is which pace and group experience they want. It is not evidence of a new numbered sequel or a timetable for retiring another version. The WoW 2 explainer now connects this interview to the earlier developer comments and the announced product.

October 10 update: This entry retains its original publication date. See the launch facts for later developments.

Blizzard’s living Beta known-issues post is now the first place to check when a feature behaves strangely. The September 18 revision lists disabled character friends, a minimap that may sit partly off-screen and a Cooldown Manager whose implementation varies by class.

The same post identifies combat and class-specific problems. Queueing Heroic Strike, Cleave or Raptor Strike can disable the spell-queue window; Bear Form can multiply armor from buffs and consumables; Arcane Missiles can fire a full-damage bolt when interrupted by damage; and lower-level resurrection sickness can have the wrong duration.

Several items are explicitly marked for the next Beta build, including selected Waylaid Crate behavior, Starshards with Twilight Focus, Retribution Vengeance, Holy Strike rank progression and Firestone tooltip text. “Fixed in the next build” does not mean the correction is already on the client you are using.

Before resetting talents or reinstalling, record the client build, class, level and reproduction steps, then compare the symptom with the official list. Our Beta guide now turns the source into a short triage table and explains which observations still need a fresh client check.

GamesRadar reproduces a September 17 Warcraft post that acknowledged final opening issues and said the team expected the doors to open soon. GamesRadar’s reporting collected follow-up developer posts describing heavy pressure and active service scaling.

This supports a narrow conclusion: the opening attracted enough simultaneous demand to create queues and require scaling. The posts do not give a concurrent-player total, a regional split, a conversion rate or a retention figure.

For players, the practical lesson is to separate an account-entitlement problem from a live-service problem. A client that installs, a Play button that activates and a realm that accepts a login are three different checkpoints. The Beta access guide now keeps those checks beside the official issue list.

Read the official opening announcement for the announced testing program.

According to GamesRadar’s attributed account of the World of Warcraft Developer Q&A, senior game designer Josh Greenfield said GDKP will not be allowed in WoW Forever. GamesRadar’s attributed report connects the decision to protecting social play, reducing barriers for players without large gold reserves and limiting an avenue used to move illicit gold.

GDKP is a raid-loot arrangement in which items are auctioned for in-game gold and the collected gold is distributed among the group. The Q&A sets a policy direction for Forever; it does not, in the material checked here, provide a complete enforcement rulebook, penalty schedule or definition for every player-run loot system.

The practical planning point is simple: a group preparing for Forever should agree on a different loot method and document expectations before a raid. Our systems guide now keeps the confirmed position, its rationale and the still-open enforcement details together.

The policy summary here was checked against the named report; the Q&A video is linked for reference, without claiming a separately verified transcript.

Start a race choice with faction and class, then compare the problem each racial ability solves. The race selection guide works through Alliance Paladin, Horde Shaman and Alliance Druid options.

Alliance Skyborne adds Read Ley Line, while Horde Skyborne adds Skysight. The racial comparison lets you put two candidates side by side.

Ready to travel? The Riverglades guide explains the Steamwheedle–Powderfuse port connection, level fit and how to agree on a meeting point with friends.

Datamined preview · contains spoilers. Icy Veins’ gallery includes Riverglades and Zephras Isle map art, plus instance maps such as City of Dalaran and Excavation Site: Wetlands. The report cautions that unused files, including Season of Discovery assets, are also present.

Wowhead’s loading-screen gallery separately shows new continent and destination artwork. Loading screens are illustrations, not maps for navigating entrances.

How to use these previews: open the original galleries for the full images, then compare destinations with our world directory. Record a route only after checking its build, entrance and access requirements. A file name alone does not confirm an open dungeon, a new flight path or an obtainable quest. These galleries do not turn our destination directory into a complete interactive map.

Datamined preview · contains spoilers. Icy Veins’ first mount roundup shows Skyborne Galestriders alongside models such as Golden Sabercat and Pack Kodo.

Use the gallery as an appearance preview. A model’s presence does not establish that every mount can already be obtained, or settle its vendor, price, drop rate or launch availability.

A useful collection checklist: keep the model name, source link and observed build together. Add the acquisition method only when a specific quest, vendor or reward is confirmed. Keep race access and collection-edition rewards separate when comparing character choices in the Skyborne guide.

In Robin Baird’s September 15 interview, Josh Greenfield describes hiding item stats until a drop occurs for a player or someone on their server. He also discusses a built-in damage meter; the planned cooldown manager may not be in the Beta.

For your first session: check which interface tools are actually available before importing an old setup. Keep equipment notes with the build, item source and observed stats. Avoid treating an early list as a final best-in-slot guide. This interview is not a tested add-on compatibility list or a blanket ban on a named add-on.

October 10 update: This entry retains its original publication date. See the launch facts for later developments.

Blizzard’s September 15 announcement separates the two sessions: WoW Forever starts September 17 at 10:30 a.m. PDT, after the modern WoW session at 10:00. That is 1:30 p.m. EDT, 18:30 BST, 19:30 CEST and September 18 at 01:30 in Taipei and Beijing. Watch through the official Warcraft Twitch or YouTube links in the announcement; Blizzard also says a VOD will follow.

A Reddit post by WarcraftTeam said, before opening, that Beta would open after the Q&A livestream. This gives an order of events, not a precise server-opening hour.

Use the Beta access and timing guide, then the first-session checklist. The race/class table separates six officially named additions from the wider preview matrix.

The latest official schedule distinguishes modern WoW at 10:00 a.m. PDT from Forever at 10:30. The older general-event listing of 19:00 CEST / 01:00 Taipei was not the Forever segment’s start. The corrected times are above.

Players are also asking about naming rules, mail between rulesets and gear progression. These are questions, not developer answers; our community question list keeps that distinction visible.

October 10 update: This entry retains its original publication date. See the launch facts for later developments.

In its September 14 report on Destin’s developer interview, Wowhead describes three useful planning points:

• The September interview described an opening level-20 cap, with a later rise to 30. The October 1 official update subsequently published the level-30 phase.
• Characters are described as starting at level 1 at launch.
• The team has no current plans for a WoW Token or level boosts.

Our summary follows the attributed report; the original interview is linked for context. No precise cap-increase date is established here, and “no plans” is not an irreversible promise about the game’s future.

How to use this: keep your first-session plan focused on early abilities, controls and one repeatable route. Do not treat reaching the test cap as a completed endgame review, or schedule level-30 activities for the opening session. The access guide keeps interview plans separate from written eligibility rules.

Blizzard Support, checked September 17, explicitly separates game time from Beta access. This answers a practical question for returning players whose subscriptions have expired.

Digital Epic/Collection upgrades and selected opt-ins flag the account automatically. Physical Collector’s Edition access uses the emailed redemption instructions. A missing Beta option should be checked against the correct account; Support advises restarting Battle.net once testing begins.

A useful order for your own checks: establish eligibility, look for the installer, then check the current service notice before trying to log in. An installed client does not establish account access or an online server. Do not buy game time merely to solve the wrong problem.

The Beta guide now links the official instructions directly. November launch access and Invite-A-Friend benefits remain separate from September testing.

The Forever system-requirements article has separate Windows and Mac tabs. On our September 17 check, both list 8 GB RAM minimum, 16 GB recommended and 128 GB available SSD space. That storage figure is a requirement, not a measured Beta download size.

The Windows minimum lists Windows 10 64-bit, a four-core 3 GHz processor and a DirectX 12-capable 4 GB GPU. The Mac table lists macOS 12 minimum, Apple M2 or ninth-generation Intel Coffee Lake; its recommended CPU is Apple M4. Read the original table for the complete graphics and operating-system combinations.

Before your first session: compare your exact device and free space with the current table, then decide which settings to test. Meeting minimum specifications does not promise a particular frame rate. See the compact comparison in getting started.

September 21 update: Blizzard’s GPU notice adds an architecture compatibility check. “Supported” still does not mean a card meets minimum specifications. The new guide section explains the distinction; Kaivax’s installation reply is a pointer to that notice, not a diagnosis of every installation failure.

Icy Veins’ Hardcore panel report describes a warning before the world refreshes around a character, with a countdown and an option to move earlier once the player is somewhere safe. Its example starts at three minutes; this is a demonstration timer, which may differ in the current client.

The Reddit discussion raises a different set of questions: what happens during combat, deep inside a cave, or when a player wants to avoid repeated layer changes? Those comments identify useful testing questions; they do not establish a cooldown, a right to postpone indefinitely or protection from damage.

If you encounter the feature: record the build, trigger, countdown, button text and outcome. Check one behavior at a time. The systems guide now keeps this preview separate from Blizzard’s written ruleset rules. Hardcore’s later release is not evidence that it is available in the opening Beta.

Start the first session by agreeing on faction and ruleset with friends. Use the character table before creating a character, then follow the getting-started checklist for controls, abilities and the first outing.

If the party needs to cross continents, name the departure and destination ports. The boat guide explains the announced connections, including transfers at Auberdine. Confirm the next stop before leaving a vessel.

Blizzard’s Found Photos recap lists three services: Stormwind Harbor–Auberdine, Menethil Harbor–Southshore–Auberdine, and Steamwheedle Port–Powderfuse Port.

For Stormwind to Southshore, the first two services share Auberdine as a transfer port. The three-port service does not specify a timetable or stop order, so confirm the vessel’s next destination before leaving. Use the boat planner to compare connections and agree on a meeting port.

Our new WoW 2 news explainer brings together the IGN developer interview, Blizzard’s Forever announcement and a clearly labeled player discussion. It explains what the sources establish without turning a comment about the game’s direction into a sequel announcement or permanent cancellation claim.

The world guide now separates the Riverglades port report from official region facts. The Zephras Isle notes bring the starting-area and character-choice references together. Both include credited preview images; neither is a complete navigation map.

The travel detail comes from Wowhead’s September 14 zone preview, checked September 15. Dock coordinates and later island-access rules still need verification.

Blizzard has published its September 13 Deep Dive recap. We updated the systems guide and added the official ruleset selection image, replacing earlier unresolved notes about point limits and selected system rules. Detailed rules stay in that guide so future corrections have one clear home.

The destination finder now filters regions, dungeons, raids and battlegrounds while retaining the distinction between official names and community level ranges. Complete map coverage and entrance coordinates remain unverified here.

The new systems guide pairs Legacy and Camping with two images from Blizzard’s game page. Each image is credited to its original source. A screenshot can illustrate a system without proving that its visible numbers or rewards are final.

The guide also turns visual and control announcements into practical questions for a first testing session. This is where to start if convenience, alts or playing with a controller matters more to you than picking a talent build immediately.

The community FAQ answers practical questions raised in player discussions: how character names work, how to check access, and what rules matter when forming a party.

Two-part character names are unique as a complete combination within a region. For a group outing, agree on ruleset and faction before choosing characters. Check access and reservation dates before planning the first session.

Blizzard’s Deep Dive names six additions for the original races: Undead Paladin, Dwarf Shaman, Orc Mage, Human Hunter, Gnome Priest and Troll Warlock.

Start with your party’s faction, then choose a class. A Horde player interested in Paladin can consider Undead, while an Alliance player interested in Shaman can consider Dwarf. The race-class table shows the complete set of options.

Once the combination fits your group, compare racial abilities and class talents to decide how you want the character to play.

The September 12 WOWTBC.GG overview describes abilities for Mage, Priest, Rogue, Shaman and Warlock, alongside Warrior and Paladin changes.

Start with the effect that changes your play: an extra spell, a different resource interaction or a new talent requirement. The class comparison helps you find the ability; the talent planner shows how it fits the points available at your level.

Blizzard’s What’s Next panel recap covers world destinations and character options. See the world guide and Skyborne guide for the practical details.

The official game page and upgrade announcement also make the access comparison more useful. Our Beta guide now separates opt-in selection, included edition benefits, name reservation and live-game dates. It records inconsistent time-zone wording rather than hiding it inside a countdown.

For the broader premise, read Blizzard’s Carve a New Path announcement. For the original visual reveal, use our official trailer library, which links directly to the Warcraft uploads.