|
I've reported problems with generated names a couple of times already, but I'll do it again. This time, I ran an experiment specifically to try to detect it:
I started a new league in the US, no foreigners coming in thru the draft or int. FAs, and the USA language set to 100% US-modern. Before the draft pool was announced I changed the US's language (from the drop-down list in the Nation Editor) to Japanese. When I looked at the pool, everything seemed okay... so far. At the end of the year, I changed the US language again--this time to 100% Hispanic. In the next draft pool I got plenty of Hispanic guys, but also some (about 20% of the overall pool) who had Japanese first names and Hispanic last names. I simmed ahead 5 seasons to see if it was a temporary situation that would gradually sort itself out, but that didn't happen. Finally I changed the language to German, and got a draft pool of players with German surnames, and German, Japanese, and Hispanic first names.
Obviously this is an extreme example, and something that no one would ever do "for real". But it does confirm something I've already seen in other leagues created under "real" conditions: some names being generated from 2 entirely separate namesets. The problem seems to be with first names being chosen incorrectly; in every instance I've experienced, the last name correctly matched the set that was assigned to that particular country, but it was the first name that was going "over the wall" into territory it didn't belong.
(Just to add, I've had this happen while using Questdog's namesets, but also with all the default files, so it definitely seems to be a game problem, not a mod problem.)
|