WoW Forever beta bans hit offensive surnames

The WoW Forever beta lost a chunk of its testers this week over the names they gave their characters. Blizzard pushed through forced renames and pulled access outright from the accounts that went furthest. Senior producer Tom Ellis then answered the complaints in public, in terms that travelled across the forums within hours. Underneath the row sits the surname system, the one genuinely new thing this release brings to World of Warcraft.

At a glance

Blizzard revoked WoW Forever beta access over character names that breached the code of conduct.

Senior producer Tom Ellis says he read the full list of removed names and offers no leniency.

The automatic filter was not live for dual names, the release’s headline feature.


Tom Ellis answers the players who lost access

The tone caught part of the community off guard. Tom Ellis, senior producer on World of Warcraft, wrote on his X account that “multiple unfortunate humans read through every name that was removed from beta today”, then added: “I read the list. No sympathy. Be a better human next time.” GamesRadar gathered the exchange and the detail of the penalties.

To anyone claiming honest confusion, the producer had a straight answer ready: “if you’re genuinely confused, remember that it’s our database, we can see every character you’ve created”. The team holds the full creation history behind an account, which is how a one-off slip gets told apart from a pattern.

Blizzard is hardly alone in going public with this sort of enforcement, as Riot Games showed when it banned close to three hundred thousand accounts in one sweep. Two tiers of penalty went out: a forced rename, standard practice on the game for years, and the heavier removal of beta access, kept for names judged well outside the code of conduct.

Demand explains part of what happened. GamesRadar reported that the opening struggled under the load, quoting the team on the number of people “hammering at the door of the Beta”. A crowd that size arriving at once is precisely the condition under which a half-ready filter shows its limits. Blizzard moved fast and said so out loud, which is unusual enough from a producer talking about moderation.

WoW Forever revisited Felwood zone from the new World of Warcraft release
A zone reworked for this release. Official Blizzard Entertainment artwork

The WoW Forever naming filter was caught out by dual names

The technical account comes from the producer himself. Tom Ellis wrote that “our naming filter wasn’t ready to rock for dual names”, adding that the team assumed twenty years in, players understood where the line sat, and that a few weeks of beta would pass fine before the filter came online.

That detail matters, because the dual name is the headline addition. WoW Forever lets a character carry a first name and a surname, where World of Warcraft has run on a single word since launch. The number of possible names explodes as a result, and a filter tuned to check one word gets much harder to set up across two.

The obvious way around it follows from that: two harmless halves can spell out something offensive once joined together, and a system checking each field on its own waves them straight through. Moderation therefore fell to people reading line by line until the filter went live, which is what the remark about “unfortunate humans” working through the list describes.

A name also carries more weight in an MMO than in most other games. It works as public identity for years, sits above the character for everyone sharing a zone, and follows its owner through guilds and ladders alike. A cosmetic-looking feature has opened a real moderation job for Blizzard.

WoW Forever character claiming a new power in the World of Warcraft universe
New powers as shown on the official page. Official Blizzard Entertainment artwork

Five weeks from launch, what this episode signals

The calendar makes this touchier than it first appears. The official WoW Forever page sets launch for 4 November, which leaves little room to finish a filter capable of absorbing millions of character creations inside a few days. Opening day concentrates the worst of it: players rush the pool of available names, and the hunt for something rare pushes people towards borderline choices.

For testers still in, the practical takeaway fits in a sentence: the existing naming rules cover both halves of the name. An acceptable first name paired with a problem surname is still actionable, and account history weighs in whenever a moderator rules on a borderline case.

If you get renamed by force, the process is the familiar one. The character keeps its progress and its gear, and the game asks for a new name at the next login. What gets lost is the chosen identity, sometimes carried for years on an earlier version, which accounts for a fair share of the irritation on the forums.

None of this is new ground for Blizzard, mind you. World of Warcraft naming policy has long ruled out slurs, hateful content, impersonation and explicit sexual references, and forced renames have sat in the moderation toolkit for years. The real test lands on launch day, when the filter is running and the quality of the calibration shows inside the first few hours.


Upcoming dates, releases, DLC and major updates, are all in our calendar.