I read up to the "custom passwords". I have to shake my head quickly and shout "NO". As a majority of graalians don't use the most common sence and often, you guessed it, repeat passwords. Ever wonder why people are getting hacked left and right all the time? Leaked databases, I have seen and forwarded to Graal Staff. Where people hardcore own themselves by using the same password as there email. And some people have lost everything, facebook, myspace, aim, etc.. it's just not secure at all.. Let graal gen you a password, end of story.
As for account names, about Graal#### blah blah names.. Live with it, the problem is the lack of support (from developers) for proper usage. Basically, if you don't like it ignore it because of the following
All account's have an account name, but not all accounts have a community name. Accounts created before Graal###, have there community name set as there account name, ex:
Classic Subscription Account Test Results: (bloodpet)
player.account, returns "bloodpet"
player.communityname, returns "bloodpet"
As far as scripting goes, ALWAYS USE ACCOUNT NAME NOT COMMUNITY... or your script can/will break. (Those accounts that have Graal###, but never bought a community name)...
I don't know why people insist the Graal### names are problems, because its not a compatibility error but a human error on the developers behalf.. GRR
Best solution:
making Graal### invisable, and giving us a feature that is retard proof for scripters.
findplayer() and
findplayerbycommunityname(). People don't understand when to use them because they try using communit name's instead of account and it can't find them. It IS messy. But its not rocket science. there should be 0 complaints from anyone about the current system.