M.C - Comments

Yes, it will be live in tomorrow’s update (which is the next one).

Any corrective activity - such as what FootyGamer did - that takes place after the ‘Built at’ time gets incorporated in the next iteration.

Those builds are automatic and happen at around 04:00 UK-time. The actual Data Update release happens thereafter, on a variable basis, as a staff member needs to finalise it. But most of the time it is within a few hours of the build.

For what it’s worth, to make it work with the SortItOutSI Data Update, you simply need to disable the ‘England (League) file in the update and use this lower-league database for England instead. You won’t have up-to-date promotions/relegations in England, of course - but that is the option that players will need to make.

Those wanting to start in the lower levels of England may not mind as much that the top 4-5 divisions are based on 2023/24.

Sorry not to have replied before - that really elongated wait time on the ‘Setting up game database’ step (and it will appear not to progress, visually, for most of the wait time) is because of the ‘Player History’ file. It adds 3,000,000+ records and so reading and executing those changes takes a long time.

It's not a bug, but it is a content-heavy file. It is optional to use and once it has done the one-time load, it has no effect on performance in-game, processing breaks or, indeed, the time it takes to load an ongoing save.

I'm afraid not. It is all integrated into a single file and there is no technical method to split it so we can't offer that separation.

The ‘drastic’ do-it-yourself approach that people have taken is to open the ‘Changes.fmf’ file and then search for and delete all of the Person records that have a UID of 2002042189 or higher.

I am more interested in knowing the reasons why you would want to do this, though, but I thought I would offer the advice all the same.

Oh, I understand. At this time, the SortItOutSI Data Update doesn't provide a playable Azeri league system. In order to play as Qarabag, you would need to use a custom database (in addition to the SortItOutSI Data Update) that provides that playable league system.

You could have a look at this thread, which maintains a list of custom database files from creators who are known to produce valid and safe files. MasterIgor has produced an Azeri file that enables it as a playable nation.

https://sortitoutsi.net/content/67061/fm24-nation-and-league-expansions-add-playable-leagues-to-football-manager-2024

Using it alongside the SortItOutSI Data Update should be possible.

Can you try and explain what you mean in more detail, please? I am not really sure I understand.

The club are definitely in the game.

I've moved the comment, because there is no value in a second thread existing. In reality, the best place for these sort of queries regarding individual players is the ‘FM24 Player and Staff Updates’ thread: https://sortitoutsi.net/content/65386/fm24-player-and-staff-updates.

Personally, I am not sure what the best mechanism to enact changes like this is. Of course, on an isolated basis, they can be made - in a file - to make such a change. But then that raises the question of whether we should - and, if we do - does that set a precedent to manage this particular variable on a global level? Because there is a question of feasibility, too.

On this specific case, I do see that the Minimum Fee Release Clause data is stripped out by the main Changes.fmf file. There may be valid reasoning behind doing that on an overall basis. I suspect the result is the game applying a new one programatically which perhaps, given his age and other factors, ends up being particularly low. I would need to consult the rest of the team to understand the best way to tackle something like this.

Yes, you certainly can. Previous releases can be accessed via https://sortitoutsi.net/football-manager-data-update/releases.

…and just to reiterate, I am working on understanding the cause of the error in today's Data Update (i.e. missing values in the Non Dynamic Data file) and rectifying it. But I may need support from others, so I can't promise a timeline to resolve right now.

FWIW, my very basic, working theory for now is that - perhaps - in the processing of the data there was a ‘cutoff’ point and so only players who have had CA/PA submissions more recently than X date have ended up being committed into the file. But I'll be honest - that is pure guesswork. I don't personally have any way to query the back-end site data and I am also not personally involved in the actual ‘data processing’ activity. Also, as I'm sure you can appreciate, the output in the FMF is extensive and consists of many, many records - so pinning down a root-cause in those circumstances, for me alone, is tricky.

I am fairly confident that the failure to write the updated CAs into the content of ‘Non Dynamic Data’ file is unintentional. That is something we will need to troubleshoot/bugfix. I will flag and we will get on the case ASAP - thank you for flagging.

In terms of the players you have observed that don't match a specific Ability Submission - this is intentional. The Ability Submissions don't work on the basis of ‘most recent overrides all others’. You'll notice that one player can have multiple Approved submissions (one per member). It factors all of these in to arrive at a final CA/PA value.

