M.C - Comments

I appreciate your first post didn’t get a reply, but there’s no need to repeat your post. We also ask that all posts are made in English.

The structure of the Data Update has changed recently. The ‘Changes’ file is now called ‘Contracts’.

All of the content is still there - just the files have been shuffled around a bit.

It is that unconfirmed format for 2026/27 which makes it tricky to create with full authenticity. I think it's well-publicised that the Super League 2 will return to a ‘single group' format but it's unclear about how the promotions in to that league will work.

I've got a work-in-progress file that I've started for Greece to update it to reflect 2025/26 - the plan is to absolutely do my best. As a minimum, I'll try and reflect the known structure for this year and next year and I'll estimate the structure around it.

As best I can work out, between Super League 1 and Super League 2 there will operate a ‘two up - two down’ system. So, two teams get relegated and two teams get promoted.

Between Super League 2 and the Gamma Ethniki is where things get a little more complicated but, if I have it correctly, a total of 8 teams will be relegated from Super League 2 - the bottom four from each of the North and South, which is decided following a second phase (contested by the bottom 6 of each group from the first phase).

Being promoted into the division are four teams. Two of those teams come from Gamma Ethniki Groups 1-3 and the other two come from Gamma Ethniki Groups 4-6. I think the process for these promotions is simple enough - of course, the important thing is that a total of four teams go up, as this results in the correct number in Super League 2.

Relegation from Gamma Ethniki appears to be a total of 18 teams. It's effectively the bottom three from each of the 6 groups, following a second phase. How those 18 teams get replaced from the regional divisions below, I'm not sure yet.

After all of that, you end up with the right numbers for 2026/27. I have no idea how the Gamma Ethniki promotion to the Super League 2 changes, however, for that second season. Of course, Super League 2 will be a 16-team single league for 2026/27. At the end of that season, is there any understanding of how many teams will be relegated from Super League 2? Will it remain as 16 teams for 2027/28?

If you have any sources that I could read up on, I'd appreciate it - it's OK if those sources are in Greek; I can translate them as necessary.

Please take a look at the thread here: https://sortitoutsi.net/content/74544/our-data-update-just-got-a-huge-upgrade

Your specific question, as well as some other common ones, are answered in that post.

That will work but you’re effectively making a concession not to use the Player Attributes file, which contains all the modified CA/PA values from the Data Update.

If you chose to use your own file, it would enable you to use all of the files from the Data Update and you could keep them updated.

So - firstly, yes, you have the general concept correct: the files at the bottom of the list will take preference/be applied last.

Where I refer to appending your alterations - I just mean opening an existing FMF file and then making further changes, before saving that file again. No need to use the ‘merge’ function.

Making your own file is as simple as opening the Pre-Game Editor, selecting the database (24.3) and loading it. From there, simply start to make changes. As soon as you make a database change, you'll see it shows there are Database Changes (1) (top-left section). As you make changes, that number in brackets will grow. When you're done, then save your file (File → Save Editor Data As), thus creating an FMF file. The file you've saved will contain only your changes.

I believe this has now been resolved. For yourself, or anyone else suffering the same issue, please re-download the latest/current Data Update and you should find the Remaining Wage Budgets are back to expected values.

OK, thanks - that's useful context.

The basic premise is that Editor Data files are read and applied in the order that they appear in-game (in the window where you select your database version and enable which Editor Data Files you want to use). The ones at the top of the list are read and applied first.

Therefore, files further down the list will overwrite files higher up the list, in any scenario where more than one file makes changes to a particular value.

In terms of the Enhanced Data Update files, the primary file that alters CA/PA values is ‘Classic FM - Non Dynamic Data.fmf’. It should be noted, though, that in the last 24 hours the overall structure of the Data Update has been altered and so the equivalent file is now called ‘sortitoutsi.net FM24 Data Update - Player Attributes.fmf’. I'm mentioning this because if you download the latest update, you may find all the filenames are changed and be confused.

For your CA/PA changes, I'd recommend either:

1. Loading the ‘Classic FM - Non Dynamic Data.fmf’ / ‘sortitoutsi.net FM24 Data Update - Player Attributes.fmf’ in the Pre-Game Editor and appending your alterations into that file.

2. Making your alterations in a brand new file, which you save with a filename that comes later alphabetically (e.g. ‘zzMyChanges.fmf’).

