World of Warcraft: Forever opens in a matter of hours, and the sentence we quoted to you two days ago is not the sentence sitting on Blizzard's page today.

The gamepad paragraph in the official development notes — the Kaivax post of November 2 Pacific time, thread 2360696, post 9 — read "Gamepad Support has entered a complete functional state" when it went up at 03:20 UTC on November 3. Right now it reads "Gamepad Support has entered a functional Beta state." Same post, same URL, different claim.

This is not a mirror site drifting. The forum's own metadata reports post id 30732723 at version 3, with updated_at of 2026-11-04 02:12 UTC — roughly eleven hours before the launch article was last touched, and about twenty hours before the servers open.

The evidence chain, because this one is checkable

Read down that column and the sequence is unambiguous: for at least fifteen hours on November 3, Blizzard's notes and Blizzard's marketing articles described the same feature in incompatible terms. Then, early on November 4, the notes were edited to match the articles.

The forum does not expose revision history to anonymous readers, and Blizzard has published no correction notice, so we cannot say which of the post's three versions changed this sentence, only that the sentence changed. What we can say is what we read ourselves on November 3, what a Chinese outlet published at 18:14 UTC that same day, and what the JSON now returns.

Why this is worth more than a wording quibble

Two reasons.

First, it is the pre-launch change that client diffing cannot catch. Every other adjustment in the last month was readable out of build 1.60.1.70707 — spells, cooldowns, talent rows. An edit to a forum post is invisible to that method, and the post is the document players cite when they argue about whether a feature shipped finished.

Second, "complete" and "beta" are not synonyms in a launch week. "Complete functional state" reads as done. "Functional beta" reads as playable, unfinished, expect gaps. Blizzard now says the second one, twice, in the two documents a player is most likely to read before logging in.

What "beta" means in practice, in Blizzard's own words

Strip the labels and the substance is consistent across all three documents, which is the more useful takeaway:

• Core play is covered. Movement, spells, interactions, loot pickup, menu navigation and UI navigation all work on a controller, and Blizzard calls these "all major gameplay and core user interface experiences."
• The interface is not finished. From the walkthrough: "Not every screen has a footer yet: gamepad support remains in a functional beta, and interface updates are ongoing."
• You still need a keyboard. Typing in chat requires one, and the shortcut list deliberately routes chat to a button rather than solving text entry. Blizzard states the direction plainly: reducing keyboard dependence "remains a development goal, with a keyboard-free experience as the longer-term aim."
• New in this build: AoE items on the gamepad bar can be placed at a targeted spot and confirmed with a second press; the ruleset selection screen is navigable; cinematics can be skipped or exited; friendly corpses and critters are targetable; enemy players are selectable by hostile analog targeting regardless of PvP flag; flight paths can be ended early at the next node; pets take move commands; and the bag UI gained remaining-slot and ammo counters.

So the honest pre-launch answer is: playable end to end, not finished, keep a keyboard within reach. That is a long way from "complete," and it is what the current text says.

Setting it up

Escape → Options → Gamepad, under Gameplay. Blizzard says all XInput-compatible controllers work and the UI ships Xbox and PlayStation button icons. Settings are grouped into Camera, HUD Modifier, Frame Focus Style, Action Bars, Targeting and Raid Targeting Options, and the same screen is where Edit Mode customisation lands. On controllers with supported lighting the light turns red for Horde, blue for Alliance.

A gamepad legend sits in the upper-left of the main screen and expands contextually. Most panels carry footers describing their controller interactions — most, not all.

The bindings, as published

The action bar maths is worth doing once. Three sets, each containing four bars with 28 slots combined — so 84 spell and ability slots in total, all reachable without opening a menu. Blizzard's own example is a mage putting Polymorph on Up, Fireball on LT + Up, Frostbolt on RT + Up and Blizzard on LT + RT + Up, and it explicitly labels those example assignments rather than fixed bindings.

One binding the two documents still disagree about

The notes say LB + RB + Face Down selects your Focus Target. The walkthrough published sixteen hours and forty minutes later assigns LB + RB + Down to opening Chat, and puts Change Focus Frame on the View button.

Both texts are live. One of them is wrong, or the binding changed between the two documents being written, and we cannot tell which from the outside — there is no build in the wild to test, because the beta closed on October 23. If you tank or heal on a controller tonight, treat the Focus Target bind as unverified until you press it.

What we are correcting on our side

Our November 4 briefing on the development notes quoted "complete functional state" in good faith — it was the text at the time, and it is what every Chinese outlet published. That article now carries an update marking the edit. Our launch and first-login guide has also been changed back: it had been amended to say the beta wording was superseded, and that amendment no longer holds.

Worth saying plainly, since we got the direction wrong: when a developer and a marketing page disagree, the marketing page can be the more current one.

Original editorial illustration by RealmList, generated for this article. This is artwork, not game footage or official promotional material.