WoW Forever Name Reservations Hit by Bug That Blocked Ordinary Names

World of Warcraft Forever has run into an early character-name reservation problem after eligible players found that the game was rejecting many seemingly ordinary names as restricted. The issue surfaced when servers opened for character creation following the end of the recent beta, giving players who purchased Skyborne packs an opportunity to secure names ahead of the game's next phase.

For some players, the process worked as intended. For others, the character creation screen displayed a message saying the desired name was on the restricted list, even when the name did not appear to contain profanity, impersonation attempts, or an obvious reference to a major Warcraft character. Blizzard has acknowledged the problem and said a bug in the name-filtering process caused the system to be much more aggressive than intended.

The incident matters because name reservations are often a high-stakes moment for MMO communities. Players may have used the same identity for years, want a name that matches a guild or group theme, or simply value a short and recognizable character name. When reservation access is tied to a paid pack, an unexplained rejection can be particularly frustrating, even if the underlying technical issue is temporary.

An overly broad restriction rule

Community manager Kaivax explained that WoW Forever uses a restricted-name list in addition to whatever checks are in place for profanity and other prohibited language. Such lists can be used to reserve important lore names, prevent players from using names that could create confusion, and block entries that cause technical problems.

For useful background on this topic, read Atari Hotel Breaks Ground in Phoenix With Esports Arena, Creator Studios Planned.

That broad objective is familiar to long-running online games. A developer may not want thousands of players creating characters with the names of central story figures, and it may also need to guard against terms that interact badly with account, chat, customer-service, or database systems. The difficulty is ensuring that these protections do not accidentally catch a large portion of harmless player-created names.

In this case, Blizzard determined that a bug had made the filter overly restrictive. Kaivax pointed to one especially revealing example: names containing the letter sequence c-o-n were being blocked incorrectly. Since those three letters occur in a wide range of ordinary English words and invented fantasy names, the potential impact was much larger than a restriction aimed at a single reserved term.

A name system can seem simple from the player side, but it has to compare every submission against multiple sets of rules. It may check for words, partial strings, special characters, spacing, capitalization, protected terms, and variations designed to evade moderation. If one part of that process treats a small string as a match in too many contexts, the result can be a wave of false positives. That appears to be what happened during WoW Forever's reservation window.

Players highlighted broader false positives

Responses from the community suggested the con issue was not the only reason players were being turned away. One player, Nursejoy, argued that the restricted list appeared to reach beyond major lore figures and into much more generic NPC terminology. They cited the words Nurse and Officer as examples of names that do not necessarily evoke major Warcraft characters but could nevertheless be disallowed when included within longer character names.

Nursejoy also listed 23 attempted character names containing the word nurse that they said could not be reserved. That feedback illustrates why name-filter disputes can become difficult to evaluate from isolated examples. A word may be restricted because it appears in a named NPC, because it overlaps with an internal rule, or because a broader matching error is affecting it. From a player's perspective, however, the important issue is straightforward: a normal-looking name was rejected without an explanation that made sense at the time.

Blizzard said the relevant fixes should have gone live with a server restart. There were still player reports of reservation problems after that restart, so it is not yet clear whether every unintended restriction was resolved immediately or whether some names were being rejected for separate, legitimate reasons. The stated bug involving con does appear to have been addressed; the name "Concon Concon" was successfully reserved after the fix was deployed.

That does not necessarily mean every disputed name should become available. WoW Forever is deliberately maintaining a stricter approach to names in some areas, and Blizzard has made clear that certain names are meant to remain unavailable. The key distinction is between intentional restrictions and names that were caught because the filtering logic malfunctioned.

Why reservations need clear communication

Name reservation systems regularly generate pressure because they combine scarcity, identity, and timing. Even in a game where a player can create multiple characters, the first hours of access can determine whether someone gets the name they have used in other games, previous World of Warcraft eras, or community spaces. A reserved name can also carry practical value for streamers, role-players, guild organizers, and players who want consistency across a friend group.

For that reason, a vague "restricted" notice can be more aggravating than a simple "name unavailable" message. If a name is already claimed, the player at least understands the problem. If it is restricted, players may reasonably wonder whether the decision is intentional, whether the term violates a rule, whether it references lore, or whether the system has made a mistake. More detail is not always possible without revealing moderation criteria that people could try to exploit, but acknowledgement and rapid correction go a long way.

The situation is also a reminder that reservation access and actual character creation are related but different stages. Blizzard opened servers after the beta ended specifically so Skyborne pack owners could reserve their names. A malfunction during this window can create concerns that desirable names will be taken while affected players wait for a repair. The speed of the server-side restart was therefore significant, even as reports of remaining issues continued.

Strict naming has already been part of the discussion

The current bug arrives after earlier debate around WoW Forever's name policies during the beta. Players had raised concerns about names being reported, prompting Blizzard to reassure the community that humans were reviewing those reports. That earlier clarification is important context: automated systems may flag, sort, or initially identify potential problems, but enforcement decisions around reported player names are not presented as entirely automatic.

There is a meaningful difference between an automated report pipeline and an automated reservation filter, though both shape the player experience. Human review can account for context after a report is filed. A reservation filter must make an immediate decision in the character creator, usually without a person examining every submission. That makes accuracy especially important, since an overly broad technical rule can stop a player before they ever enter the game.

Blizzard's challenge is to preserve the atmosphere it wants for WoW Forever without creating the impression that ordinary names are arbitrarily off limits. Protecting important Warcraft identities and discouraging disruptive naming behavior are understandable aims for a social MMO. At the same time, players need confidence that a rejected name was blocked for a clear reason rather than because a common substring happened to trigger an unintended restriction.

What players can expect next

Players who encountered the error may want to retry their preferred names now that the server restart and filter adjustments have been implemented. The successful reservation of "Concon Concon" suggests that at least the specific faulty behavior Blizzard identified has changed. Those still receiving restricted-name messages may be dealing with another bug, an unresolved edge case, or a name that is intentionally protected under the game's rules.

For now, the safest conclusion is that WoW Forever's restricted-name list remains active, but one part of its implementation was defective. Blizzard's acknowledgement establishes that names containing certain ordinary combinations were rejected by mistake, not necessarily because those names violated the intended policy. Continued player feedback will likely be important in identifying whether other unexpected matches remain.

The name-reservation stumble is a small but highly visible test for a game seeking to build a more social version of the World of Warcraft experience. Principal game designer Kris Zierhut has discussed a future focused strongly on social play, and character identity is one of the first places where that social experience begins. Before players form groups, join guilds, or build reputations, they need to be able to enter Azeroth under a name they can actually use.