The reason for doing #1 would be to allow you to lookup and see what the CA/PA value is in the Pre-Game Editor on the basis of using that file (i.e. what is the value currently, so you can decide whether you want to change it at all). The drawback is that you need to load that file, which contains a lot of changes, and so it is slower to work with.

The reason for doing #2 is that you are starting from an empty file and it'll be faster to work with in the Pre-Game Editor. The drawback is that you can't reference, in the Pre-Game Editor, what the CA/PA value is for any given player - because what you'll see is the default/vanilla values that those were in FM 24.3.

Another important, underlying reason to do #2 would be the fact that it would enable you to download (and use) the latest Data Update file at your leisure without overwriting your work. Otherwise, if you make a load of changes, you can't then grab the latest version and apply it over the top - because that would remove all of your changes.

In terms of a recommended approach for altering playing positions - the SortItOutSI Data Update doesn't alter positions of players and, therefore, things are simpler. Option #1 or #2 would be equally acceptable. I'd recommend option #2, overall - by quite some distance.

Can you give me a sense of the nature of the alterations/tweaks/changes you want to make?

On that basis, I can provide some targeted advice and - if required - explain what files that are part of the Data Update you should be appending your changes into and/or why you're seeing inconsistent results thus far.

Just wanted to acknowledge this - I am able to replicate this. We are investigating this and will seek to get this resolved ASAP. It is definitely an unexpected error - we just need to identify the cause and tackle it.

Apologies for the inconvenience.

We don't have control over the Sports Interactive data, unfortunately. Whilst it is technically possible for an update to correct this to be produced and integrated as part of the Data Update, we don't currently consider these sort of errors in-scope for the update. If we started to manage these sort of things, it could lead to an unmanageable workload.

With that in mind, I'd recommend submitting this to Sports Interactive. They have a dedicated forum for submitting data issues and the sub-section within it that this should go in is https://community.sports-interactive.com/bugtracker/football-manager-2024-early-access-bugs-tracker/database-and-research/england-efl-championship-league-1-and-league-2-data-issues/.

I am not able to replicate this, using the latest Data Update. I can also see no history of transfers submitted/approved that would cause this.

Is it possible you have other custom data files loaded alongside the SortItOutSI Data Update?

You have a whole host of ‘other’ updates, too; many of those are likely providing overlapping content.

In particular, wherever you've got two files (e.g. one from our Data Update and one from another creator) both trying to alter the rules/structure of a particular nation, at best you'll end up with them competing with each other and breaking the logical structure and at worst the inability to activate both files at once.

For this latter scenario, you will either be enabling one of the files (i.e. choosing which one to use), or if you leave them both enabled you will find that neither is activated and thus both files just sit there doing nothing.

My strong recommendation is to cleanse your ‘editor data’ folder of everything (create a backup folder and move everything in there), then install the Data Update afresh.

Thereafter, you can selectively choose which other files you use alongside it by moving them into the folder.

Sorry for the slow reply. This thread passed me by and I've been a bit busy in the last few days.

The answer to CA/PA values in the Data Update not reflecting what has been submitted/approved lies in the fact that those submitted/approved changes are not quite integrated in real-time, yet. Currently, the most recent version was produced around 12th / 13th September and so would have any and all CA/PA submissions that were approved by that point integrated into it.

Before that, these CA/PA submissions were integrated approximately monthly. This is mainly because there is no automated way for those submissions to be integrated and so it requires a lot of data scraping and manual work. Noting the date on the original question, at that time the most recent update would've reflected everything up to about 12th August.

However, there is work going on to integrate these in a more automated way. The intention being for there to be a new file produced on at least a daily basis, in line with the frequency that the overall Data Update gets produced. I can't say exactly how long it'll take - because I'm not the one doing the clever parts of that automation - but I have been involved in testing and the foundations are there. So it is genuinely, very close.

--

In terms of the recommended CA - I'm familiar with the variable in the PGE, but I am not sure what would cause that to alter as a result of the changes that the Data Update makes. As I'm sure you know, the individual attributes aren't changed by the Data Update (for the most part), only the CA/PA are exposed for submissions.

Obviously, that recommended CA is a perceived score based on some editor/game calculations and whilst it probably is predominantly based on their playing attributes, perhaps it is influenced by some other factors because, as you say, it would make no sense for the RCA to change if it is solely based on the playing attributes and those haven't changed.

Can you give me 2-3 specific examples? I'd also like to establish with some certainty that the ‘recommended CA’ has an in-game implication. I don't see why it would. I am not even sure that ‘recommended CA’ is a value that in any way translates into the game. I would expect attributes to change to trend towards a player's CA, as you have suggested, irrespective of what their ‘recommended CA’ is.

