Blizzard Support addressed that situation on 30 October. The explanation separates mistaken restrictions from names that passed before all the checks were in place.
Earlier acceptance isn’t a guarantee
On 30 October, a player reported that recreating a previously accepted name produced a mature-language rejection. Blizzard Support’s Vrakthris explained that some naming systems weren’t in place when reservations opened. Some names got through that shouldn’t have; others were mistakenly blocked. Blizzard was still adjusting the system.
This explanation isn't a diagnosis of every rejected name. It doesn't establish the reason for a rejection on your own account.
What about the restricted-name fix?
The 27 October fix announcement addressed an overly restrictive check, including names containing “con”. Kaivax said the fix would arrive with each region’s next realm restart, after which affected players could try again.
That announcement did not remove the naming rules or promise that every previously accepted name would work. It also isn’t evidence that a later mature-language rejection has the same cause.
What to check before trying again
- Check the full combination. Blizzard’s naming guidance says both parts can be assessed together. Splitting a restricted word between them doesn’t necessarily make it valid.
- Distinguish availability from eligibility. The complete two-part name must be unique within your region, and it must meet the naming requirements. A different second name may distinguish an otherwise valid first name; it isn’t a way around restrictions.
- Keep an alternative ready. Blizzard doesn’t guarantee desired names. If yours is taken or ineligible, choose another combination or use the name generator.
My practical caution: don’t delete an existing character on the assumption that you can recreate its name. You can report a suspected bug, but a report isn’t a promise of approval or recovery.