Skip to content
everloot

WoW: Forever Name Check Bug: Rejected Names Get a Retry

Blizzard says WoW: Forever's restricted-name check blocked too many names during reservations, including any with "con" in them. A fix ships with each region's next realm restart, so retry names that were rejected.

By Everloot Team1 min readSource: Blizzard forums (US), Blizzard forums (EU)
blue-postforever

TL;DR: Blizzard confirmed a bug made WoW: Forever's restricted-name check far too strict during name reservations. Names containing "con" were blocked, for example. The fix goes in with the next realm restart in each region. After that, try again any name that got the "That name is restricted" message.

What Blizzard said

In the official forum post, Blizzard explains that Forever keeps a restricted list for non-profane names it wants to block, such as major lore characters or names blocked for technical reasons. A bug in that process caught far more than intended:

"For example, it has been incorrectly restricting names containing 'c-o-n'."

Blizzard says the fix ships "with the next realm restarts in each region," and players who were told a fair name was restricted should "feel free to try again." The post doesn't give a restart time. The same notice is on the EU forums.

What to do

  • If a name you've used for years was rejected as restricted, try it again after your region's realms restart.
  • A green check mark only means nobody owns the name yet. Players on the forums report that a name can still be refused as restricted after that check.
  • Your 3 character slots are shared across every ruleset, so pick where each reserved name goes. Our rulesets guide covers the options.

News recap. Everloot has no addon data on names.

Help the DB grow: install the Everloot addon before launch on Nov 4 so your drops count from day one.

Sources

All news