Just a follow up. Support emailed me that they generic'd my costume, but I still crashed. They asked if it was OK to log into my account to check things themselves and I said sure. Then they emailed to say that they accidentally generic'd the wrong character, specifically the one that I logged the /petition from. When they generic'd the character that was crashing, I could log her in again.
So the quick solution is to /petition to have your broken character's costume generic'd. The better solution is to have NCSoft put some checks in place so that this doesn't happen. Maybe explicitly catch broken costumes in the client and report them as such, maybe establish a rule that costumes cannot be made invalid, or establish a procedure for genericing costumes during maintenance when they become invalid.
Goodbye and thanks for all the fish.
I've moved on to Diablo 3, TopDoc-1304
Just a follow up. Support emailed me that they generic'd my costume, but I still crashed. They asked if it was OK to log into my account to check things themselves and I said sure. Then they emailed to say that they accidentally generic'd the wrong character, specifically the one that I logged the /petition from. When they generic'd the character that was crashing, I could log her in again.
So the quick solution is to /petition to have your broken character's costume generic'd. The better solution is to have NCSoft put some checks in place so that this doesn't happen. Maybe explicitly catch broken costumes in the client and report them as such, maybe establish a rule that costumes cannot be made invalid, or establish a procedure for genericing costumes during maintenance when they become invalid.
Goodbye and thanks for all the fish.
I've moved on to Diablo 3, TopDoc-1304