WoW Forever Name Reservation Bug Fixed After Ordinary Names Were Restricted

World of Warcraft Forever’s name-reservation launch ran into a very particular kind of MMO problem: players could reach character creation, type in a name, and be told it was restricted even when the name did not appear to be offensive or a protected Warcraft identity. Blizzard has identified the issue as a bug in the restricted-name filter and said a fix was deployed with a server restart. The explanation matters because the affected names were not limited to obvious attempts to claim a famous lore character. At least one faulty rule was broad enough to reject names containing the letter sequence “con.”

The reservations became available after the Forever beta ended, with access tied to purchasers of a Skyborne pack. For players who have carried a character name through other games, guilds, friend groups, or role-playing communities, that early reservation window is more than cosmetic. A character name is often the first persistent piece of an online identity. That is why a failed reservation system can generate a disproportionate amount of frustration even when the underlying problem is “only” a filter bug.

What went wrong with the restricted-name list

Blizzard uses a restricted-name list in addition to profanity checks. In this case, the list is intended to prevent use of names the game wants to hold back, including major Warcraft lore characters and names blocked for technical reasons. A restricted-name list is not necessarily a bad-word list: it is a policy and technical safeguard designed to stop players from presenting themselves as an established character or colliding with a protected system term.

The failure was in how that list was being applied. A community manager said the process had become overly restrictive and gave “c-o-n” as an example of a sequence being incorrectly blocked. That is an unusually clear signal of a substring-matching issue. A substring is simply a run of characters inside a longer word. If an automated rule treats a short sequence as disallowed without sufficient context, it can sweep up a huge number of harmless names.

For more context, explore JBL Vibe Beam Earbuds Are Listed at $30, With 32 Hours of Claimed Total Battery Life.

That distinction is important. Blocking the exact name of a prominent Warcraft figure is a deliberate moderation choice. Blocking any candidate name that happens to contain a three-letter sequence is a technical error with far wider consequences. The latter can reject names that share no intended meaning with a protected character, a prohibited phrase, or a technical term.

Blizzard said the correction should have arrived with the server restart. There were still player reports of reservation trouble after that point, so the practical state of every individual name was not immediately clear. However, the cited “con” problem appeared to be addressed: the test name “Concon Concon” could be reserved after the change.

Why players also questioned NPC-name restrictions

Replies to Blizzard’s explanation suggest the concern was not confined to the “con” example. One player said names containing “nurse” had been restricted and supplied a list of 23 attempted names containing that word. Their objection was straightforward: generic titles such as Nurse or Officer do not intuitively read as the sort of major lore identities that need strict protection.

That does not, by itself, establish the precise rule behind every rejected “nurse” name. A name can be denied for more than one reason, and the available information does not confirm whether each of those attempted names stemmed from the same defect. Still, the reports illustrate why players found the system difficult to interpret. A character creator that only returns “restricted” gives no useful indication of whether the issue is profanity, a lore-name policy, a technical reservation, a duplicate name, or a temporary filtering error.

For a player, those categories lead to very different next steps. A profanity restriction means the name needs replacing. A duplicate usually means trying a variation. A technical issue may be resolved by waiting for a fix. A lore restriction may be permanent, even if the player feels the name is generic. When a single message covers all of those outcomes, it may protect the integrity of the system, but it also leaves people guessing.

Strict names versus broken rules

It is worth separating two related points. WoW Forever has been strict about character names, and that strictness is not automatically evidence of a malfunction. During the beta, concerns arose around reported names, after which Blizzard reassured players that reports were reviewed by humans. Human review is significant because it means the final handling of a report is not meant to rest entirely on a player-triggered automated action.

The reservation bug is a different layer of the process. Before anyone reports a name, an automated filter can decide whether that name is even eligible to be created or reserved. Automation is useful at that scale: it can immediately screen obvious profanity, impersonation attempts, and system-conflicting strings. But its weakness is context. Software can recognize a sequence of letters; it is less reliable at judging whether that sequence has a meaningful relationship to the policy it is meant to enforce.

That is the central lesson of the incident. Strong naming rules and reliable naming tools are compatible goals, but they require careful boundaries. A game can reserve major character names while permitting ordinary words that happen to overlap with a small fragment of a protected name. It can also retain human review for reported names while ensuring the initial automated gate does not behave as though every partial match is a violation.

What Skyborne pack owners can do now

Players who were rejected during the reservation period have a sensible first option: try the preferred name again now that the server-restart fix has been applied. The verified result for a name containing the previously cited “con” sequence indicates that at least part of the overly broad behavior has changed.

If a name continues to receive a restricted message, it is useful to distinguish that outcome from a claim that the name is definitely unavailable for the same bug-related reason. The game’s message may still reflect a valid restricted-list entry, another naming policy, or a remaining issue. Players can make the situation easier to document by keeping the exact spelling used, including spaces or punctuation if applicable, and noting whether a simpler variation produces the same message.

Retry the exact intended name after the server restart rather than assuming the original rejection remains final.
Check a small number of variations to see whether a particular word or character sequence appears to trigger the restriction.
Do not assume a generic-sounding term is guaranteed to be permitted; the game can maintain legitimate reservations beyond famous character names.
Conversely, do not assume a restriction necessarily reflects misconduct or profanity. Blizzard has confirmed an overly restrictive filter bug occurred.

Players should be cautious about abandoning a preferred identity too quickly, particularly during a name-reservation period where timing matters. At the same time, repeated guesses are not a substitute for a clearer status explanation when a valid-sounding name remains blocked. The remaining reports following the restart show why continued attention to edge cases is important.

WoW Forever’s team has described an ambition to make the MMO even more social. In that context, names are part of the game’s social infrastructure, not a minor text field. They are how party members recognize one another, how guildmates build continuity, and how a player establishes a public identity before a character has earned gear, achievements, or reputation.

That makes the quality of the reservation experience consequential. A strict filter can serve the social game by limiting impersonation and discouraging names that undermine the intended environment. A filter that catches ordinary names by accident creates the opposite effect: it makes an entry point to the community feel arbitrary.

Blizzard’s acknowledgment of the bug and deployment of a fix are the key developments. The open question is narrower now: whether the corrected rules consistently distinguish names that truly belong on the restricted list from innocuous names caught by accidental matching. For players with a rejected reservation, the immediate evidence says it is worth trying again. For the game, the episode is a reminder that the best moderation systems are not merely strict; they are specific enough to enforce the rule that was actually intended.