Blizzard is issuing forced name changes to WoW: Forever beta characters that break its naming policy, and some testers have lost their beta access entirely. The announcement comes from developer Fwoibles, who says the worst offenders created names "far outside" the Code of Conduct.
The culprit, at least in part, is the beta's dual names. Two name fields give players more room for creativity, and also more room to combine words into something that would never get past a single-name filter. Blizzard's phrasing is pointed: some players "took this opportunity to reveal too much about themselves" and will not be taking part in the beta any more.
We are in the process of issuing forced name changes to characters found to be in violation of our character naming policies that were created in the Forever Beta. Additionally, we have removed beta access for some users who created names that were far outside of our Code of Conduct. The use of dual names has allowed players new levels of creativity and personalization with your characters, some took this opportunity to reveal too much about themselves and will no longer be participating in this Beta.
The World of Warcraft team takes the safety and inclusiveness of our game very seriously. These actions were performed directly by the World of Warcraft Development team and were individually reviewed. The Customer Service team cannot and will not assist with any appeals. Our system for enforcing naming standards will be coming online very shortly, we would appreciate testers refraining from “testing” this system, as you run the risk of being actioned and losing access to the Beta. Please keep your character names respectful and within policy.
For anyone needing a refresher our code of conduct can be found at: https://us.support.blizzard.com/en/help/article/42673
A few details in the post are worth spelling out.
- The development team did this directly. These were not automated bans. The WoW team says each case was reviewed individually.
- There is no appeal route. Customer Service "cannot and will not" help with appeals. If you lost access over a name, that decision is final as far as the post is concerned.
- An automated system is coming. Blizzard says its tool for enforcing naming standards will come online "very shortly". The post gives no date and no detail on how it will work.
- Do not poke the filter. Blizzard specifically asks testers not to "test" the new system. Doing so risks the same action and losing beta access.
That last point is the practical one. Beta testers are used to stress-testing anything new, and a name filter is an obvious target for curiosity. In this case Blizzard has said plainly that probing the filter counts as breaking the rules, not as helping with the beta. Anyone who wants to report a gap in the filter should leave it at that and not build test names to prove it.
For most players nothing changes. If one of your characters gets a forced rename, you will need to pick a new name that fits the policy. Blizzard does not say which specific names or patterns were flagged, so nobody outside the team knows exactly where the line was drawn. The post links Blizzard's Code of Conduct on its support site for anyone who wants a refresher.
It is also a reminder that the WoW: Forever beta is not a private sandbox. With launch set for 4 November 2026, Blizzard is setting expectations now for how it will treat names on live servers. Dual names stay. The team just wants them used for characters, not for slipping things past the filter.