M.C - Comments

If a player is missing from the database, they can be added by any community member. Simply head over to https://sortitoutsi.net/football-manager-data-update/attributes to get started and follow the guidance from there.

The most likely reason is that you have additional custom database/editor data files that are conflicting. In fact, I can tell from the different divisions that the error message is mentioning that you must have some additional editor data files. It may be that whatever extra files you are using also move teams between divisions.

I have re-checked and the SortItOutSI Data Update allows the Czech leagues to be loaded when it is used in isolation. I personally made this file and tested it thoroughly before including it in the publicly-available Data Update.

I also ensured the divisional assignments of teams at least one more division down, to ensure compatibility with MasterIgor's populate Czechia expansion file (which enables the CFL/MSFL, the third tier).

I'm included a screenshot, below, which shows the successful ability to use the Czechia nation when the Data Update is enabled, just to assure you (and others) that it does, in fact, work.

If you need help identifying which files you are using, which are incompatible, please share a screenshot that shows the full list of files you have in the Editor Data Files list.

You are not doing anything wrong. Alas, those community-updated CA/PA changes have not yet been integrated with the Data Update. Unfortunately, there is no way to make use of them (yet).

It's on the to-do list, but there has been a necessity to prioritise other things in the period since the ability to submit them was introduced. The staff team will advise as soon as there is a timeline for these to be integrated - I would expect that, when they are integrated, there will be nothing more needed for anyone other than to ‘use the Data Update’ to make use of them.

Just to confirm: all of the contract extensions have been reflected as expected. However, the SortItOutSI Data Update offsets everything by two years to account for the time that has passed in real-life.

The goal of the Data Update is to provide the football ecosystem of real-world Summer 2025 at the point of in-game Summer 2023. In the same way a player who has made a transfer in Summer 2025 is at their new team, in-game, in Summer 2023, so too are promotions/relegations done to reflect the real-world scenario.

To tackle the issue of that relative offset, the Data Update also offsets player DOBs and contract lengths by two years. So a player will be the age they are in real-life in Summer 2025 in-game in Summer 2023. A player with ‘one year left’ on their contract in real-life in Summer 2025 (i.e. a contract until Summer 2026), will have ‘one year left’ on their contract in-game in Summer 2023 (i.e. contract runs until Summer 2024).

Unfortunately, this is not as simple as it may seem.

This website maintains a searchable database of Person records from previous versions of the game - which is why Collins Atule is discoverable at all. However, he doesn't exist in the FM 24 database and so there is no way to recreate him in the ‘original form’. The only way to have him exist in FM 24 is to create him as a new player - as you say, this is effectively done, as a result of our community's submissions system. Which is the best/only solution, unfortunately.

There is a plan to establish a facepack for newly-added players - it is, however, a lot of work and it requires some planning. The underlying planning (to ensure UIDs remain static) has been done.

This is an odd one - because this is appearing as though there are four instances (which all come up when you search for the player) in the original database. However, the original database only has one.

I will flag this with the site owner, in case this is a bug that is being presented through the website only as it may require a different/specific fix.

There should be no reason that the game doesn't, fundamentally, finish loading.

It is true that this particular step will take noticeably-longer than if you are running a Vanilla version. How much longer is hard to articulate - there's a lot of variability depending on PC/laptop specifications and so on.

As an example, on my PC, using a Vanilla database, that step takes about 2-3 seconds (i.e. it is pretty immediate). With the Data Update installed, that same step can take approximately 45-60 seconds - and it spends almost all of that time with the ‘progress bar’ showing at the end. Fundamentally, during this step, the game is reading all of the database changes and processing them. There are a lot of database changes in the update.

If I then enable custom playable nations, that I personally also use, that goes up to 60+ seconds. Essentially, the more custom data you're loading, the longer it'll take. Whether the ratio of ‘Vanilla’ to ‘Data Update’ times are the same for different specification systems, I have no idea.

The initial troubleshooting steps to take are:

1. Ensure the Data Update is installed correctly.

2. Check that only the Data Update is installed/enabled. This is about benchmarking to see if it is strictly the Data Update, or some other files, that are introducing the delays.

