The obvious solution to the name problem

The name problem I define as the restriction on most MMO servers that each character name be unique. Essentially, this boils down to databases and their fundamental requirement for one unique field (that is, one particular characteristic that is unique for every database entry). Character name is the obvious first choice for this unique field, because names are easy to remember. However, this causes other bothersome issues with the player base, beginning with frustration when their desired name (and the first half-dozen alternates) are all taken. The problem grows as the server population does. And when you add in server merges, you get players up in arms at the prospect of losing the name they've played under for months.

The obvious solution is to choose another unique field. For instance, what about a six- or seven-digit number? Most servers will not see 10 million players, so this number can easily be unique. Also, every player in real life has to deal with ten-digit numbers on a regular basis (phone numbers). Format the number correctly (in three- to four-digit blocks) and present it as a "Galactic ID number" or "Universal call code." Implement a context-sensitive search function on mail and social windows, where the entry of a character name or partial number will result in one or more database entries, complete with character name, class, level, ID number, and perhaps other information, all in one line. EVE Online has such a function, so it is certainly doable. Also, perhaps a tooltip that displays caller ID over a character's name in chat. If a player wants to name his character John or Luke, he'll just have to make sure to tell people his call code.

or they could make the legacy the unique field, seeing as its already treated that way. I see no reason to limit first names in this case, so long as you make legacy available on character creation for servers and then either lock xp access to it or something similar until level X

But Legacy cannot be a unique field, since each Legacy can have up to 8 characters associated with it. Also, you cannot have a unique field that is a combination of two non-unique fields.

this is an egghead solution. So you'd need to know the persons id code to invite, mail, whisper etc?

You do realize that the obvious solution to the name problem is stop taking names so seriously? This is just a game!

I hate to break the news to you, but I expect the unique identifier *is* a number. Name (string) comparisons can be messy and long. Number comparisons are fast. There's no reason NOT to use a number.

Additionally, when somebody deletes their character, the "name" indicator on stuff they have crafted becomes "worn off". If the identifier was just a name, that would presumably be the identifier used on the crafted stuff, and thus still be there even though the character has been deleted. I would only expect the "worn off" functionality if it was a number identifer, that then goes into the database to look up the corresponding name. If there is no corresponding name anymore THEN it does the worn off message.

And, of course, you're missing the obvious reason why names are unique. Communication. How does "/whisper Bob" work if there are 25 Bobs? or "/invite fred" if there are 30 Fred's? or "/ignore SirSpamAlot"

Names need to be unique because that's how we, as players, identify other players. (and no, legacy name wouldn't be a good idea. Many people, while under the same legacy, prefer to keep their different characters friends/guilds/etc. separate. Not to mention that you don't GET a legacy until ~32 levels in)

How dare you use logical, well thought out answers as a response!!!

/invite TK421

Legacy needs to be chosen at character creation. Don't let the points start accruing until the end of chapter 1 as currently, but if they make Legacy unique, and first names not, then it has to be done that way.

First names need to be unique within the same legacy, but not unique on the server.

most people fail to realize that the invite system works on that single name. otherwise we would have to type

/invite john doe

which means we would ahve to rememeber everyones legacy name, and display it all the time. not that big a deal since most peopel right clcik to invite anyway. but if u think about it, if somsoen takes a legacy name, then you are still screwed if you want to use it.