M.C - Comments

Appreciate your efforts to help, @WelshViking7. Just to let you know, myself and Luke were able to resolve it in another thread - which is where it was initially reported.

For anyone wondering, the issue was that they were attempting to use all of the ‘Dynamic Data’ files simultaneously. In fact, this is the probably the most common cause of the Data Update crashing during that initial setup phase.

OK. So the issue is that you are trying to use all of the Dynamic Data files at the same time.

You‘ll note in the download, there are a bunch of files in an ‘editor data’ folder and then some in further ‘Optional’ sub-folders. Specifically, the bunch of files called ‘Classic FM - Dynamic …’ are not all meant to be used together.

Delete all of those from your ‘editor data’ folder. There are 30 in total - named ‘Dynamic Data’, ‘Dynamic New Player Data’ and ‘Dynamic Pre Window Budgets’ (each numbered 1-10).

This should leave you with 53-54 files. One of which is the ‘Classic FM - Non Dynamic Data.fmf’ file, which you will want to keep.

As a starting point, get as far as having 53-54 files in your main ‘editor data’ folder (without any ‘Dynamic’ files) and load up a new game. This will work.

If you consult your original download, you’ll see in the ‘Optional Dynamic Data’ folder there is a readme that explains their use. But for your convenience:

Those files are used to randomise certain things to keep the game world fresh for more regular players. They are optional and, if someone wants to use them, they need to remove the ‘Non Dynamic Data’ file and replace it with one ‘Dynamic Pre Window Budgets’ file and one ‘Dynamic Data’ file. There are ten variants of each.

One thing I’ll take the opportunity to point out is that the ‘Dynamic New Player Data’ files are obsolete and have been removed from the very latest Data Update as they serve no purpose anymore.

One simpler approach than picking through files you may find is to simply delete everything from your ‘editor data’ folder, download today’s update and then copy across only those files not in an ’Optional’ sub-folder. Again, you should end up with 53-54 files; not 83-84.

Apologies - this report (your original post) escaped my attention.

I can assure you that, fundamentally, the Data Update does work. I suspect you have an installation error at your end if it is not progressing at all.

The most common thing that causes a crash at that initial stage is the attempted use of the Dynamic Data at the same time as the Non Dynamic Data. Or perhaps the attempted use of some other update/custom editor data files that are incompatible.

As a first step, can you please share screenshots showing your Editor Data folder and, ideally, also screenshots that show the list of enabled Editor Data (which can be selected when you are selecting which database version to use). This will help me diagnose what is going wrong for you more definitively.