Just to confirm: it's not an error. The ‘Dynamic New Player’ data files were removed because they were no longer needed.

In reality, they should've been removed a while ago - they were needed when the ‘New Players’ were in a separate file from the ‘Changes’. Ever since they were consolidated into a single file, the ‘Dynamic Data’ files are all you need. These contain the dynamic ability randomisations for the newly-created players, too.

What we do need to do is update the associated Readme file.

Noted and I have replied in a Direct Message to continue the conversation.

From the view that I can see - I note that you have, since today, got a subscription to the Enhanced Data Update. I cannot see a record of a purchase made against the Premium Membership.

There are two different, paid product subscriptions available via the site - the Enhanced Data Update, which provides a version of the Data Update with additional features, including player ability updates and dynamic data, whilst the Premium Membership provides access to faster downloads versus having to use mirrors/download larger files in parts.

The reason they are separate is that there are very different costing profiles/activities associated with the upkeep of each of them.

If you believe you have made a payment for the second product (Premium Membership), then unfortunately I think only the Site Admin will be able to look into that. I appreciate that the distinction has not been very clear in all parts of the UI and that is something that is being worked on. In terms of seeing the distinction most clearly, if you go to your https://sortitoutsi.net/shop page, you will be able to see those two products and also be able to see the orders you have made.

I can see both of these players in my game. The most common reason for players not appearing is if the database setup isn't big enough. Are you able to confirm (a) which Data Update version you are using (and from which date) and (b) what settings you used to setup your game?

Not explicitly, I don't think. It's still a work-in-progress and resolving it will require identifying the images that are in a format that don't appear and replacing them with other images. I think it'll take a bit of time to work through those and identify them etc.

To be honest, there is no real harm in continuing to use the facepack because any that are in the right format will work and the ones that don't appear would otherwise just have the default silouhette. So my advice is to use the facepack regardless because you don't lose anything by using it.

It is worth noting that as an overall position, the contents of the facepack are nowhere near ‘all of the players’ yet. I think there are ~1,800 images in the facepack so far and that is about 10% (or perhaps less) than the total number of players that have been added to the Data Update. Of course, it is a work in progress and that number will grow.

No problem - only flagged up due to Data Update submissions and a newly-created player submission creating the other one.

@mons / @Lebohang Mokoena - I don't know the best way to report this but I believe the image associated with this player is of a different player with the same name.

The image we currently have is of this player: https://www.transfermarkt.com/aleksa-maras/profil/spieler/878340

However, this player is - in fact - the following player: https://www.transfermarkt.pl/aleksa-maras/profil/spieler/387088

For accuracy, I am confident we should remove this image from this player.

This is a confusing one - this player is the goalkeeper, who is 29 years old (in real-life) and plays for FK Drezga, as per https://www.transfermarkt.pl/aleksa-maras/profil/spieler/387088.

What confuses the situation is that the image associated with this player is not him - it belongs to another player of the same name.

This is why I have amended this player's transfer/contract status. The player who is pictured has been submitted as a newly-created player, which I have approved, under https://sortitoutsi.net/football-manager-data-update/new-person/2100050458.

I have also requested for the image to be removed from this player, because that can only confuse matters further. Finally, I've removed the TransferMarkt profile from the other player from this profile - as that may help keep things clear(er) for future submissions.

So, when you are setting up a new game and choosing the game start date in Brazil, you get options that are either the 2023 or 2024 season. To see the below options, you only need the SortItOutSI Data Update. It should look as below:

You should select one of the start dates for the 2024 season (those circled red). The file has been set up to reflect the real-life 2025 (i.e. current) season against that season. The 2023 season in-game reflects the real-life 2024 season.

For the nations that operate their league season throughout a single year, FM provides two ‘start years’. The later year will reflect the existing year. I appreciate it can be a bit awkward, but it's a symptom of the passing of time and at different parts of the year having to iterate the files in different ways.

Which Brazilian start date are you using? My assumption is the earlier one. In which case, this is ‘by design’.

For nations where there are two start dates, the earlier year reflects the ‘previous season’ and the later start date reflects the ‘latest season’. In the case of Brazil, if you start in the earlier start date, Santos are in the second tier. If you start in the later year, Santos are in the top tier.

