WoW Forever coverage. Sources and dates identify the announcement and its game context.
Which rejection does this address?
Kaivax has acknowledged an overly restrictive in official WoW Forever before launch. The example in the announcement is a name containing the sequence c-o-n. Those hyphens identify the example; adding punctuation is not the proposed fix.
The relevant English message is “”. A different message deserves a separate check. This announcement does not diagnose every problem encountered while choosing a name.
The comes before the retry
Blizzard plans to apply the correction with the next in each region. Afterward, players who received that rejection for a name they believe should be allowed are invited to try again. The post supplies no times and does not confirm that every region has already received the fix.
Keep the spelling you actually wanted. Repeatedly changing letters before the makes it harder to tell whether the original false rejection has gone away.
Make one useful comparison
Save the rejected spelling and the message, then compare them with the next attempt after your region’s . If the message changes, record the new one instead of treating every refusal as the same bug. Keep a second choice too: fixing an excessive does not promise that a particular name will be accepted.
Some restrictions remain intentional. Blizzard mentions major Warcraft story characters and technical reasons, including names without profanity. A clean-sounding name alone is not proof of eligibility.
Sources
- Overly Restrictive Name Check and Fix Incoming - October 27us.forums.blizzard.com
