I've taken my first baby steps towards contributing towards the Metallic Logos, specifically to try and enrich the visuals for the Lower Leagues in England.

The attached download (which will evolve over the coming days/weeks/months, significantly I hope) is intended for those that use the FM24 English Lower Leagues Database.

Thus far, I've created the competition and club logos for Levels 18-20 (attachment: L18-20.zip), which comprises of the following competitions:

Level 18:

Birmingham & District League Division Six

Bristol & District League Division Four

Central & South Norfolk League Division Two

Devon & Exeter League Division Six

Huddersfield & District Association League Division Five

Lancashire & Cheshire Amateur League Division A

Leicestershire County League Division Three

Lowestoft & District League Division One

Mid Sussex Football League Division Six

Mid-Essex League Division Two

North East Norfolk Football League Division Two

North Northumberland League

North West Norfolk League Division Two

Sevenoaks & District League Division Three
Stroud & District League Division Five North
Stroud & District League Division Five South

Yorkshire Amateur League Division Five

Level 19:

Central & South Norfolk League Division Three

Devon & Exeter League Division Seven

Lancashire & Cheshire Amateur League Division B

Lowestoft & District League Division Two

Mid-Essex League Division Three
Stroud & District League Division Six

Level 20:

Central & South Norfolk League Division Four

Devon & Exeter League Division Eight

Lancashire & Cheshire Amateur League Division C

Lowestoft & District League Division Three

Mid-Essex League Division Four

At this level, many of the competitions/clubs are not in the official FM 2024 database and therefore there is no method for me to upload the work into the central megapack. I am hoping posting this thread, here, is the right alternative thing for me to do. Love all of the work by the community here and just wanted to give something back.

The individual download for Level 20 of the pyramid can be found attached to this post. The first post of this thread contains the single attachment for all levels created thus far.

The next update will be for the entirety of Level 19 - consisting a total of six divisions, comprising 59 clubs.

The individual download for Level 19 of the pyramid can be found attached to this post. The first post of this thread contains the single attachment for all levels created thus far.

The next update will be for the entirety of Level 18 - consisting a total of 17 divisions, comprising 174 clubs.

This is great work

Indeed

The individual download for Level 18 of the pyramid can be found attached to this post. The first post of this thread contains the single attachment for all levels created thus far.

The next update will be for the entirety of Level 17 - consisting a total of 36 divisions, comprising a lot of clubs (I haven't counted yet).

Thank you for this, but they don't work in the latest update and database made by @DanFMDatabases, it seems the IDs all got changed for some reason, is there a workaround to this? cheers

I'll be honest, I haven't kept up with the latest releases from Dan - I don't own FM 2024 through Steam, so I am not subscribed to the database that way.

Suffice to say, if all of the team IDs have changed that would render everything I've done so far pretty redundant for use with the latest versions…FWIW, the version I have is the one currently available via https://www.fmscout.com/a-fm24-database-england-lower-leagues.html. I don't know how that stacks up against the versions on Steam. From a quick look, I see there have been two releases since then (well, four, but I suspect two meaningful ones with two bugfixes).

To answer your actual question: I cannot think of a simple workaround to the issue. It's effectively a question of re-mapping old IDs to new IDs. If I end up having no option but to get to the latest version of the Lower Leagues DB, I would probably just go back through the work I've done so far and re-map…but that's a big if because it's a lot of work and will be a bit soul-destroying to do it.

Hi there, it's strange, I decided to download the version of the link you posted so that I couldd see your logos but all IDs still changed, don't know what to try anymore :/

My assumption is that the team ID changes stem from the latest FM 24 database update. I suspect the Lower Leagues DB file is pivoting its changes due to that.

My ‘test game’ is on the previous version of the FM 24 DB. I suspect when I have time to start a new test game, I'll experience the same.

I'm not sure there is a solution besides changing the definitions in my logo packs. I'll take a look and report back on what I decide.

I've done a quick bit of testing - it's clear that the underlying, official FM database effectively ‘dictates’ which Unique IDs are assigned to the teams added by the Lower Leagues DB. There must be some logic that does this to enable compatibility - which is a good idea, in general.

The effect, of course, is that the latest FM 2024 database update (the latest 24.3 version) makes my work on logos to this point incompatible (or incorrect).

I have also validated that there is no ‘randomisation’ or ‘regeneration’ of the unique IDs assigned to teams between games (i.e. starting a new game, with the same combination of database/editor data results in the same unique IDs every time), just in case.

With all that in mind - I am going to have a go at re-mapping what I have done so far to the new unique IDs and, of course, any future logo packs will use the latest unique IDs.

Graphic megapacks works in FM because the UIDs for each entry are fixed, and do not differ whether it's in my career or someone in Antarctica because the config file will map the same graphic file to the respective game “file” in everyone's career.

UIDs for entries added using the editor are not fixed and will differ depending on the database version as well as the alphabetical order of any editor data files in place within the user's editor data folder. This means that the UID may even differ on the same user's system if different editor data files are used. This means that it's essentially pointless to create graphics for entries not in the default db because they will need to be re-mapped for every single possible file configuration, which is naturally impossible, or mapped by each user themselves, which may be beyond some users' technical knowledge and/or too time-consuming.

…and that is really useful to know; there was an element of that dynamic re-numbering that I suspected may be the case. Obviously, for myself personally, my test conditions retained the same combination of editor data, coupled with different baseline database versions.

I may pursue this as a personal project just because I enjoy the process and like enriching my own game - but knowing that there's really no guarantee around it working makes me re-consider whether it's worthwhile, overall.

That is the reason why we don't bother cutting people for the cut-out faces megapack who aren't in the default database, essentially.