Blizzard is taking World of Warcraft: Forever beta names more seriously than a forced rename. Players who put policy-breaking first-and-last-name combos on a character can lose the beta entirely. The warning landed on the official forums after a tester said they were locked out with no explanation and no email. Support representative Vrakthris answered that an email did go out, that it named the character, and that junk folders are worth checking.
"Character names must adhere to our naming policies, including in Beta," the reply said. "If you violate those policies that may result in the removal of beta access." That is a harder penalty than the live-game habit that most players are used to of a GM pass and a free name change. Beta keys for Forever are limited. The test opened Thursday, September 17, runs through October 21, and sits behind the Skyborne Epic Pack or the Warcraft Forever Collection. Get kicked and you are out of the only public build until launch on November 4.
The new naming system is why this blew up so fast. Forever is realmless. Names have to be unique across a whole region, not a single old-school realm, so every character now gets two fields: a main name and a secondary name, read as a first and last. Blizzard's own example was "Ana Forever." Two players can share a first name. They cannot share the full pair. A settings toggle can hide the second part on nameplates.
The extra field was sold as breathing room in a bigger pool. It also gave people a new way to smuggle jokes the old filter used to catch in one box. Screenshots started circulating as soon as the beta went live. Some were dumb bathroom humor. Some split a banned word across the two fields and hoped the client would treat each half as clean.
Blizzard already said that trick does not work on paper. An official naming post notes that the system can evaluate both parts together, so breaking a restricted word in half does not automatically make it valid. Impersonating Blizzard staff, using confusing spellings, and the rest of the existing code of conduct still apply.
A player on the same forum thread argued the beta exists to stress-test systems, so crude names should be treated as filter feedback instead of a ban. Vrakthris shut that down.
"It isn't a matter of 'tuning', we know what bad names are and we know people create characters with them all the time," the post said. "We have a reporting option specifically to have those addressed. Some slip through the cracks here and there because they go unreported."
The first-and-last option "provides opportunities for a lot of… creativity, but our policies are still in place." Names still have to follow the rules. The Forever development team is handling reports that reach them. QA and game development run most beta enforcement. Appeals exist if someone thinks the hit was a mistake. Vrakthris added that none of the examples they had seen looked appropriate, and that the final call is not theirs.
It's no surprise the report tool is doing the first pass. WoW has used player reports for dirty names for twenty years. The difference here is the punishment attached to a successful report during a paid, time-boxed test.
Early name reservation for pack buyers opens October 27 and runs through November 3. Eligible accounts can lock in up to three characters, first come, first served, on the account that bought the upgrade. Desired names are not guaranteed. If the full pair is taken or fails the filter, you pick another combination or roll the random generator. That window is the last clean shot at a name before the November 4 stampede.
Live Forever will still use the two-part structure. Blizzard has not said every live offense will cost the whole product the way a beta key can vanish. The forum post is about the test. The policy line itself is not new. The two-box character creator just made the violations louder and easier to screenshot.
Are you rolling a serious first-and-last name for launch week, or are you waiting to see how hard Blizzard polices the filter after November 4? Let us know your thoughts in the comments below.