@Osarogie @thehet @andynufc10 @oopsupsideyourhead @ryanpark - tagging those who have specifically asked about this recently.

Just to confirm, a latest build of the CA/PA update (which is part of the Enhanced/Classic FM Data Update) was performed. It was finalised this morning, about 60 minutes ago.

To that end, it will be included from tomorrow's update onwards (unfortunately, it was completed too late for the build that was released about 7 hours ago).

On the note of presenting the ‘last update’ on the download page systematically, we are not going to do that because we are now very close to integrating these changes to be re-processed, daily, as standard - which was always the goal.

Ah, right - yes, I see now. Sorry, I completely overlooked that part as being different from what I had. In that case - yes, that should be possible.

On your account, I can see that you have an active subscription to the enhanced Data Update - which started on 3rd September 2025. I just want to confirm - do you believe you have made a separate, second payment for the Premium Membership product since that date?

Sorry for not replying sooner. In general, the Premium Membership applies automatically and immediately following the transaction being completed.

Unfortunately, in terms of who can directly inspect those transactions and troubleshoot a specific case - it is only the Site Administrator/owner. I will tag him in this post to draw his attention to it.

@Footygamer - can you please take a look at this account and assist when you can?

That is a different issue and one that needs to be tackled separately.

For context, Paul Pogba was removed by Sports Interactive in the 24.3 database. As such, him ‘disappearing’ starts from their decision.

Our solution is reintroducing him as a newly-created player. This is done through the website's web form, which allows for a limited amount of detail. As a starting point, that is the best that we can do. There may be the possibility to recreate him in a ‘fuller’ way, but this would need to be done outside of the website functionality and, with it, it would also mean it isn't possible for users to submit CA/PA submissions for him, nor to see him on the website as with all other players. So there is a trade-off.

So the change/extension to the rule is that concept around players bought/registered in one season being able to then be extra foreign players for the second season? Or that the players signed and registered in the first season are exempt from the age-restriction part of the rule in the second season? That is my reading of it, at least - I am not sure if it is the translation, but I can't really make clear sense of the rule from what you posted. In particular, this part:

"If foreign players born in 2002 who have signed contracts for more than one season and are included on the A Team List for the 2025-2026 season are signed with these players, they may be included on the A Team List for two seasons, subject to this rule.

In the 2026-2027 season, at least four of the 14 foreign players must have been born on or after January 1, 2003."

If so, I must admit - I do not think such a rule is possible to replicate in the Pre-Game Editor.

This is normal. The Operating System filename (e.g. ‘Classic FM - Changes.fmf’) and the in-game filename (e.g. ‘_sortitoutsi.net FM24 Data Update - Changes.fmf’) are two different values. In many cases, they will be the same, but in the case of the paid Data Update they are different because the Operating System filename is re-processed.

The enhanced Data Update includes many of the same files, but also some extra files. This is what differentiates the two versions. Rest assured, if the downloaded files have ‘Classic FM’ at the start (as yours do), you have in fact received the enhanced Data Update.

The latest build of the CA/PA community submissions is underway as I type this. There has been some (small) delay, owing to various other priorities - including troubleshooting some issues with the Data Update (unrelated), but also some important development work being done on other site functionality.

Some of that work is, importantly, a direct precursor to integrating the CA/PA submissions into a daily update flow. That isn't the case effective immediately, but it is close.

I would expect a new CA/PA update to be integrated into the main Data Update within the next 24 hours. I've also made the suggestion around visibly publishing the ‘last update’ timestamp - that is a task for the Site Administrator/Owner to decide on and implement, assuming it is feasible to do so.

Just to confirm: a few days ago (and we are not sure who/what caused it) the newly-created version of Paul Pogba was deleted. This was an error.

He has been reinstated - I would expect that when today's Daily Update is processed, he will be back in the game.

Please note: this is an English-speaking forum. As such, we ask all posts are submitted in English.

That being said, I've translated your post and so understand the subject. It sounds like you are saying that in today's/the most recent update, certain squad updates have regressed/moved backwards (or possibly players have disappeared entirely who were previously there).

Can you please provide a few individual examples of players where you believe the update is now incorrect, as a starting point? This will help us troubleshoot and try and understand the cause.

