#0 - Sept. 25, 2010, 7:02 p.m.
My two posts:
Q u o t e:
Hi, I went to pay for a character name change about 8 hours ago on my 73 warlock and I got through to the final step, where you enter your credit card information, only after that step I was greeted by a page that said error. I went to re-start the process, only I saw that the character in-question was now ineligible for a paid name change until a month from today's date, however, the character also has the new name I was going to change it to on the list of my characters for that realm where it says ineligible. The bigger problem is, every-time I try and log into that character, the loading screen comes up and the bar gets to full, then I'm brought back to the character select screen, with a message saying: "You cannot log in until the character update process you recently initiated is complete." After I get this message, if I try to log-in to any other character or the warlock again, I am disconnected and I have to log-in again and if I want to get into the game on another character, I can do so only if I haven't tried to log-in to the warlock r and be greeted with that message. It has been like this for 8 hours, I assume it'll stay like this for the next month unless I'm able to get this fixed. Also, the character name I intended to switch it to is now unavailable on the server, making me believe that some part of the paid name service process is in effect still.
Character whose name I was trying to change is Poosy, level 73 warlock of Skullcrusher. :). Thanks.
Q u o t e:
Its now been over 24 hours and I'm still getting the same error and cannot log-in. The character has the same name (Poosy) as prior to the paid name change process in my character select screen, yet can be seen on the armory under the new name: http://www.wowarmory.com/character-sheet.xml?r=Skullcrusher&cn=Brettk Also, I failed to mention this earlier, but I was receiving some kind of error about not being able to log-in while logged into the mobile armory yesterday before the current error message became the only once I've seen since.
Thanks.
