If the game answered “name restricted” during the reservation, the problem may have come from the game itself. On Wednesday, October 28, 2026, at 2:28 a.m. Paris time, community manager Kaivax acknowledged on the official Blizzard forum a bug in the list of restricted WoW Forever names. Example given: names containing the letters “c-o-n” were wrongly refused.
What Blizzard admits, and what it leaves out
Kaivax’s message separates two mechanisms. The profanity filter is not at fault. The culprit is a second list, the one of non-vulgar names Blizzard still wants to block, such as major characters of the Warcraft universe or names set aside for technical reasons. Blizzard writes that the game was “overly restrictive with some names” and that the bug hit “c-o-n”.
The fix will arrive “with the next realm restarts in each region”. No time is given. On Wednesday around 3 p.m. Paris time, the thread holds more than 400 messages, and the only Blizzard message is the first one: no employee confirms there that the fix is live. Until that is written, treat it as announced, not applied.
Why “con” hits so many WoW Forever names in French
In French, “con” opens a lot of first names and words: Conan, Constance, Condor, Conquérant. A name built around that syllable is nothing exotic, and having just one of them refused is enough to cost a player a quarter of an hour without understanding what they are accused of. Nothing indicates the filter targeted French, though: Blizzard talks about a processing defect, not a language. The Output Lag site, which picked up the announcement on the evening of October 27, describes the likely mechanism: somewhere in the processing of the list, strings of letters started matching where they should not, in the middle of harmless names.
Players report other refusals: “Connie”, “nom” and names containing “gm”, such as “frogmage”. These are testimonies from the forum and social networks, which Blizzard has not confirmed. Some also say that truly offensive names got through. Nothing says accented characters are a problem, however: the question is documented nowhere, and I prefer not to guess.
Restricted or taken: the difference that decides what to do
The practical rule fits in two error messages. If the game says the name is restricted (“That name is restricted”), you can try again after the next realm restart in your region. Blizzard writes it plainly: try again if you think the name should have passed. If the game says the name is taken, nobody will give it back to you: another player has already reserved it.
The reservation window, opened on October 27 at 6 p.m. Paris time, runs until November 3, at three names per account. Launch is on November 4. There is some room, but not for long on common names: the longer you wait after the fix, the more likely a coveted name has been taken in the meantime. Since names are reserved per region, including from one ruleset to another, a taken name stays taken everywhere in that region. Our article on the choice of ruleset details this constraint.
A reservation piling up setbacks
This bug comes on top of an already bumpy opening: we covered the reservation delay from 6 p.m., after presenting the window in Three names, one window. Kaivax had also flagged on October 27 a defect specific to Oceania: players connected to Australian servers must create their roleplay or roleplay PvP characters before their Normal or PvP characters, otherwise the former disappear from the choices. Blizzard promises an “urgent” fix there too.
Reactions on the forum show another irritation. According to Output Lag, Kaivax’s message drew 200 replies in 90 minutes, and many are not about the filter. Players who had bought early access complain that they could not get in when the window opened, or that someone beat them to a name they have carried for years. Blizzard has not answered on that point, and “first come, first served” remains the stated rule.
What we do not know yet: the exact restart time in each region, and whether Blizzard will extend the window for those who lost time. No announcement to that effect at this hour. If one of your WoW Forever names containing “con” was refused, note it down, and try it again as soon as your region has restarted.
0 Commentaires
Aucun commentaire pour le moment. Soyez le premier à commenter !