WoW Forever beta testers are losing access over character names, and Blizzard says the surname is no loophole

WoW Forever lets you give a character a first name and a last name, and it took the beta very little time to find out what some players would do with two fields instead of one. Names that are harmless on their own turn into something else once they are put together, and the beta forums filled up with threads from people who logged in to find their access gone.

What Blizzard said

The clearest answer came from Vrakthris of Blizzard Customer Support on September 19, in a thread from a tester who had been suspended “without any reason given”. The key points from that reply:

• The rules do not change for the beta. Character names have to follow Blizzard’s naming policy there too, and breaking it can mean losing beta access.
• You should get an email that names the character. The rep could see a message sent to that tester with the offending name in it, and suggested checking the spam or junk folder before assuming no reason was given.
• It is not a tuning problem. A tester argued that a new naming scheme needs real-world stress testing, so why punish the people doing it? The answer was that Blizzard already knows what counts as a bad name, and names that slip through are the ones nobody reported.
• QA and the development team run the beta, so enforcement there sits with them rather than with the live game’s usual process. If you think the call was wrong, the advice is to submit an appeal.

The rep added that none of the examples they had seen looked appropriate, while making clear the final decision was not theirs.

Why the beta is harsher than live

On the live game, a reported name has usually meant a forced rename before anything else, which is why a beta that simply removes access feels like a step up to many testers. VICE picked up the story on September 21 and framed it the same way: on Forever’s beta, a rude name can cost you the beta, not just the name.

Forum MVPs, who are volunteers and do not speak for Blizzard, filled in some of the reasoning. Blizzard judges a name by what most players would read into it, not by what its owner says they meant, so a first name that is fine on its own can get flagged once a surname turns it into something else. One EU MVP also noted that suspensions have recently been added next to forced renames on retail, because some players picked edgy names on purpose knowing a rename was the worst that would happen.

How players reacted

The community is split in a familiar way. A US thread titled Time to start bans on last names passed 170 replies with proposals such as taking custom names away from anyone who gets a forced rename and leaving them with the random name generator. An EU thread asking how Blizzard should punish name abuse passed 150 replies, and several newer Banned from Beta threads mix appeals with people pointing out that beta access is a privilege, not a purchase right.

The other side argues that a stress test is exactly where a new system should be pushed, and that losing access to a paid-for beta over a name is a heavy penalty. Blizzard’s answer, so far, is that the policy is the same one players already agreed to.

What this means for you

If you want to keep testing until launch on November 4, treat the surname as part of the name: read the full name out loud before you confirm it. If your access disappears, check your spam folder for Blizzard’s email first, then appeal through support if you think the name was fine.

More on the beta: the WoW Forever beta tracker, the WoW Forever FAQ, and our earlier look at how testers reacted to surnames on day two of the beta.