During the World of Warcraft: Forever open beta, Blizzard has for the first time force-renamed offensive characters and revoked beta access from some players; senior producer Tom Ellis confirmed the figure — 0.18% of all created names.

In the World of Warcraft: Forever open beta, Blizzard ran its first mass name cleanup: the studio started force-changing offensive character names and pulled beta access from some players. Senior producer Tom Ellis put a number on it — 0.18% of created names were banned.

What actually happened

• Blizzard sent beta participants messages saying that naming rule violators lose access to the test.
• Force-renamed or kicked from the beta — each case was decided individually, after a manual review by the development team.
• Customer support does not accept appeals — the statement says so directly.

Why now

The trigger was dual names — a personalization mechanic introduced in Forever that lets you give a character two names at once. Some players used it to slip past filters. Blizzard's statement calls the new tool out directly: it brought "new levels of creativity and personalization," and some people "revealed a bit too much about themselves."

What Tom Ellis said

Senior World of Warcraft producer Tom Ellis followed up with a series of posts:

• Only genuinely offensive names were banned. If a character was given a rude or vulgar nickname, the system would have just renamed them — not cut off their beta.
• Every offender's name was run through the same system that would apply in live, and manually checked by humans.
• The name standards haven't changed: they've been the same for all WoW versions over the past 20 years.
• Out of the entire list, the team found only one person who, in their view, was trying to come up with a neutral roleplay name and got caught by the filter by accident.
• The automatic name-checking system isn't working right now ("not launch-ready"), and Blizzard had expected players to behave themselves during the few weeks of beta.

In practice

• If you have a character in the beta with a dual name, double-check there's nothing in it that could read as a slur or a reference to forbidden content. Better rename it before launch.
• If you've already received a forced-name-change notice — nobody's punishing you, just follow the system's recommendation.
• If you've lost beta access — there are no appeals; the decision is final.
• By launch, Blizzard promises to turn on the full name filter, so you won't need to "test" it manually anymore.