3. Whilst it is ‘Loading Game Database’, open up Task Manager and check the status of Football Manager 2024 on the Processes tab. If the CPU/Memory utilisation is actively fluctuating and the process does not show ‘Not Responding’, then the reality is that it is still loading and processing the changes. If the game genuinely stops processing, you'll find it shows ‘Not Responding’ and its consumption of CPU/Memory is likely to drop right down.

Over and above, I'd recommend starting a game without any Editor Data files enabled and record the length of time it takes. This gives you a good benchmark for your system. Then try again with the Data Update (and only the Data Update) enabled and record that length of time. It should finish, but it also should take longer. Ignore the distance the ‘progress’ bar has made - it'll go to the end and then do most of the work. It appearing to be at the end and not completing is not, in fact, a sign that something isn't working. It's just how the game's UI presents this step.

For anyone who believes something isn't working, it's really useful to know (1) specifics of what you are enabling in the ‘Editor Data Files' list, (2) the length of time you have left it on that screen and (3) the outcomes of the core troubleshooting, in particular the status observed of the process under Task Manager.

Honestly, I don't think it's that much of an unknown. I think what FIFA publish is pretty robust - they publish the start date and clearly indicate the number of transfer windows. It's fairly official and, I would say, an authoritative source.

At this stage, I would say that Sakaryaspor could be an ‘error’ on the site, or it maybe isn't. They had three infractions, two of which were those ‘transactional’ ones, with one that stipulated a three-window ban. The two transactional ones have been lifted - the third one still remains published.

Unfortunately, I don't know what SI have historically used as their source - but we do know which clubs were configured with a ban in FM 24. So I could do a bit of cross-checking. However, once bans have completed, they no longer appear on the FIFA site - so I can't consult the history, as such.

These two clubs - as representative examples - raise an interesting point.

