Von Online Games VIP Editorial
·
IGN reports that WoW Forever name reservations faced login queues, regional access problems, and character creation errors before the November 4 launch.
World of Warcraft: Forever's character-name reservation feature ran into technical problems before the game's full launch. IGN reports that European players initially struggled to access the feature, while North American players later faced login queues and disconnects.
Blizzard subsequently pushed a fix to European users, according to IGN, but the problems did not end there. The outlet later reported that players who reached character creation could still receive a timeout error when attempting to reserve a name. Blizzard was aware of that issue and working on a fix, although the supplied report does not confirm when the problem would be fully resolved.
The situation matters because name reservations are intended to give players a head start before launch. Instead, access problems meant that some players could not reliably reach the reservation screen, while others could not complete the final step. The feature is scheduled to precede World of Warcraft: Forever's full launch on November 4.
IGN reported that the reservation feature was initially intended to become available in Europe before opening for North American servers at 1 p.m. PT and 4 p.m. ET. Blizzard's Battle.net message told players that European reservations were delayed while the team addressed final technical issues, according to IGN.
The first visible problem was access through the Battle.net launcher. IGN reported that many European players saw a disabled Play button, preventing them from launching the latest version of World of Warcraft: Forever and attempting to reserve a name. That issue did not necessarily affect every player in the same way, but it created an immediate barrier for anyone unable to start the client.
IGN also reported that some players discovered their Battle.net launcher was set to the wrong region. Changing the account or launcher region back to Europe restored access for at least some users, based on player reports cited by the outlet. That workaround came from the community rather than from an official Blizzard support instruction in the supplied source, so it should not be treated as a confirmed universal fix.
Blizzard later pushed a fix to European users, with players who were still affected advised to log out and back in, IGN reported. The source does not specify the technical cause of the disabled Play button, the number of affected accounts, or whether the regional setting explained all European access failures.
When the feature went live in the United States, IGN reported that players encountered login queues. Some users reportedly reached the end of the queue only to be disconnected. At the time covered by the report, Blizzard had not announced that the North American reservation window would be delayed.
The reservation system is designed to let players make decisions before the full release rather than competing for names after launch. According to IGN, players are supposed to launch the current version of World of Warcraft: Forever, select a ruleset such as PvE or PvP, and create up to three characters with reserved names.
That structure gives the feature more importance than a simple account check. A player who cannot log in during the reservation window may be unable to secure a preferred name or establish the characters they want ready for launch. The supplied source does not confirm whether reserved names are permanently protected, how long the reservations last, or whether unused reservations will expire.
The ruleset selection also makes access relevant before the game opens fully. IGN reported that players were expected to choose among options including PvE and PvP while creating their characters. If the ruleset options remain unavailable, reaching the client does not necessarily mean the reservation process can be completed.
That distinction is important when assessing the reports. There were at least two separate points of failure described by IGN: some players could not launch through Battle.net, while others could enter but encountered a timeout at the end of character creation. A workaround that gets a player to the ruleset screen therefore may not solve the later creation error.
Analysis: The practical risk for players is not only losing access to a name. A disrupted reservation window can make it harder to confirm which server ruleset to use, test account access, and verify that the game client is ready before launch. Those are reasonable concerns based on the reported sequence of failures, not evidence that every player will experience the same problem.
Blizzard's response remains incomplete
Blizzard's response, as described by IGN, changed during the reservation window. The Battle.net notice first stated that European reservations were delayed because of technical issues. Later, IGN reported that Blizzard had pushed a fix to European users and advised those still affected to log out and back in.
For North America, IGN reported that the feature went live despite the login queues and that no delay had been announced at the time of writing. The report does not establish whether Blizzard considered the queues expected launch demand, a separate service problem, or part of the same issue affecting Europe.
IGN later reported that Blizzard was aware of the character creation timeout and working on a fix. The source does not include a Blizzard statement explaining the cause, a projected resolution time, or confirmation that the fix had been deployed globally. It also does not confirm whether players who saw the timeout had their names held temporarily or had to restart the process.
This leaves the public status difficult to summarize as a single resolved or unresolved incident. European launcher access reportedly improved after a fix, but character creation still produced errors for at least the source's tester. North American users could reach the service, but some were disconnected from queues. Those developments should be tracked separately until Blizzard confirms that the full flow works from login through completed reservation.
Analysis: A reservation system has a concentrated workload because many players are motivated to use it during a narrow period. That makes queues and intermittent failures especially disruptive. The source does not provide player counts or server capacity information, so it is not possible to determine whether the reported problems came from unusually high demand, a regional configuration issue, a client problem, or several causes at once.
The reported regional differences are also worth watching. Europe began with a delayed feature and launcher access complaints, while North America opened with queues and disconnects. This does not prove that the regions share a common technical fault. It does suggest that players should avoid assuming that a solution observed in one region will automatically apply to another.
Players may also need to distinguish between a launcher problem and an account or character-creation problem. IGN reported that changing the Battle.net region helped some European users whose Play button was disabled. However, the same report later described a character creation timeout after access was restored. Reaching the game is therefore only one checkpoint in the process.
The timing before the full launch adds pressure. IGN reported that World of Warcraft: Forever's beta ended the previous week, leaving the name reservation period between the beta and the November 4 launch. That gives Blizzard an opportunity to identify and correct problems before release, but it also means the reservation period is the main practical test of whether players can access the launch client and complete early setup.
IGN also reported that it spoke with Blizzard principal game designer Kris Zierhut about the MMO's future. The source said regular updates may be planned and that areas associated with later expansions, including Northrend and Pandaria, could potentially become accessible. Those longer-term comments are separate from the immediate reservation problems, and the supplied report does not confirm release timing, content details, or a specific plan for either continent.
The next useful evidence will be a clear Blizzard status update confirming whether name reservations are available in each region and whether the full process can be completed. That update would ideally address the launcher access problem, queue disconnects, and character creation timeout separately rather than treating all three as one issue.
Players should also watch for confirmation about the status of names after a failed attempt. The supplied source does not say whether a timeout can consume one of the three character slots, reserve a name despite showing an error, or leave the account unchanged. Until Blizzard explains that behavior, repeating the process could carry uncertainty for affected users.
Another open question is whether the regional launcher setting will continue to cause confusion. IGN reported that at least some users had the Battle.net client set to the Americas region while trying to access European reservations. Blizzard has not been quoted in the supplied source explaining why that setting changed or whether the later fix removed the need for manual correction.
Finally, the November 4 launch will show whether these problems were limited to the reservation service or reflect wider readiness concerns. That conclusion cannot be made from the current reports alone. For now, the confirmed picture is narrower: Blizzard's reservation rollout experienced regional delays, launcher access failures, login queues, disconnections, and character creation timeouts, while the company worked on fixes.
OnlineGamesVIP is analyzing IGN's report, not presenting an independent hands-on test or a separate verdict on World of Warcraft: Forever. The most reliable next step is to wait for Blizzard's own confirmation that name creation and reservation work consistently across the supported regions.