WoW Forever Beta Bans Players for Offensive Names and Blizzard Says There Is No New Policy

By Indie Kings | September 26, 2026

Updated September 26, 2026: Blizzard sent a wave of beta bans in World of Warcraft: Forever over offensive character names, and senior game producer Tom Ellis says there is no new policy. The cause was a naming filter that was not ready for dual-character names, which forced Blizzard to review every name by hand for the first weeks of the beta.

Source note: Ellis's remarks come from his account on X, as reported by PC Gamer on September 25, 2026. GamesRadar covered the same story separately. We have not seen the original posts, so the quotes here are PC Gamer's transcription.

World of Warcraft Forever beta character names

Image: World of Warcraft: Forever beta. Credit: Tyler C. / Blizzard Entertainment via PC Gamer.

What happened in the beta

Players who created characters with names containing racist or otherwise inappropriate terms in the World of Warcraft: Forever beta had access revoked in a wave of bans that went out alongside the beta's first major patch, which PC Gamer reports as Wednesday September 24.

The bans did two things at once. They revoked access for the worst names, and they forced characters with borderline names to be renamed. The second group is where the controversy came from, because a player who was told to change a name reasonably reads that as a warning rather than a punishment.

The cause was a filter that was not ready

The root cause is the interesting part, and it was not a policy decision. According to senior game producer Tom Ellis, speaking on X, the naming filter was not finished when the beta opened.

Our naming filter wasn't ready to rock for dual names but we naively thought after twenty years folks knew what was and wasn't OK and we'd be fine for a few weeks of beta till it came online.

Two admissions sit inside that. The filter specifically was not ready for dual names, which suggests the gap was in handling two-word combinations rather than in detecting the underlying words. And Blizzard expected players to self-regulate for a few weeks on the basis that twenty years of World of Warcraft had made the boundaries obvious.

PC Gamer's reporter, who played through the beta week, found the opposite. Their observation was that World of Warcraft usually has a pretty strict filter covering a lot of racist or disgusting names and all their permutations, but in the beta they saw more than usual that should have been blocked at the character creation screen.

Why Blizzard was reviewing names by hand

Because the automated filter was not live, Blizzard ran every name manually through its own filter and then double-checked the results, per Ellis.

That is an expensive way to run a live game, and it explains the delay between the problem starting and the enforcement arriving. The process Ellis describes, where staff spent an evening re-reading everything and checking posts, is what a manual queue looks like when it has to be worked through after the fact rather than as names are created.

The pushback, and Ellis's answer

The bans produced complaints on social media and Reddit from players who said they had been punished unfairly. Ellis addressed that directly.

A couple of us spent the evening reading through everything again and checked every Reddit post and Twitter and so far every one of them who's posted their three cheeky or just inappropriate names has had a 4th character they have accidentally omitted.

That is a specific and checkable claim. Anyone who posted complaining about three characters was reported to have a fourth character they had not mentioned. It is also the kind of statement that invites exactly the argument it is trying to settle, since it rests on the absence of public reports rather than on anything the complaining players can check.

There is no new policy

The part that should settle most of the disagreement is also the simplest. Ellis says there is no new policy for World of Warcraft: Forever.

His framing is that any name of the type in question would not have been allowed in any variation of World of Warcraft at any point in the game's history, and would have earned a suspension. So this is not Forever being stricter than Classic, or the beta having rules that do not apply elsewhere. It is an existing standard being enforced late.

Claim	Source
The naming filter was not ready for dual names	Tom Ellis, senior game producer, on X, via PC Gamer
Every name was reviewed manually and double-checked	Tom Ellis, via PC Gamer
Bans shipped with the beta's first major patch on September 24	PC Gamer
There is no new name policy for Forever	Tom Ellis, via PC Gamer
Such names would have earned a suspension in any version of WoW	Tom Ellis, via PC Gamer

What this means for your beta characters

If you are in the beta right now, the practical advice is narrow. If you have a character whose name is borderline, rename it before the filter goes live rather than after, because the manual phase is described as temporary and the automated filter is the permanent state.

Two things are genuinely unknown. Nobody has stated when the filter will go live, and the enforcement has so far come through manual review rather than through the system that will eventually do it automatically. The second unknown is how dual names specifically will be handled once live, since that is the stated gap. If the gap was in two-word combinations, then a name that is unremarkable word by word may be treated differently once the gap is closed.

Our beta playbook covers the practical side of testing, including server basics and the current level cap.

FAQ

Why were players banned from the WoW Forever beta?
For character names containing offensive terms. Senior game producer Tom Ellis says the naming filter was not ready for dual names when the beta opened, so Blizzard reviewed every name manually and enforced in a wave that shipped with the first major patch on September 24, 2026.

Is there a new name policy in World of Warcraft: Forever?
No. Ellis says there is no new policy, and that names of this kind would not have been allowed in any version of World of Warcraft and would have earned a suspension.

What was the actual bug with the name filter?
It was not ready for dual names, meaning the gap was in handling two-word name combinations rather than in detecting the underlying terms.

Were only offensive names banned, or also borderline ones?
Both, in effect. The wave revoked access for the worst names and forced players with iffy names to change them, which is where the complaints about wrongful punishment came from.

Why did enforcement take so long?
Because the automated filter was not live. Blizzard ran every name through its filter manually and double-checked the results, which Ellis described as staff spending an evening re-reading everything and checking Reddit and Twitter posts.

Will my dual-name character be safe once the filter goes live?
Unknown. Dual names were the stated gap, so how they are handled once the filter is active has not been specified. Blizzard has not said when the filter goes live.

Bottom Line

This is a failure of preparation rather than a policy change, and Blizzard has been unusually direct about which. The filter was unfinished for dual names, the team expected twenty years of player self-regulation to cover the gap, and it did not, so the gap was filled by hand. That is why enforcement arrived as a ban wave rather than a creation-time block, and it is why the delay makes the process look arbitrary to the players caught by it. The substantive point for anyone still in the beta is that the standard did not move, only the enforcement did, and it will be automated once the filter is live. The honest gaps are the date the filter goes live and how dual names specifically will be treated, which is precisely the case the current system mishandled.

Source: PC Gamer, World of Warcraft: Forever dev has no sympathy for players kicked from the beta for offensive names, by Tyler Colp, September 25, 2026, reporting statements by senior game producer Tom Ellis