Issues with Character Creation/Deletion on Anniversary Servers

On Anniversary (Classic Fresh) server launch day, I made a couple characters to reserve names for myself and started playing one of them (all my characters follow a naming scheme where they are all 4-5 letter names that are 1-2 letters different) and leveled one to level 12 on the Dreamscythe Normal realm.

After enjoying it, I went ahead and tried to delete some of the other characters as I decided to play the level 12 the whole way through and deleted the wrong one by mistake (the level 12). They’re only one letter off so I must’ve just misread it.

I went to restore the character, and when I hit to restore them I got the error message “You already have an active character with that name. You can’t restore this character at this time.” I took a screenshot of it and opened a support ticket. It also locked me from restoring a character for 24 hours. This is obviously some type of inconsistency/error as I had just deleted the character, and not made any new ones so I wondered if maybe because it was almost an instantaneous restoration it hadn’t updated on the back-end and still thought the character exists.

I don’t expect much from support given the plethora of horror stories I’ve heard and I unfortunately I was not surprised at how awful the responses I got were – despite providing a screenshot showing that my character’s name was not present in Dreamscythe, I got told by three different agents that the character was already present in the realm as a Level 1 (one said Level 0!) and that there was nothing they could do until I deleted the character.

I then remembered yesterday that I did make the same exact character on the Nightslayer PvP server in case I wanted to try that at some point, so when the 24 hour lock on restoration expired I tried again but deleted the level 1 on the PvP server just in case there is some lower-level integrity/state issues between characters (and since people seem to be reporting en masse that their PvP toons are moving to PvE realms randomly so it made me wonder if there was a connection).

Still no dice, “You already have an active character with that name. You can’t restore this character at this time.” I took another screenshot of this and updated my ticket and today I was told that they cannot restore the character due to the name conflict that I have on my account (still not correct) but they went ahead and renamed my character by adding xyz to the end to allow me to restore it.

They then told me to use the paid name change service to change the character’s name after I would restore it. Three problems:

  1. Wow Classic Fresh (as far as I can see) does not have Paid Name Change
  2. The insinuation that I should rectify a problem that is a bug with the product by paying money to fix it, is egregious.
  3. I’m still locked out of playing the character for another 10 hours (we’re at 48 hours now of being locked out) only to unfortunately realize that when I do restore my character it will have a completely wrong name.

At this point I’m at the verge of just throwing out the 6 hours of play time and re-rolling but I’m posting this more as a warning, that there’s something funky with the integrity of character creation in classic fresh right now and I hope whatever the actual issue is gets fixed before it screws out many other players from playing either the characters they want, or on the server they want.

3 Likes

This same thing is happening to me. Thanks for posting about it so I know I’m not alone.

2 Likes

Any updates? I had the same problem but couldnt find a fix

2 Likes

Same issue. I opened a ticket for it. We’ll see.

1 Like

Same issue here on Dreamscythe. I have no other character with the same name on any other server, Classic (any version) or retail. As an added note, I have no addons.

According to Support, this is intended behavior if someone immediately claims the name after deleting your character.

I think that Support are bots that have no actual idea of what’s going on. I don’t know why someone would immediately claim Kruvterothree the millisecond it’s deleted on a non-hardcore server.

I don’t know the situation others are facing, but that was mine.

The first response was absolutely a bot, or a human copy/pasting the support page for this error message, as it just reiterated my problem and then verbatim what that page says.

The next replies were from humans, who, without being able to come out and say it, implied that the guidelines are not as simple as presented, and for characters whose names are immediately taken (as in the case of attempting to force a name change), the character will not be restored. In my case, I was told this was intended behavior and not a bug.