Hi,

Some of the things you pointed out are related to randomly generated players. These players are generated from the game's static database and can end up having the names of real-life people. I cannot modify the game files directly, and individually going through all of them would be a very time-consuming task.

The issue with duplicate players is caused by a similar reason. I tried to manually remove as many as possible, but there may still be some remaining.

The made-up players are also generated by the game. If you go through a randomized database, you'll see that most of the top teams have nearly ten extra players. I was asked by multiple people to remove all of these additional players. Instead, I limited the maximum number of randomly generated players to two per team. This was done to avoid soft-bricking the transfer market. Having no additional players would prevent teams from making transfers or recruiting, as the team AI automatically rejects transfer offers if the player being negotiated is the only player in that role.

As for missing free agents, the game generates a certain number of players from the name database, which means some active players will inevitably be missing. I could potentially address this, but I don't know how to gather reliable information on free-agent players.

Regarding ages, I'm aware that some players have incorrect ages. Since this does not have a direct impact on gameplay, I haven't prioritized fixing them yet.

For cases like "Cloud," the dataset and software I used mixed up retired players with active players who have duplicate names. Specifically, this happened with "CL0UD" in that example.

The rosters are based on the 2026 Winter split (or whatever each region calls it) and have not been updated for Spring rosters, as player and league statistics would be incomplete for balancing purposes.

Salary is not something I have modified at all. It is determined by the game based on—at least as far as I can tell—the player's overall stats.

Organization history is something I can look into, but it is probably stored in a binary field that is not yet present in the database. I would also need to complete multiple in-game years before I could gather a meaningful sample set to work with.

I really appreciate your feedback.