Overly Restrictive Name Check and Fix Incoming - 28 October

In WoW Forever, we’ve been working on the restricted name list, which is a list the game uses to check for non-profane names that we wish to restrict, such as major Warcraft lore characters or names that are blocked for technical reasons.

Today we’ve determined that we have a bug in the process that caused the game to be overly restrictive with some names. For example, it has been incorrectly restricting names containing “c-o-n”.

With the next realm restarts in each region, we’re going to implement the fix. Afterward, if you previously received a message that said “That name is restricted” for a name that you think should have been allowed, please feel free to try again.

Thank you!

11 Likes

in what regions? do you know that if you select RU language, all rulesets are not available?

12 Likes

Yay! you read my post!

Edit: Ye gods. Don’t look at the US version of this post. I’m just happy this is getting resolved before launch

3 Likes

and when is this realm restart?

4 Likes

Wednesday for EU, so I would assume today

EU Players still can`t create characters having cyrillic names. Blizzard are lazy amaters.

11 Likes

The reset seems to have already happened for the restricted letter combinations.

At least a name can be created with Falcon in it

Yes but not Conflag (short for conflagration) power. Flag power is allowed though.

As if they took your post and copy pasted nickname examples from there
:dracthyr_lulmao:

Also Russian client recived RP-PvP ruleset, but grayed out like the rest and Cyrillic nicnames are not allowed as well. Blizzard scammed like 10-12% of their playerbase with false advertisment, it seems, with providing localized beta for a product that doesn’t work in the region most of these player were playing.

5 Likes

NAME BACON 名叫培根

FILTER SAYS NO 过滤器拒绝

REMOVE CON 删掉禁字

NOW JUST BA 只剩巴

SIXTY PERCENT NERF BEFORE LEVEL ONE 级没到先砍六成

3 Likes

:dracthyr_lulmao:

Oddly specific name restriction.

1 Like

For some reason names including “Shockingly” are restricted

Does anyone know if the EU realms have been restarted so this fix has been applied?

Just checked before. A name that i used during beta, also in retail, still restricted (not taken).

Hello Kaivax,

I am a long-time World of Warcraft player and a purchaser of the full WoW: Forever bundle. I am writing to report a serious issue affecting Russian-speaking players during Early Name Reservation on European servers.

I purchased the full bundle partly to gain early access and reserve my character names ahead of launch. However, the current situation prevents me from using this feature as intended.

I have reproduced the following issues:

1. Russian client — EU Rulesets unavailable

When launching the game with the Russian (ruRU) client and connecting to the European region, all Ruleset options (Normal, PvP and RP) are greyed out and cannot be selected. As a result, I cannot proceed to the server selection stage or reserve character names using my preferred language.

2. English client — Rulesets available, but Cyrillic names rejected

When switching the game client to English, the Rulesets become selectable. I can enter a server and create a character, but the client does not allow me to use Cyrillic characters in character names.

Consequently, neither option allows me to complete Early Name Reservation in the way I need: the Russian client blocks access to the EU Rulesets, while the English client prevents me from using Cyrillic character names.

3. The Russian client worked correctly during the North American beta

I participated in the WoW: Forever beta using the Russian client on North American servers, and everything worked correctly. The current problem appeared when Early Name Reservation became available on European servers.

This strongly suggests that the issue is related to the interaction between the Russian client locale and the European server environment, rather than a general incompatibility with the Russian client.

I have also found reports from other players describing the same or very similar problems on the official European WoW forums.

I understand that this could be a technical bug or a configuration issue. However, without an official explanation, players have no way of knowing whether Russian-language support on European servers is temporarily broken or subject to an intentional restriction.

If this is a technical issue, I urge Blizzard to investigate and resolve it as soon as possible. If it is an intentional restriction, I request a clear explanation of the policy behind it and its implications for Russian-speaking players.

I respectfully request that Blizzard:

  1. Investigate why the Russian client cannot access the European Rulesets during Early Name Reservation.

  2. Clarify whether Cyrillic character names are supported on European WoW: Forever servers and, if so, why they are rejected when using the English client.

  3. Confirm whether Russian-language clients will be fully supported on European servers at launch.

  4. Provide an official status update and, if this is a known issue, an estimated timeframe for a fix.

  5. Address both problems before Early Name Reservation ends on November 3, 2026, so that affected players have a fair opportunity to reserve their intended character names.

This is particularly important because Early Name Reservation is a time-limited feature, and character names are allocated on a first-come, first-served basis. Every day without a solution reduces the opportunity for affected players to secure their preferred names.

I purchased the full bundle in good faith and expected to be able to use the game’s Russian localization. I do not believe players should have to choose between accessing the European servers and using their preferred language and character names.

I would appreciate a substantive response from the WoW: Forever team or the relevant technical team, rather than a generic troubleshooting recommendation.

Thank you for your time and attention. I hope this issue can be clarified and resolved before launch.

Best regards,
A WoW: Forever player

5 Likes

I can’t even hit “Play”, it’s still greyed out :dracthyr_shrug:
“You have pre-installed…” but that’s it…

Edit: Okay…never mind, just restarted the battle.net app, my bad, amateur mistake :dracthyr_hehe_animated:

Can I have my name back?

Neg being restricted as mature language sucks when this has been my ign forever :frowning:

And yet no official word, or apology, for the farce that was name reservation yesterday!

5 Likes

It’s STILL being idiotically restrictive even now! My Character on the BETA was called Malady as was a priest. Malady is simply sickness, illness etc. Well I’m a priest and I cure sickness etc. Absolutely fine on the BETA. How is this suddenly restricted? It’s not a curse or offensive. Someone did say that it’s 'cos it contains the word Lady which is utterly stupid. And is no different to banning any word with the word Con in it! And the proof that it’s Lady thats restricted? Well Malady is restricted. Málady is restricted but…Malády is NOT RESTRICTED. Fix this dumb ai bot system please!!!

2 Likes

I don’t even need to create a name using Cyrillic characters. I’d be happy to create names using the Latin alphabet—it’s a beautiful script. The MAIN thing is being able to play on the Russian client.

Tried to use my old retail name… “Android” - rejected while the name is restricted… Than just for fun I entered the name “Pornwatch” - got also rejected, but because the name was already taken. Absurd.

1 Like