[{"data":1,"prerenderedAt":487},["ShallowReactive",2],{"site-settings":3,"article:\u002Fresources\u002Fbriefings\u002Fforever-launch-day-one-known-issues-layers-faction-lock":16,"article-surround:\u002Fresources\u002Fbriefings\u002Fforever-launch-day-one-known-issues-layers-faction-lock":476},{"id":4,"description":5,"email":6,"extension":7,"footerNote":8,"legalNotice":9,"locale":10,"meta":11,"name":12,"stem":13,"url":14,"__hash__":15},"settings\u002Fsettings.yml","Compare World of Warcraft realms by expansion, region, population and play style.","listings@realmlist.org","yml","An independent realm directory.","Not affiliated with Blizzard Entertainment.","en",{},"RealmList","settings","https:\u002F\u002Frealmlist.org","QXaYspLUSxnrVumL6oFir6PInhNsRw-yJchxEYSe1AU",{"id":17,"title":18,"author":19,"body":20,"category":418,"description":419,"draft":420,"extension":421,"featured":420,"meta":422,"navigation":423,"path":424,"publishedAt":425,"seo":426,"sitemap":427,"sources":432,"stem":466,"tags":467,"updatedAt":474,"__hash__":475},"articles\u002Fresources\u002Fbriefings\u002Fforever-launch-day-one-known-issues-layers-faction-lock.md","Forever's First Day: Clean Queues, Empty Capitals, and the Bug List Blizzard Published Itself","RealmList Editorial",{"type":21,"value":22,"toc":406},"minimark",[23,40,43,48,51,54,60,67,71,86,89,171,178,182,193,196,200,207,217,228,231,260,263,267,282,289,293,308,318,326,329,333,340,350,354,357,378,385,395,400],[24,25,26,30,31,35,36,39],"p",{},[27,28,29],"em",{},"World of Warcraft: Forever"," went live in every region at the same moment: ",[32,33,34],"strong",{},"3:00 p.m. PST on November 4",", which is 23:00 UTC and ",[32,37,38],{},"7:00 a.m. on November 5 in Beijing",". Twenty-two years of separate realms ended, the login queues that everyone had braced for mostly did not arrive, and the argument about the game moved within a few hours from \"will the servers hold\" to \"why is Stormwind empty\" and \"why can't I roll Horde on PvP\".",[24,41,42],{},"That is a strange pair of problems for a launch, and it is the pair worth understanding, because both come from the same design decision and neither will be fixed by waiting out a queue.",[44,45,47],"h2",{"id":46},"the-launch-short-queues-and-one-specific-glitch-at-the-gate","The launch: short queues, and one specific glitch at the gate",[24,49,50],{},"The first-hand accounts agree on the shape of it. Eurogamer reports from its own session that, for European players who stayed up from about 11 p.m. to 3:50 a.m. UK time, the login queues were \"short and constantly moving\", with no random disconnects and at most a lost spell cast or two. Space4Games, publishing its own launch-night screenshots, was placed at position 783 with an estimated three-minute wait.",[24,52,53],{},"The one reproducible snag was at the selection screen: players who connected the instant the servers came up found the ruleset boxes unclickable. Backing out and rejoining the queue cleared it, though for some it took several attempts, and the whole thing had settled within roughly half an hour.",[24,55,56,57],{},"Blizzard's own read on the night, from executive producer Holly Longdale on X, as quoted in full by Eurogamer: ",[27,58,59],{},"\"At the risk of jinxing things, so far so goodish which is crazy by itself. The team prepared a lot since the wildness of Beta. And this launch was crazier than the insanity we imagined but thankfully the team built plans and contingencies. They are incredible in my opinion.\"",[24,61,62,63,66],{},"On attention rather than population, Eurogamer also notes Forever climbing to the top of Twitch's most-viewed games during the first day, with streamer Ahmpy at roughly 18,300 live viewers. ",[32,64,65],{},"Blizzard has published no player or subscription numbers",", and it has not done so since around 2015; treat any figure you see circulating as an estimate by whoever posted it.",[44,68,70],{"id":69},"blizzards-own-bug-list-published-the-next-morning","Blizzard's own bug list, published the next morning",[24,72,73,74,77,78,81,82,85],{},"At ",[32,75,76],{},"15:42 UTC on November 5"," — 07:42 Pacific, 23:42 Beijing — Blizzard opened a Known Issues thread, prefaced with a framing worth reading literally: these are issues the team has judged ",[27,79,80],{},"\"notable, impactful, and already tracked with plans to fix in the future\"",", and the list is explicitly ",[27,83,84],{},"\"not a comprehensive list\"",".",[24,87,88],{},"What is on it:",[90,91,92,105],"table",{},[93,94,95],"thead",{},[96,97,98,102],"tr",{},[99,100,101],"th",{},"Area",[99,103,104],{},"Issue Blizzard lists",[106,107,108,117,125,132,139,147,155,163],"tbody",{},[96,109,110,114],{},[111,112,113],"td",{},"Dungeons",[111,115,116],{},"In Razorfen Kraul, a cauldron near Roogug can be fallen into, trapping the character",[96,118,119,122],{},[111,120,121],{},"Gamepad",[111,123,124],{},"An error may be generated when deleting more than one rare or epic item",[96,126,127,129],{},[111,128,121],{},[111,130,131],{},"The Xbox Elite 3 (Actium) controller is not correctly recognised, and its paddle buttons cannot be bound",[96,133,134,136],{},[111,135,121],{},[111,137,138],{},"Push-to-talk keyboard instructions may be shown unintentionally when joining a voice channel",[96,140,141,144],{},[111,142,143],{},"NPCs",[111,145,146],{},"PvP vendors are temporarily unavailable in all locations — Orgrimmar, Stormwind and Dalaran",[96,148,149,152],{},[111,150,151],{},"Quests",[111,153,154],{},"\"Vorsha the Lasher\" in Ashenvale is disabled until a crash bug is fixed",[96,156,157,160],{},[111,158,159],{},"User interface",[111,161,162],{},"Bank pages display as pages, pushing the tabs outside the frame",[96,164,165,168],{},[111,166,167],{},"World",[111,169,170],{},"The Stormwind Keep entrance may not look as intended, including unintended flashing textures",[24,172,173,174,177],{},"Two things follow from that table. First, the PvP vendors are gone for now: the post says only \"temporarily unavailable\", gives no date, and that means anyone planning to spend honour in the opening days has nowhere to spend it. Second, and more useful for reading Blizzard's posture: ",[32,175,176],{},"the faction lock, the empty capitals and the missing boats are not on this list",", even though all three were acknowledged separately. Absence from this thread means \"not on this list\", not \"not happening\".",[44,179,181],{"id":180},"the-one-hotfix-with-a-named-cause-invite-a-friend","The one hotfix with a named cause: Invite-a-Friend",[24,183,184,185,188,189,192],{},"The clearest fix of the first day landed before most of Europe woke up. At ",[32,186,187],{},"02:43 UTC on November 5",", Kaivax confirmed a live hotfix for players who entered through an Invite-a-Friend code: they had been ",[27,190,191],{},"\"unexpectedly restricted from using certain chat channels, leveling past 10, participating in guilds, forming parties, or trading items with other players.\""," The advised remedy is to log out and back in.",[24,194,195],{},"That is a specific failure worth naming plainly. The whole point of the invite programme is to put a returning friend into a group with you for a week; the bug removed grouping, guilds, trading and part of chat from exactly those players. Blizzard's post does not say how many accounts were affected, and some players on the forums reported that a single relog did not immediately clear it.",[44,197,199],{"id":198},"layers-blizzard-admits-it-split-the-world-too-finely","Layers: Blizzard admits it split the world too finely",[24,201,202,203,206],{},"The complaint that dominated the first twelve hours was the opposite of a launch-day crowd. Players reached capital cities and found almost nobody: one thread opened with a player counting ",[27,204,205],{},"\"maybe 8 people AT BEST\""," in Ironforge while trade chat showed a channel population in the forties.",[24,208,209,210,213,214],{},"Blizzard's senior game designer Josh \"Aggrend\" Greenfield answered it on the forums at ",[32,211,212],{},"06:35 UTC on November 5"," (22:35 Pacific on November 4), in terms that concede the tuning rather than the design: ",[27,215,216],{},"\"we are aware of some issues with certain areas not feeling as populated as they should. We will be tweaking some numbers tomorrow to help things feel a bit more lively.\"",[24,218,219,220,223,224,227],{},"\"Tomorrow\" there means ",[32,221,222],{},"November 5 Pacific time",", which for readers on UTC+8 is the small hours of ",[32,225,226],{},"November 6",". No numbers, thresholds or target populations were given, and we found no follow-up post confirming the tweak had shipped before we published this.",[24,229,230],{},"Worth keeping separate in your head: Forever's layering has two prompts that push in opposite directions, and coverage has blurred them.",[232,233,234,246],"ul",{},[235,236,237,240,241,85],"li",{},[32,238,239],{},"The crowded-zone prompt."," When an area is saturated, the UI offers a refresh — move to another instance now, or wait about five minutes. This is the load-shedding mechanism Blizzard described in its pre-launch technical briefings, and we covered it in ",[242,243,245],"a",{"href":244},"\u002Fresources\u002Fguides\u002Fforever-realmless-architecture-explained","our guide to the realmless architecture",[235,247,248,251,252,255,256,259],{},[32,249,250],{},"The group prompt."," When you join a party and your friend is on a different layer, the game is supposed to offer you a way across. At ",[32,253,254],{},"15:51 UTC on November 5",", answering a report that grouped players could not see each other, Kaivax described the intended flow step by step: a blue message in the lower right after accepting the invite, clickable, producing a pop-up with a ",[32,257,258],{},"\"Refresh Now\""," button, which should place you with your party.",[24,261,262],{},"Players in that same thread reported that no pop-up appeared for them, and that what worked was logging out and back in, or walking to the next zone together and back. None of that is officially confirmed as a fix; it is what players report working.",[44,264,266],{"id":265},"boats-and-zeppelins-portals-where-the-docks-are","Boats and zeppelins: portals where the docks are",[24,268,269,270,273,274,277,278,281],{},"The transport failure was real, and Aggrend described its cause at ",[32,271,272],{},"06:39 UTC on November 5",": ",[27,275,276],{},"\"We are aware of some issues with transports such as boats and zeppelins becoming lost in the maelstrom for extended periods of time.\""," The temporary remedy was to spawn ",[32,279,280],{},"portals near most transport docks and inside the zeppelin towers",", with a proper fix promised \"in the morning\" and the portals to be removed once that fix was verified.",[24,283,284,285,288],{},"Two caveats. \"In the morning\" is Pacific time, so UTC+8 readers should read it as November 5 evening into November 6. And ",[32,286,287],{},"we have not seen an official confirmation that the fix shipped or that the portals were removed"," — the Known Issues thread does not mention transports at all, and players were still discussing the portals hours later, some asking Blizzard to keep them permanently as a convenience.",[44,290,292],{"id":291},"the-faction-lock-the-one-problem-you-cannot-queue-past","The faction lock: the one problem you cannot queue past",[24,294,295,296,299,300,303,304,307],{},"Five minutes after the servers came up, at ",[32,297,298],{},"23:18 UTC on November 4",", the loudest new thread on the Forever forums was not about queues. It was about this message: ",[27,301,302],{},"\"This faction is currently unavailable on this ruleset due to population imbalance.\""," By our check it had ",[32,305,306],{},"217 posts and 12,786 views",", with a second thread passing 181 posts by mid-morning and a third — \"Faction Imbalance is unfixable once it starts\" — at the same count by 11:45 UTC.",[24,309,310,311,314,315,85],{},"Two different strings are in circulation, and players kept conflating them: the faction-unavailable message above, and ",[27,312,313],{},"\"Creation of that type of character is currently throttled\"",", which appears to be a broader creation throttle and which some players saw on non-PvP rulesets too. Neither ships with a countdown, and ",[32,316,317],{},"Blizzard has published no threshold, no lock duration and no estimate of when a faction reopens",[24,319,320,321,325],{},"The important context is that this is not a launch-day bug. Blizzard announced the mechanism before launch — faction-balance controls on the PvP ruleset, modelled on Season of Discovery, where new character creation can be limited for the majority faction — as we reported when the ",[242,322,324],{"href":323},"\u002Fresources\u002Fbriefings\u002Fwow-forever-rp-pvp-ruleset-launch","RP-PvP ruleset was confirmed",". Threads about the same lock exist from October 17, October 27 (during name reservation) and November 1. What changed on November 4 is scale, and the fact that the realmless design removes the old escape hatch: on a normal realm launch, an over-full faction meant picking a different server. Here there is nothing to pick. Waiting for the other faction to grow is the entire mechanism, which is precisely what makes it feel like a wall.",[24,327,328],{},"The counter-argument is also live on the forums, in a smaller thread titled \"Please do not back down from faction locks and balancing Blizzard\". A 50\u002F50 split is the design goal, and the alternative — the imbalance that turned some Classic realms into a monoculture — is what the lock exists to prevent. Both positions are player opinion; neither is Blizzard policy.",[44,330,332],{"id":331},"characters-on-the-wrong-ruleset-reports-no-confirmation","Characters on the wrong ruleset: reports, no confirmation",[24,334,335,336,339],{},"A separate cluster of reports has no official answer at all. Players say characters created during name reservation on one ruleset — PvP, or Roleplay — appeared on ",[32,337,338],{},"Roleplay-PvP"," instead, and in some cases the original characters were gone from the ruleset they were made on. One thread opened at 09:17 UTC on November 5 describes three reserved characters on Horde PvP being moved to RP-PvP after the overnight maintenance, and the poster says they have screenshots. Another, filed as a bug at 02:29 UTC, describes making three characters on PvP that somehow existed on RP-PvP as well.",[24,341,342,345,346,349],{},[32,343,344],{},"None of this is confirmed by Blizzard",", and we have not reproduced it. One documented behaviour is adjacent and should not be confused with it: Oceanic players connecting to Australian data centres were told before launch that they must create characters on Roleplay or Roleplay-PvP or their ruleset would not appear — a rule, not a bug. That does not explain reports from players who say they never selected RP-PvP. If you are affected, the practical warning is to check which ruleset a character actually sits on ",[32,347,348],{},"before"," you level it, because deletion is the only fix players have found, and re-creating can run straight into the faction lock.",[44,351,353],{"id":352},"what-we-are-watching-next","What we are watching next",[24,355,356],{},"Three things, all with timestamps we can check rather than promises:",[358,359,360,366,372],"ol",{},[235,361,362,365],{},[32,363,364],{},"The layer tweak."," Announced for November 5 Pacific — November 6 in the small hours for UTC+8. Population in capitals is the observable, and no target has been published.",[235,367,368,371],{},[32,369,370],{},"The transport fix and the portal removal."," Promised for the morning of November 5 Pacific. Unconfirmed at the time of writing.",[235,373,374,377],{},[32,375,376],{},"Whether the faction lock ever reaches the official list."," It is the largest player complaint of the launch and the only one with no stated resolution path. Its absence from the November 5 Known Issues thread is the fact to track.",[24,379,380,381,384],{},"We have seen no announced change to ",[32,382,383],{},"December 9",", when the first raid tier is due to open.",[24,386,387],{},[388,389],"img",{"alt":390,"height":391,"loading":392,"src":393,"width":394},"Editorial illustration: a hooded traveller with a staff stands on an old stone bridge at dusk, facing three overlapping copies of the same torch-lit harbour city",1024,"lazy","https:\u002F\u002Frealmlist.org\u002Fimages\u002Farticles\u002Fbriefings\u002Fforever-launch-day-one-known-issues-layers-faction-lock.webp",1536,[24,396,397],{},[27,398,399],{},"Original editorial illustration by RealmList, generated for this article. This is artwork, not game footage or official promotional material.",[401,402,403],"note",{},[24,404,405],{},"Verified on November 6, 2026 (Asia\u002FShanghai). The launch moment, the 217-post faction thread, the Invite-a-Friend hotfix, the layer and transport statements, the Known Issues list and Kaivax's \"Refresh Now\" description were read directly on Blizzard's official forums at the thread IDs and timestamps given in the sources; the Known Issues list was version 1 at 15:42 UTC on November 5 and may be edited afterwards. Queue behaviour, the unclickable selection screen, the empty-capital counts and the \"no pop-up appears\" reports come from first-hand accounts by Eurogamer and Space4Games and from player forum threads — they are not Blizzard statements, and we did not observe them ourselves. RealmList has no access to the live client and has not played the release build, so nothing here is a hands-on test. The faction lock's mechanics are player-observed; Blizzard has published no numbers, thresholds or durations, so any figure you see elsewhere is someone's estimate. Whether the layer tweak, the transport fix and the portal removal actually shipped is unverified at the time of writing. The December 9 raid date is Blizzard's, unchanged since it was announced.",{"title":407,"searchDepth":408,"depth":408,"links":409},"",2,[410,411,412,413,414,415,416,417],{"id":46,"depth":408,"text":47},{"id":69,"depth":408,"text":70},{"id":180,"depth":408,"text":181},{"id":198,"depth":408,"text":199},{"id":265,"depth":408,"text":266},{"id":291,"depth":408,"text":292},{"id":331,"depth":408,"text":332},{"id":352,"depth":408,"text":353},"briefings","WoW: Forever opened on November 4 with the smoothest launch Blizzard has managed in years, then handed players a different set of problems: layers tuned so high that capitals look deserted, a Horde faction lock with no published exit, and a short official list of what is actually broken. Here is what Blizzard has confirmed, what it has only acknowledged in passing, and what the timestamps say.",false,"md",{},true,"\u002Fresources\u002Fbriefings\u002Fforever-launch-day-one-known-issues-layers-faction-lock","2026-11-06",{"title":18,"description":419},{"loc":424,"images":428,"changefreq":430,"priority":431},[429],{"loc":393},"daily",0.8,[433,436,439,442,445,448,451,454,457,460,463],{"label":434,"url":435},"Blizzard Entertainment (Kaivax) — Known Issues - WoW Forever - Updated Nov. 5 (official forum thread 2402363, posted 2026-11-05 15:42 UTC, version 1)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fknown-issues-wow-forever-updated-nov-5\u002F2402363",{"label":437,"url":438},"Blizzard Entertainment (Kaivax) — Issues Resolved for Invite-a-Friend Players (official forum thread 2401646, posted 2026-11-05 02:43 UTC)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fissues-resolved-for-invite-a-friend-players\u002F2401646",{"label":440,"url":441},"Blizzard Entertainment (Aggrend) — reply on transports and temporary portals, thread \"Zeppelins broken?\" (official forum thread 2401777, post 15, 2026-11-05 06:39 UTC)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fzeppelins-broken\u002F2401777\u002F15",{"label":443,"url":444},"Blizzard Entertainment (Aggrend) — reply on under-populated zones, thread \"Why do I see maybe 8 people inside the main city?\" (official forum thread 2401806, post 27, 2026-11-05 06:35 UTC)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fwhy-do-i-see-maybe-8-people-inside-the-main-city\u002F2401806\u002F27",{"label":446,"url":447},"Blizzard Entertainment (Kaivax) — reply on group phasing and the \"Refresh Now\" prompt (official forum thread 2402367, post 2, 2026-11-05 15:51 UTC)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fphasing-issues-with-group-still-persist-from-beta\u002F2402367\u002F2",{"label":449,"url":450},"Blizzard forums — \"This faction is currently unaivalable on this ruleset due to population imbalance\" (player thread 2401311, opened 2026-11-04 23:18 UTC; 217 posts and 12,786 views when we checked)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fthis-faction-is-currently-unaivalable-on-this-ruleset-due-to-population-imbalance\u002F2401311",{"label":452,"url":453},"Blizzard forums — \"[wow forever] My three characters were moved to Roleplay PvP\" (player thread 2402015, opened 2026-11-05 09:17 UTC)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fwow-forever-my-three-characters-were-moved-to-roleplay-pvp\u002F2402015",{"label":455,"url":456},"Eurogamer — World of Warcraft: Forever is off to a great start with Blizzard's smoothest launch in memory (Connor Makar, November 5, 2026; first-hand European account and Holly Longdale's X post quoted in full)","https:\u002F\u002Fwww.eurogamer.net\u002Fworld-of-warcraft-forever-launch-smooth",{"label":458,"url":459},"Eurogamer — Forever's launch continues as it soars to the top of Twitch's most viewed games (November 5, 2026)","https:\u002F\u002Fwww.eurogamer.net\u002Fworld-of-warcraft-forever-launch-twitch-most-viewed",{"label":461,"url":462},"Space4Games — WoW Forever Launch: Short Queues, but an Empty World (first-hand launch account, updated November 5, 2026)","https:\u002F\u002Fspace4games.com\u002Fen\u002Fgames-en\u002Fwow-forever-launch-2",{"label":464,"url":465},"WoWSoD Pro — WoW Forever Launch Night: Short Queues, Horde Locked Out of PvP, Near-Empty Cities and Lost Zeppelins (November 5, 2026; independent write-up cross-referencing Wowhead and Icy Veins)","https:\u002F\u002Fwowsod.pro\u002Farticles\u002Fwow-forever-launch-night-horde-locked-empty-cities","resources\u002Fbriefings\u002Fforever-launch-day-one-known-issues-layers-faction-lock",[468,469,470,471,472,473],"WoW Forever","Launch","Layering","Rulesets","Faction Balance","Hotfix",null,"DbudOqG-Ar2QqbFFe76OGlpvLeTU1MiajYvinCxFAXE",[477,482],{"title":478,"path":479,"stem":480,"description":481,"children":-1},"Whitemane's Road Ahead: Stormstout Opens December 12, Naxxramas Goes Flex, Ascended Dungeons Arrive — and a Warning About Stolen Passwords","\u002Fresources\u002Fbriefings\u002Fwhitemane-road-ahead-stormstout-naxx-flex-ascended","resources\u002Fbriefings\u002Fwhitemane-road-ahead-stormstout-naxx-flex-ascended","Whitemane's November 3 roadmap post packs a week of changes and a launch date into one announcement: a flexible 10-30 player Naxxramas Normal with no instance lockout, harder Ascended heroics from November 4, Personal Loot across every level-80 raid, a Stormstout launch on December 12 with realm closures to follow — and the disclosure that about 50 hijacked accounts trace back to a breached WotLK realm that stored passwords in plaintext.",{"title":483,"path":484,"stem":485,"description":486,"children":-1},"Blizzard Quietly Rewrote Its Own Forever Notes: Gamepad Support Went From a \"Complete Functional State\" to a \"Functional Beta\" Before Launch","\u002Fresources\u002Fbriefings\u002Fforever-gamepad-beta-state-edit-november-4","resources\u002Fbriefings\u002Fforever-gamepad-beta-state-edit-november-4","The gamepad paragraph in Blizzard's November 2 development notes no longer says what it said when we quoted it. The forum post now sits at version 3, last edited at 2026-11-04 02:12 UTC, and the sentence reads \"has entered a functional Beta state\" — matching the dedicated November 4 controller article instead of the earlier wording. Here is the evidence chain, what beta actually means on launch day, every controller binding Blizzard has published, and one binding the two documents still disagree about.",1794069776025]