It would be good to get a sense of all of the custom databases you are using - clearly you have quite a large number activated. I appreciate most of those may be custom playable nations (which shouldn't, theoretically, cause any issues), but you never know for sure what those files actually contain within them.

Also, what game mode are you playing in?

It is deliberate that the ‘Changes’ file is near the start of the load order. The issue, a few days ago, was that another file (the ‘+2 Age and Contract Years’ file) was not also brought to the front.

If you install the Data Update in its entirety, you should end up with the +2 Age and Contract Years file first in the order and the ‘Changes’ file second. This is the correct order and will result in everything working just fine. When we fixed it, we did not revert the ‘Changes’ file to be down in the middle of the order. We simply brought the +2 file up the very front. Again, this is deliberate/expected and planned…and does work. Crucially, this order is what enables new player UIDs to be consistent and, thus, support facepacks for those newly-created players.

I would strongly recommend you do not re-save the files under different names. If a standard install is resulting in you having problems, please share the details of what those problems are and we can help troubleshoot. Data Update content has been thoroughly tested and I can say with a high degree of confidence there is no issue with the load order we currently have.

Amending the salaries of players is not a standard feature that this update provides.

All player transfers/contracts are submission driven. I am sure you can imagine that, on a global scale, access to player wages is variable and often not published at all. As all submissions need to be moderated, evidence would need to be provided that confirms the wages for this to be viable. I think this would limit the number of submissions. It would also significantly increase moderation time.

As such, it should be expected that individual player salaries are not updated following transfers. Sometimes, they’ll have a salary set in the PGE and therefore carry that over. Other times, the game will decide.

Just to circle back on this - following some further troubleshooting, I believe this has now been resolved.

In simple terms, the Dynamic New Player Data files were an unintended hangover following some general file structure changes a while ago. Those who use the Enhanced Data Update will now see that, in the Optional Dynamic Data folder, there are only two types of dynamic data files remaining: ‘Dynamic Data’ and ‘Dynamic Pre Window Budgets’.

Using one each of these is all anyone needs to do - and the fault with many players having blank names is resolved. The ‘Dynamic New Player Data’ files have been removed. No functionality is lost - the ‘Dynamic Data’ file takes care of what the ‘Dynamic New Player Data’ was originally intended to do.

Apologies for the inconvenience.

You must have some other data loaded that is also modifying the structure/divisions of the Spanish pyramid.

Used alone, the Data Update Spain file works just fine.

Are you using any files that make further divisions in Spain playable? If you’re unsure, please share screenshots of your ‘editor data’ folder and your in-game database selection screen, which is where you can enable individual data files.

The Premium website membership and the Enhanced Data Update are two separate, paid products. Purchasing the former does not, unfortunately, provide access to the latter.

If you go to your profile's ‘Shop Orders’ page (https://sortitoutsi.net/shop), you should see two distinct products. You can also prompt the purchase of the Enhanced Data Update from the main download page.

Just to clarify the distinction: Premium Membership grants access to direct downloads without the use of third-party file hosting sites. The cost is directly to offset the hosting and bandwidth that the site then provides.

The Enhanced Data Update grants access to that specific download. As an aside, access to the Enhanced Data Update is free for anyone that contributes a certain number of submissions to the Data Update in general, as a way to thank those contributors. Of course, the free version of the update is available to all members and it does provide a lot of content - including promotions/relegations, updated squads and so on.

Both cost £10 for a period of 12 months. In that period, you'll get access to every version of the Data Update released during that time, should you choose to purchase it.

I’m replying because it feels the right thing to do - and because I understand your POV.

Just for context, I explained the situation because I‘m a moderator and felt it my duty to clarify the situation. But it’s not my place to justify the pricing model further - I volunteer my time to help moderate the forums. Hope you can appreciate my perspective and why I am sharing the info that I am, but why I cannot discuss the detail/intent further.

I am tagging the site owner, however, so he can have his attention drawn to the feedback - @Footygamer - think you should have a right-of-reply to this.

I suspect this will apply equally to all of you: the Premium website membership and the Enhanced Data Update are two separate, paid products. Purchasing the former does not, unfortunately, provide access to the latter.

If you go to your profile's ‘Shop Orders’ page (https://sortitoutsi.net/shop), you should see two distinct products.

Just to clarify the distinction: Premium Membership grants access to direct downloads without the use of third-party file hosting sites. The cost is directly to offset the hosting and bandwidth that the site then provides.

The Enhanced Data Update grants access to that specific download.

Both cost £10 for a period of 12 months. In that period, you'll get access to every version of the Data Update released during that time, should you choose to purchase it.

Specifically on the staff salary demand…isn't that showing that his wage demands are £65k per year (i.e. not per week)? So more like £1.2k per week?

My assumption is that the other salaries you mention are being shown to you, also, per year/annum.

In your position, I'd first check the game settings to see if things are being displayed to you annually. Change that to weekly, if that is what you are used to/measuring it against.

I fear you may have an issue with installation, or other files interfering/taking precedent, at your end. Spot-checking the first handful of your examples - none of those are the case in the Data Update.

I can see from both a check of the website data and the corresponding situation in-game that they are all updated as expected (specifically, I checked Buonanotte, Barco, Chalobah & Rak Sakyi). In case you're not aware, the Data Update is driven directly by community submissions and, essentially, all of these have been submitted and are in effect. A good way to consult the situation for any given player is to look them up by searching for their name via https://sortitoutsi.net/football-manager-data-update/contribute. This will show a page and indicate their current status in terms of club, transfer, contract etc. Anything approved is integrated into the Data Update on a daily basis and the two very reliably match.

Can you share screenshots of your ‘editor data’ folder and/or the list of enabled Editor Data files, from the in-game Database selection dialogue window, so we can try and troubleshoot what is happening for you?

I am sure we could arrange an announcement/clear indication (in any/all relevant places) once that pivot to daily updates is made, yes.

If it helps, the LNC files are essentially containers for information. They're text files and you can add extra rows to them, thus extending the content.

They have a strict ‘structure’ to how the data needs to be formatted - for example, for a stadium entry you need to enter (as an example):

"STADIUM_NAME_CHANGE" 996 "Stadium de Toulouse" ""

The first part specifies the type of change, the number is the Unique ID of the item being changed and the text string is how it will display in game. Extending the file is as simple as adding a new row with a new entry.

The same concept can be applied for any LNC file. The bit you'd need to look up is the Unique ID, which you can do by enabling the relevant option in-game to display them and then just browsing/finding the item in-game.

Can you please share screenshots of your ‘editor data’ folder and/or the ‘Editor Data’ view in-game (during database selection) that shows which files you are using?

Respectfully, you are having a different experience from everybody else who is using the Data Update and so I suspect this is either interference from other files and/or an installation error.

If you have nothing in your ‘editor data’ folder then it could be that you have additional mods that you subscribe to via the Steam Workshop, as I think those get populated into a different location (possibly).

Categorically, the Data Update has the examples you cited as incorrect, configured correctly.

The only software you can open them in is the Football Manager 2024 Pre-Game Editor.

If you would like an understanding of what any specific part of the SortItOutSI Data Update contains, though, please do just ask - it may be easier for me to just give you an overview and/or more detail on a specific file if you want that detail.

As a broad summary, the Data Update provides:

• up-to-date transfers and contract changes, globally. It is updated daily and is community-submission driven.
• updated league structures, rules, promotion/relegations and competition histories for many (not all, yet) nations, reflecting 2025/26.
• updated continental qualification to reflect 2025/26.
• approximately 20,000 newly-created players who are part of the footballing world but were missing from the vanilla 24.3 database.
• as mentioned, the enhanced Data Update also provides updated CA/PA values for many, many players, which are partly community-submission driven.

Just to confirm - and @WelshViking7 has it pretty much correct:

‘Classic FM - Non Dynamic Data.fmf’ is the file that provides updated CA/PA ratings. This comprises changes that are done in one of two methods: a data-driven, global scrape of performance data from the previous season, conducted by the Site Owner as a one-off activity (which has been done following the completion of the 2024/25 season). Now, of course, those stats and figures are one way to assess player ability. The other method - perhaps more dynamic, perhaps more contentious - is on the basis of community submissions through the website.

Any community member can submit a CA/PA recommendation/proposal/change for any player. These are moderated and anything determined to be a reasonable submission should get approved. Each community member can have one ‘active’ submission per player, at a time (i.e. if someone re-submits, the system will take their most recently-approved submission into consideration).

From there, all of the active submissions (from all members) are factored in to produce a consolidated, overall new CA/PA for that player. This would then be recorded in the ‘Classic FM - Non Dynamic Data.fmf’ file.

However, unlike with the transfers/contract changes that are delivered via the ‘Classic FM - Changes.fmf’, the re-processing of these new CA/PA values isn't integrated to happen in an automated, daily way. At present, it is iterated approximately monthly, so there is some lag time behind new submissions being reflected in-game. In the coming days, this file will be re-processed and, as I'm sure you can imagine, the excitement of the transfer window has meant a lot of moves and a lot of people submitting updated values for players who have made moves, or been the subject of speculation.

Obviously, football is a game of opinions and CA/PA ratings in Football Manager are a natural extension of that. I can say with some certainty that the excitement around Nick Woltemade has been reflected through community submissions (you can look up a player and see the submissions and their status here: https://sortitoutsi.net/football-manager-data-update/person/91187791). Is it all justified and is he going to go on to become a world-beater? Only time will tell.

Now, in terms of the Optional Dynamic Data files. These exist to provide some variation for people who want a level of randomness to proceedings. Each file offsets CA/PA values of all players with a different variation on the calculation. They're intended to ‘freshen things up’ for experienced players who maybe feel the game is getting stale/predictable in terms of who the ‘sure bets’ are for development etc in-game.

The way I think of it is: for the most realistic experience, use the Data Update files without the Optional Dynamic Data. Debate about how ‘realistic’ the ratings are that the community have submitted could, of course, go on forever. But the consolidation system should even things out over time if people make those submissions on an ongoing basis (and by all accounts, they are so far).

For a level of unknown variety, use a random combination of Dynamic Data files (one of each type, simultaneously).

Yes, please do make a submission - that is the basis for any changes that are made. So in simple terms, I think the new Data Update fixes the overall issue and, in Ederson's case, there is just a need for someone to submit that change with the relevant proof and that'll then get integrated.

As a first step, can I please ask that you ensure you have downloaded and are using the latest Data Update?

From your screenshots, I believe you are using yesterday’s build which, unfortunately, contained a bug that caused the contracts to be incorrectly offset.

Replacing with today’s Data Update should resolve the problem across all players in the database.

No worries - I am glad that it turns out it is correct, after all, and that I did understand what I had researched correctly. Fun fact: for this nation, I had to get the official PDFs and run them through a translator to get to a point where I could see the official, written registration rules before building the file. Enjoy!

It's correct that yesterday's Data Update changed the load order of the Data Update files…and that did cause an error with contract lengths for those using the Data Update.

That has been resolved in today's update, however, and furthermore I do not think it has any bearing on the situation you are in, specifically.

In your situation, my straightforward advice would be: make a separate folder somewhere and cut and paste all of your ‘editor data’ content to that folder. We're just using that as temporary storage to give you a clean slate.

Then, install the SortItOutSI Data Update and only that update. This gives you a clean install. Test and ensure that works (it should/does). Then, look through your backup folder and carefully integrate whatever parts you want to use alongside.

Fundamentally, I don't advise using two all-in-one updates together. They will invariably overlap with a lot of content and they will clash, one way or another.

Just to confirm: I am able to replicate this. There is going to be a logical explanation/reason and I am sure we will be able to get to a point where it is resolved.

The root-cause may be the re-ordering of files that took place a couple of days ago - but that is speculative and based on what I have briefly looked at, unlikely. Investigating properly right now.

OK that is useful to know - thanks for persevering. I will see if I can replicate when using the Dynamic New Player files. I will also inspect those files to see if there is any obvious reason in their structure that could be causing this.

Braiden Graham, as the example case, was actually last in the official Football Manager 24.0 database. Of course his removal from the 24.3 database is down to Sports Interactive and has nothing to do with this site, as such.

He appears searchable on the site because the site catalogues players from historical versions of the database, too. You'll notice that if you try to edit his details (to make a submission of a transfer/contract, for example), you'll be presented with confirmation that he is not in the 24.3 database.

He is a good example of a player who has not had a newly-created player submitted at this time. So, effectively, that explains his absence when starting a game using the 24.3 database - whether with our Data Update, or without it.

From a UI perspective, I can understand why it may be confusing - because he is discoverable via search, the assumption people will have is that he's in the official 24.3 database. Seeing that, they won't submit him as a creation.

The right action to get him into the game is for someone to submit him as a newly-created player. Once approved, he'll appear via the Data Update file like all the others.

I am just curious - in terms of what you think is incorrect, how is it functionally in-game?

I am asking because when I was making the Turkey file, I was consulting the rules and these are the rules I attempted to build the rules against. Perhaps I have not implemented it correctly - but when I was testing, it was working for me (at least in terms of the best-fit possible to my understanding).

Specifically, for the first in-game season (which is 2023/24, but which represents 2025/26 in real-life), Turkish Super Lig teams should be allowed a total of 14 foreigners, a maximum of 12 of whom can be over 23 years old. Which essentially means that at least 2 of them must be under 23 years old. This was the closest estimation possible to the threshold of being born on or after 01-01-2023.

Similarly, for the secnod in-game season (which is 2024/25, but which represents 2026/27 in real-life), the rule is set up to change so that at least 4 of the 14 foreigners must be under 23 years old.

If how I have described it above is how you are experiencing that it is working in-game, I would say that this is the closest match possible to the real rules. I have selected 23 years old, in the rules, as the threshold because that is what the intention of the real-life rule is, I believe.

As much detailed feedback you can provide about what is functionally incorrect would be very useful - I am very happy to review the implementation and correct anything that can be corrected.

Full installation instructions (step by step) are on the download page at https://sortitoutsi.net/football-manager-data-update. Best to follow those as they are definitively accurate.

Thanks for sharing. In terms of the files you're using, that looks to be a ‘clean install’ of just the Data Update.

I must admit, looking at the screenshot, it feels there is something strange going on. When I look at the player names that are showing and compare that to the players that have been newly-created through the Data Update, it doesn't look like it is impacting those players - at least, not all of them. Which was my first suspicion.

As examples, I can see the names (in your screenshot) for Marcelo Trippel, Elias Fali Vard and Mathieu Nguefack. When I look at the players who have been newly-created for Borussia Mönchengladbach, these are three of a total of five (https://sortitoutsi.net/football-manager-data-update/team/908). So it isn't simply blanking the names of newly-created players.

Of course, some of the other players that we can see are also players that exist in the vanilla database.

It would be great to try and ‘identify’ some of the missing players, individually, to see if there is any pattern. Also, it would be good to understand what settings you are using as part of your game setup. Are you using either the setting to ‘Add players’ and/or ‘use fake names’? I am just speculating, at the moment, and trying to build a picture of what is happening for you.

Just responding to acknowledge this - one other person has reported this in a separate thread, too. For now, I cannot replicate this using a clean Data Update-only install.

Using the latest version of the Data Update, either the free or enhanced version, enabling various combinations of files and all player names appear as expected.

Can you please share a copy of your Editor Data folder so we can ensure you are running only the Data Update files? And also a screenshot that shows which Editor Data files are enabled in-game, just in case that gives us any sort of clue?