I think the reason for positioning these nations like this is because it is understood that most of the community like to play the ‘latest start date’ (as it is closest to real life). Sports Interactive, themselves, also arrange those multi-year nations in a similar way - that is, you can effectively set up the divisions for two consecutive years to reflect promotions/relegations. Scandinavia is similar.

On a separate note, can I please ask that you do not tag the Site Administrator in every post. There is no need. There are a team of us who will do our best to help - we monitor the forums for posts as much as we are able.

I will also move this thread to the appropriate sub-forum as I think it is better-suited to be in the Data Update sub-forum. Finally, I noticed you posted the same query in another, unrelated thread - I will go ahead and delete that as this thread is all that is needed. Please do refrain from posting the same query multiple times in different threads - there is no need.

Just to circle back on this topic - I can confirm that, for those who have access to the Enhanced / Classic FM Data Update, the version built a few minutes ago (08:42 BST) contains an updated Non Dynamic Data file that includes the CA/PA submissions up to and including 13th September 2025. We are still finalising the automated rebuild, but hopefully this iteration will be a good step as it will factor in the many, many submissions made by the community, in particular during the transfer windows around Europe.

One small thing to note: the file in the current build is called ‘Classic FM - Non Dynamic Data 259.fmf’. Please be careful to ensure that you remove any previous iteration, which would be called ‘Classic FM - Non Dynamic Data.fmf’ (without a number). The regular/frequent build process will ensure the file is always given the same name, so this file admin is just a one-off consideration for this particular build.

Honestly, if you've held out until the transfer window closes then that is probably ‘the milestone’ to wait for. Of course, things will keep changing - in particular, non-playing staff can change - but playing personnel are now going to be fairly static.

We are still working on updating some of the league structures with promotions/relegations and things like the newly-created players continue to be added to on a regular basis - but there is always going to be something new added there, so no matter when you start, the next day something is going to be different. I'd say - just go for it! If you're ready to play, you're ready to play.

I have now uploaded a new version of the ‘Club Transfer Bans (Europe)’ file. This will be part of the Data Update from tomorrow.

It updates the transfer/registration bans in place across Europe, based on the latest FIFA data published on their Registration Bans website. It includes the removal of numerous bans where those clubs settled whatever disputes were in place (around 50 or so); and adds 13 clubs to the list who have recently received bans.

Notable clubs with their bans lifted include nine Turkish clubs, Lokomotiv Moscow, five Bulgarian clubs, two Polish clubs as well as a handful of clubs from other nations. Notable clubs who now have bans include AC Ajaccio, Boavista, Ordabasy Shymkent as well as a few others from around Europe.

The start date of the ban reflects when that club officially came under registration ban from FIFA (offset by two years) - so in some cases, clubs in-game will have their ban start after the first transfer window.

Apologies not to have picked this up sooner - I see you've opened a second thread (I'll close that, as no need for both).

It's a recurring payment, essentially a subscription, at a cost of £10 for a 12-month period (i.e. a year). From the point you make the payment, access is granted and you'll be able to continuously receive the latest version of the Data Update throughout that 12-month period.

Of course, you can cancel your subscription to prevent it from renewing any time prior to the end of the 12-month period. You can manage your content subscriptions via https://sortitoutsi.net/shop.

Further to the above, I've now amended the configuration of the file to offset the age limit by one year. It will be available in tomorrow's update, onwards. This brings it in-line with the real-life rule as documented by the Turkish Football Federation's documentation.

I have not amended the numbers of players as these appear to be correct in all of my tests across multiple years. I have also provided an equivalent update in the FM24 League Updates thread (https://sortitoutsi.net/comments/get/841625). It would be great if any further discussion could remain in that thread as it makes it easier for me to stay across it all.

…and to circle back to the above: I have now uploaded the new version of the Türkiye (League) file to the Data Update. This will appear from tomorrow's build onwards.

The correction in this file specifically alters the foreign player rule to adjust the age-limit by one year, in-line with the real-life rule for the Süper Lig. I have tested this in-game and the expected behaviour can be seen both in the first year and subsequent years.

Just to confirm - and I know others have also been keen to see this corrected: I am getting around to updating the Turkey (League) file to include the necessary correction.

I am just running simulation tests to make sure the in-game behaviour is as expected for all years.

Following that, I will be tackling a long-overdue update to the Club Transfer Bans file as there are some clubs who have formally had their bans lifted.

I am hoping that a (finally) correct Turkey (League) file will be part of tomorrow's update onwards.