![]() |
|
#1
|
|||
|
I heard that there were some issues initially with teal crosschecking name availability, so I'm a bit concerned if I move my characters to teal that someone will have my name and I'll be screwed. Anyone know if this was true and, if so, what was done to rectify it?
| ||
|
|
|||
|
#2
|
|||
|
Anyone know? I'd like to make the change to teal, but I'm worried if this happened that a name could be taken and I'll be stuck with the "x" no one wants.
| ||
|
|
|||
|
#3
|
|||
|
I tested and cant make a teal name if the green one is made, deleted green one and teal is allowed then. I think its working normally now
| ||
|
|
|||
|
#4
|
|||
|
It was fixed in a few days after teal launched. As far as I know there is no precedent for resolving legacy names (those that came first, either on blue or green) with complications arising from the period of name anarchy
My guess is you can /move and if it doesn't work or you end up with an unexpected suffix, you'll have a strong case to keep your name if you had it first. it will be a petition though. Do a forum petition and state your case if it doesn't go how you were promised with the green/teal move. I imagine it will be a simple solution in which the legacy name wins. | ||
|
|
|||
|
#5
|
|||
|
I moved my druid from green to teal and didn't got any problem with my name plus rogean said that database name are shared between green and teal so should be impossible to have somebody with your name on teal.
| ||
|
|
|||
|
#6
|
||||
|
Quote:
| |||
|
|
||||
|
#7
|
||||
|
Quote:
| |||
|
|
||||
|
#8
|
|||
|
Thought they got this all sorted out.
| ||
|
|
|||
![]() |
|
|