You should not have to do anything, specifically - your account should reflect your Premium Membership status pretty automatically following making the payment. I can see that your account does not yet reflect that Premium Membership status. Unfortunately, I do not have any access to verify payments that have/haven't been made. What I can offer in terms of advice is that you should not try to pay again, nor take any other steps for now. The Site Administrator will be able to assist.

With that in mind, I am tagging the site administrator, @Footygamer, who can probably clarify. It could be a delay in activation (i.e. a delay on the site's end), or it could be that the payment hasn't finished processing.

I've got it on my list. I am currently just finalising an update to Malaysia (nearly done) and I will turn my attention to South Africa next. I will need to take the existing, base file as my starting point and as I didn't personally make that, I am not sure exactly how far it is along.

It is worth noting that whilst I will - as part of updating that file - reflect name changes (team and competition), if you use the ‘Real Name Fix’, that will overwrite anything in the Data Update file.

Well, there is no guarantee, strictly-speaking - but by prefixing the relevant files with an underscore they are extremely likely to stay first in the list. The primary reason it has been done is to preserve their load order relative to other custom editor data.

In terms of gameplay functionality, the load order is mostly not important. In the SortItOutSI Data Update, it is important that the ‘+2 Age and Contract Years’ file comes before the ‘Changes’ file. Aside from that, the order of the files overall is fairly interchangeable.

However, to support graphics appearing reliably, the key thing is for the ‘Changes’ file to be the first file on the list that adds any new Person records. In the SortItOutSI Data Update, it is the only file that adds any Person records - so in isolation, the Data Update is fine.

Other popular add-ons (like the Real Name Fix, for example) add new Person records. Other creators' custom databases may also add new Person records. As long as those are after the ‘Changes’ file in the in-game list, the newly-created player facepacks (which are now being worked on) will work reliably.

No, I'm afraid that is not correct. You should be using either the ‘Non Dynamic Data’ file or a combination of two ‘Dynamic’ files of your choice (any one of the ‘Data’ and ‘Pre Window Budget’ files).

The ‘Non Dynamic Data’ is providing CA/PA values based on the central Data Update's ability valuation. Each ‘Dynamic Data’ file provides a variance on these, to provide some randomisation.

Classic FM - Non Dynamic Data.fmf

From what I can see on your account, it appears to indicate your Enhanced Data Update subscription is active. Please note: the ‘Premium Membership’ is a separate product, so your account doesn't get tagged with that if you only purchase the Enhanced Data Update.

If you visit https://sortitoutsi.net/football-manager-data-update, directly below the green ‘Download FM 24 Data Update’ button, it should indicate ‘You have Classic FM the Enhanced Data Update…’

If it says that, clicking the button will automatically provide the paid update. If it does not show that and it prompts you to buy it again, please do let us know/confirm.

The newly-created players have that two-year offset applied to them directly (rather than via that +2 file). It's do with how the data is integrated. I can't really explain the technical ins-and-outs in further detail as I wouldn't know how. The primary Data Update is fundamentally based around the idea of offsetting everything, versus using custom, future start dates.

However - have you tried using the ‘No Date Data Update’ (https://sortitoutsi.net/football-manager-data-update/no-date-changes-data-update)? I am not sure if this removes the offset, but I would be surprised if it didn't - as I think that is the whole point of it.

To clarify: I'm not saying you cannot pair the Data Update with other custom database files. However, the types of files that you can pair it with, successfully, depends on the function of those other files.

The Data Update provides a main transfers/contracts update, newly-created players and updates to playable leagues (i.e. promotions/relegations, 2025/26 structures).

Using extra playable leagues from other content creators should, typically, be fine - if the files they are providing only create those playable league structures. Which is the case most of the time. I, myself, use a variety of extra playable nations from creators I trust.

However, if you are also using custom files that are trying to provide a transfer update (for example), that is where things can get messy. The scenario where a particular individual/player is assigned to the wrong club, for example, where the SortItOutSI Data Update has him transferred to a new club can only happen if there is some other file that is overriding that change.

Again, in the scenario you are in - my advice is to test with the SortItOutSI Data Update only. This way, you can see for yourself that those files result in everything being correct. If you then add back in other files and the problem then occurs, it gives you/us a good sense that the cause of the problem is some other file. If you only use the SortItOutSI Data Update and the problem is present, this is a good indication that the fault is caused by the SortItOutSI Data Update.

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.