WoW Forever naming rules: forced renames, beta removals and what Blizzard confirmed

A short timeline of the published record #

What happened on September 24? #

Blizzard announced forced character renames and removal of beta access for some severe naming violations. The notice attributes the decisions to individual review by the development team. That establishes Blizzard’s account of the process; it does not let Kingy verify every decision.

Players are disputing consistency and proportionality. A forum post can establish that someone reports an experience. Without the complete notice and case history, it cannot establish why an account action happened, how many players were affected, or a false-positive rate. We have not established that apparently harmless names were the sole reason for any particular removal.

September 25 clarification: what does 0.18% mean? #

Wowhead reproduces a statement attributed to Tom Ellis saying that 0.18% of names led to removal from the beta. That denominator is names, not players or accounts. It cannot establish the percentage of players banned, the number of affected accounts, or a mistaken-decision rate.

The reproduced statement describes further manual review, says some disputed reports omitted another character’s name, and acknowledges one case thought to involve an intended role-play name that overlapped a derogatory term. It also says the dual-name filter was not ready and another review was planned. These are attributed statements, not independently verified case findings or confirmation of a reversed penalty.

The original social post was unavailable when we checked on September 26. Read the Wowhead reproduction for the reported wording; the September 24 Blizzard forum notice remains the direct source for the announced actions and appeal limitation.

Five outcomes that should not be called the same thing #

This is Kingy’s reading checklist, not a list of guaranteed client error messages.

Read both parts together #

Forever’s complete first-and-second-name pair must be unique within a region. A first name or family name may recur when the complete pair differs. It is not a traditional per-realm name search.

Blizzard says the combined meaning matters, including restricted wording split between fields. Its Forever article discusses confusing names, impersonation and repeated-character patterns, but does not publish a complete word list, numeric component limits or supported alphabet specification. Generic WoW name limits are not a verified specification for this two-field system.

Policy concerns and role-play style are separate #

Blizzard’s conduct rules apply to names and cover hate, discrimination, obscenity, threats, harassment and disruptive language. The context and full name matter. A short local rule list cannot reproduce that judgment across languages or predict enforcement.

The general role-playing guidance also discusses disruptive real-world references and phrases. A fantasy-style suggestion is an editorial preference, not a finding that another name breaks Forever’s rules. Ordinary names, accents and innocent substrings should not be treated as proof of offense.

Read a proposed pair aloud, consider its combined meaning, and avoid impersonating staff or another person. Changing letters to conceal a prohibited meaning does not resolve the underlying concern.

If you receive a notice #

1. Read the exact action, affected service and any duration in your notice. Keep a private copy with its date.
2. Follow the instructions attached to that action. Do not post account details, private support correspondence or another player’s identity to crowdsource a verdict.
3. For the September 24 beta actions, Blizzard explicitly says Customer Service will not handle appeals. A generic appeal article does not override that specific statement, and Kingy cannot offer an appeal service.
4. If a rename is offered, choose a new pair after reviewing the current policy. Do not repeatedly submit provocative variations to test the boundary.

Our view: explain decisions clearly #

Players should be able to understand what rule they broke and what consequence follows. We would like Blizzard to publish anonymized examples, distinguish a rejected input from an account penalty, and explain how potentially mistaken decisions are reviewed. Those are editorial recommendations, not existing promises from Blizzard.

Enforcement can protect players from abuse while still deserving scrutiny over consistency and proportionality. The useful debate is about the published rules and decision process. Naming individual players or organizing mass reports does not establish the facts of a case.

What the public record still does not answer #

We will revise this guide when a source answers these questions. Their absence does not prove either that all actions were correct or that all disputed actions were mistaken.

• An independently verified total of affected accounts or rate of mistaken decisions. The reported percentage of names does not answer either question.
• The complete notice and circumstances behind each disputed player report.
• The full Forever validator specification and definitive prohibited-name list.
• How launch enforcement and review will differ from this specific beta process.

What our Name Workshop can tell you #

The workshop offers curated ideas, editable two-part pairs, local shortlists and limited advisory checks. It separates technical questions, policy concerns, role-play style and availability. An unflagged result is not Blizzard approval; a flagged concern is not a ban prediction.

Our September 25 review of Blizzard’s public developer documentation did not verify a supported Forever name-availability endpoint. A missing character profile cannot prove that a name is available. Confirm availability through the official client or reservation flow when applicable.

Common questions

KEEP GOING

Your next step.