When I did the transfer bans file, it was based on the official FIFA Registration Bans database (https://knowledge.fifa.com/registration-bans). It's fully searchable.

FIFA maintains this list as a method to formally publish all clubs who are under some level of contractual registration embargo. They list clubs in two ways - either as having a ban ‘until lifted’ or for a pre-determined number of registration periods (transfer windows, effectively). The list of clubs on that page each have published outcomes of judicial/court hearings that result in their clubs being handed these punishments - that is, this is not speculative, but based on sporting law.

Typically, clubs who have been found guilty of transactional/minor misdemeanours have an ‘until lifted’ status. This typically signifies they have to pay off a remaining, small debt - or some other fine - and then they can resume registration activity as normal. Because of this, no clubs with this status only were included in the transfer bans file.

Clubs who have been found guilty of more serious misdemeanours (most often, it is due to historical transfer dealings, such as owing the selling club instalments or other fees, which have been escalated to the formal courts and resulted in this legal decision) are the ones that get pre-determined bans for a set number of windows. It is these ones that I have included in the file, because they are unlikely to be lifted sooner.

Strictly speaking, a ‘registration ban’ prevents the registration of new players from being registered as contracted to the club. It isn't, strictly, the same as a ban on acquiring the rights of a player (i.e. a transfer). But in practice, the two are pretty much equivalent. Indeed, news outlets interchange the terms - before committing to making the file, I cross-checked a variety of the clubs on the FIFA list for news of their ‘transfer’ or ‘registration’ bans and found plenty of official, local news sources reporting ‘transfer bans’ of the clubs listed (again, most of these official news sources use the FIFA Registration Bans list as their source). The words on the FIFA site itself mention this is about indicating which clubs are ineligible to sign new players. Perhaps more importantly, in the context of Football Manager, there is no method to specify a registration ban on an individual club for a set period of registration windows.

With reference to the specific examples called out: formally, both Sakaryaspor and Ümraniyespor are listed on this site with bans for pre-determined numbers of registration periods. Sakaryaspor's registration ban came into effect on 28/02/2025, for 3 registration periods. Ümraniyespor's came into effect on 07/04/2025, for 3 registration periods. These clubs may be signing players in the transfer market, but until FIFA formally acknowledge those registration bans as being lifted (by their disappearance from this published list), I would not expect either club to be allowed to register those new players for any formal, competitive competition.

I have actually been asked about the Sakaryaspor one, about a week ago. This was following the news that the ban was ‘expected’ to be lifted - Sakaryaspor had been found guilty of three misdemeanours, two of which they had satisfactorily resolved. I appreciate they - as a club - may expect to resolve the third, but until it is official I would prefer to be guided by official sources.

If the other staff/community here believe I have fundamentally misinterpreted the content of the FIFA Registration Bans list, I am happy to entirely withdraw the file from being part of the Data Update. I am not ‘attached’ to the data in any way - I am keen for this to be as accurate as possible.

That’s as a result of a submission that should have been rejected, but has been approved. Not intended. I will sort it out and revert him back to the ‘last reasonable’ submission that was made.

@Marck - for your (and other people's) awareness: I've also now checked and removed the less-complete entry for Ronaldo Luis Nazario. There was one that didn't have his history, so I took that as the ‘less complete’ instance.

I have set this instance of Ronaldo as Retired as there is a duplicate entry in the FM 24.3 database (UID of other entry = 707715).

Comparing the two records, UID 707715 is the more complete entry - including his full playing history.

Thanks for pointing this one out - sorted!

If you use the +2 years file, then in your game, players will be the age in 2024 that they would be in real-life in 2026. I'm answering this way because I'm not sure what the benchmark we're comparing to when we say 3 years ‘older’.

The player ages changes are done by altering the players' DOBs in the database. So their age in-game will always be relative to the in-game date.

It is worth noting that the +2 years file is one of many files in the Data Update, so it can be enabled/disabled in isolation.

If your goal is to have Summer 2024 in-game reflect Summer 2025 in real-life, you'd want the legacy +1 years file. Which you could get a copy of by going to https://sortitoutsi.net/football-manager-data-update/releases and choosing one of the instances of the update from May (I'd recommend just getting the oldest one).

Moved by staff into Editor sub-forum - created as new topic.

@bilidionicar - this will hopefully ensure someone can provide support.

That's really helpful, thanks - I've managed to get those translated and so the rules are crystal clear. I'll get those amended ASAP and reupload a new file.

Acknowledging this - I have fed this back to the staff member who has done the initial iteration of Portugal to this point. As the Boavista situation has been quite dynamic, I am sure this will get updated in the file soon enough.

Just to confirm - I have just uploaded a revised file for Turkey; this should be available in tomorrow's update. It includes the squad registration rules to the best degree of detail I could implement them (it includes the Super Lig, 1. Lig & 3. Lig changes, both in terms of foreign player quotas and player age quotas, including progression over the first two in-game years for the Super Lig).

@Tuna457 - just a courtesy update. Firstly, to confirm, the Super Cup format (that I mentioned in my previous post) is something I had already taken care of. So that is in the current version.

Additionally, I have been working on the Turkish squad registration rules. I think I have got this right, certainly for the top two divisions, but I wanted to check:

Süper Lig: for the first in-game season (i.e. 2025/26), there is a total squad size of 28 players. Of those, 14 are permitted to be foreign players, although two of those 14 must be under-23. There are no restrictions around the use of foreign players in the matchday squad. From the second season (i.e. 2026/27) onwards, the same rules apply, however at least 4 of the 14 foreign players must be under-23.

TFF 1. Lig: there is a total squad size of 26 players. Of those, 8 are permitted to be foreign players. In the matchday squad, there can only be 6 foreign players on the pitch at any time.

TFF 3. Lig: there is a total squad size of 25 players. Of those, a maximum of 5 can be 25 years or older.

I have just uploaded the revised file into the Data Update - it should be part of tomorrow's scheduled release onwards.

I currently have left the TFF 2. Lig squad rules as they are because I could not find any clear sources around these. My understanding is that in the TFF 3. Lig there has been quite a radical rule change around squad registration rules (https://fifpro.org/en/who-we-are/fifpro-members/fifpro-europe/hundreds-of-players-in-turkiye-protest-rule-changes), but the article only refers to some of the changes in detail. If you, or anyone else, is able to direct me to a source for these rules, I will happily reflect them into the Data Update - what I have included for now is the best representation I could from clear source material.

I'm just trying to finalise the Turkish league updates, at the moment; if no other staff member has processed it in the next 30 minutes, I'll do it.

That is my take on it - although I don’t know how ‘unpredictable’ the start would be, as the game will simulate those seasons you skip through with the future start date.

My personal preference - which I guess is shared by those that use this site’s Data Update - is simply to accept the offset 2023 start date, look past it and play the game with everything else reflecting real-life as it is now.

Yeah, so I saw that previous post and I actually looked into it - though I didn't come back and reply. That situation is slightly different, because it is two entries in the base-game database as far as I can tell. Of course, it can be resolved - I just need to look up which one is the ‘original’ (with the completely filled-out record/history) and then set the other to not exist. Also, anyone in the community could do this.

I've just taken care of this one - as one of them had ended up assigned to the youth team (and one to the main club) they were a bit tricky to spot, I suspect (on the site - of course it would obvious in-game).

When the next update is processed and rolled out this duplicate should be gone. Thanks for pointing it out.

I believe the FM RTE website has some files that enable start dates significantly into the future. A link to the file(s) that can allow you to start in the future: https://www.fmrte.com/files/file/157-custom-start-date-for-fm24-start-in-june-to-april-up-to-10-years-aheadread-the-link-in-the-description-for-full-details/

Whilst they are compatible with transfer updates (i.e. whatever status squads/staff are in at game start will be respected), the game will simulate the ‘future seasons’ as part of its initial creation - as such, it is impossible to specify the real-world 2025/26 pyramid structure and have a start date of summer 2025 that guarantees teams to be in the divisions they should be (assuming your goal is to have teams in the right divisions, as in real-life for the upcoming season). So there is a trade-off to make - it just comes down to which trade-off you're willing to make, I suppose.

The SortItOutSI Data Update tackles the challenge by, effectively, cycling the game world forward the two years (from summer 2023 to summer 2025) in terms of transfers, contracts, (most, soon to be all) promotions/relegations, transfer bans and player ages. So whilst the in-game date will show July 2023, the game world will reflect July 2025.

Whilst this isn’t strictly the right thread/forum for this, let’s see if we can’t help get you up and running all the same.

Firstly, from our perspective, the Czechia nation has been updated for 2025/26 and works as far as we can tell. Can you provide some specifics? Are you using the SortItOutSI Data Update? Do you have other files? When you say it’s ’not working’ - in what way does it not work?

Please feel free to attach screenshots, so we can get an appreciation of how this is failing for you and try and help.

As the person that did the recent Turkey update, I can advise that the foreign rules and the new Super Cup format are two outstanding tasks that I intend to correct. To be honest, I made notes about these but whilst doing the initial file, I simply managed to forget. I would be hopeful of circling back around to it and producing an updated version within the next week or so.

If you wish to seek a refund, there is a dedicated thread for requesting those. So if you ultimately choose to request one, please go to https://sortitoutsi.net/content/57415/all-issues-with-premium-membership-post-here.

Yes, Lyon were successful in their appeal and had their relegation overturned. Reims were, ultimately, relegated instead.

@ardabaranq - unfortunately, as this upload includes work from other authors, who have now indicated that their permission was not sought, I think there is no option but to withdraw the download. I am obliged to respect the position of the original authors.

If you had an alternative version that does not include the data of other modders, then you could upload that as a replacement - though I don’t believe that is the case.

I will close this thread to avoid further comments/arguing. Permission should always be sought when making use of someone else’s work in your own release…and if they don’t give it, that has to be respected/accepted.

There is a lot of overlap. Exactly how much, I’m not sure - I don’t use DaveIncid’s pack, so not intimately familiar with it.

The Data Update on this site consists of a single ‘main’ file, which is the Changes.fmf, that contains all of the transfer updates, contract updates as well as new players.

The majority of the other files are individual nation files - these typically only contain the promotions/relegations of that nation - and in some cases, new league rules to update the structure of that nation’s pyramid. These should all end with the suffix: (League).

The files that are neither of these things are a variety of targeted alterations - often, it’s obvious from the filename what they are.

Ah, yes - and now you mention it, that is my fault as I did name mine using the Türkiye spelling. I didn't think through the consequence of renaming the file. In general, we avoid changing the filenames exactly for this reason - as typically copying the new files over replaces everything.

Glad you are up and running again.

Just to confirm: it is now possible (and has been for some time) to create completely new players to be part of the SortItOutSI Data Update.

The best jump-off point to do this is from https://sortitoutsi.net/football-manager-data-update/attributes - which will guide you to search for the club and then, from the club's page, use the ‘Add New Youth Player’ button. This will take you to a form allowing you to enter all the necessary details. Once submitted, this will then be moderated and - if approved - gets automatically integrated into the Data Update thereafter.