The obvious solution to the name problem

They, like first names, are only unique on a server, not across servers. So you have the same problem when the "skywalker" legacy from Rogue Moon comes to Red Eclipse and there is already a "Skywalker " legacy on that server.

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

The only obvious solution is to either take an new name or move to a new server / new game. Bioware at this point is not going to redesign character naming so that you can keep your name.

The legacy uniqueness isn't a good solution as for some of us being obliged to have the same legacy for all our characters is an issue.

The less we use it the more we are happy.

So: NO to legacy.

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.

I know this is how every MMO does things, but it is not necessary that it be so. In the real world, if I want to talk to Bob, I have to know his phone number or email address - I can't just tell my phone to "call Bob." Actually, I can, but only because I have Bob's number programmed into the phone under the name Bob. You say, how does /whisper work without unique names? I say, right click on the name in the chat window / social panel and select whisper. It's just a different way of doing things.

And yes, it would be very difficult at this late stage for SWTOR to change the way their database works. It would be a lot easier for the next MMO to consider that just because everyone has always done things this way, that they do not have to be done that way. Imagine an MMO where characters actually have decent names instead of the crap names you see everywhere that ruin immersion.

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

Interesting discussion, but unfortunately there is no solution in my view. But the reason why is not because a well thought out scheme that would allow multiple "Yodas" on a server is lacking. It is quite simply because Yoda from origin server "x" wants to be Yoda on destination server "y" and be as unique as he was on his origin server.

My guess is if you implemented a solution that would allow multiple Yodas with a unique identifier, people would complain they are not in fact unique. lol. Yoda wants to be the only Yoda and not Yoda 8675309.