World of Warcraft Forever Fixes Overly Strict Character Name Filter

Character names are one of the first choices players make in a new MMORPG, so a reservation tool needs to be dependable. Blizzard’s early name reservations for World of Warcraft Forever have instead produced server trouble and blocked names that should have passed. Community Manager Randy “Kaivax” Jordan says a bug made the restricted name check too strict, and Blizzard is rolling out a fix during realm restarts in each region.

Why valid names were rejected

The filter checks more than profanity and slurs. Jordan says Blizzard also blocks major characters from Warcraft lore and certain names for technical reasons. That screening has to account for a change from the game’s familiar single name format: Forever uses two names. A broader set of checks may be needed for that format, but this bug caught some combinations that weren’t intended to be restricted.

Jordan confirmed that names containing the three letter string “con” were among those blocked. Players also reported problems with “nom” and “duc.” The article suggests those strings may have been caught because they have meanings in other languages: “nom” means “name” in French, while “duc” means “duke.” The issue is with the filter matching pieces of names too broadly, rather than with those character names themselves.

That kind of false positive can make a naming tool feel unpredictable. A player might try a harmless combination and see it rejected without a clear explanation of which part triggered the restriction. Here, the examples show how a short string can appear inside ordinary names, leaving players unsure whether a name is truly unavailable or whether the check has misfired.

Players can try again after the fix

Blizzard is applying the change as realms restart across regions. Jordan encourages anyone whose name was marked as restricted by mistake to submit it again. Players hoping to use names such as “bacon” or “ducky” should have another chance once their realm has restarted and the updated check is in place.

The timing matters because reservations opened ahead of launch to help players claim preferred names early. The feature is available to people who have already pre-ordered a paid edition of the game, so a rough first run affects players who have committed to joining at release. The system also faced an initial server problem that forced Blizzard to take it offline temporarily. Together, the technical interruption and the overzealous filter have made an early convenience harder to use than intended.

For an established MMORPG, name restrictions have to balance several goals: keeping offensive names out, protecting recognizable lore characters, and allowing players room to create identities of their own. The two name format adds another consideration, since checks may need to examine combinations as well as individual terms. Blizzard’s explanation points to a flaw in how those checks were applied, and the announced fix gives players a practical next step: retry names that were rejected once their realm has restarted.

The issue also highlights how much weight players put on a character’s name. It can become part of how friends recognize someone across sessions, and a reservation window is meant to let players settle that choice before launch pressure sets in. A filter that rejects commonplace strings can undermine that confidence, even when the underlying goal of restricting certain names makes sense.

Some players may still find the overall restrictions more limiting than they’d like. The original report points to Final Fantasy 14, where players can encounter names such as “Lockheart,” “Rosfield,” and “Estinien.” That comparison reflects the writer’s view that familiar names from other games don’t automatically make a character name feel unsuitable. Blizzard’s stated restrictions include Warcraft lore characters and technical cases, but the source doesn’t detail every category or how the revised check will handle borderline examples.

World of Warcraft Forever launches Wednesday, November 4. With regional restarts rolling out the filter fix ahead of launch, players who hit a false rejection can try their preferred name again and see whether it’s available.