Guides/Tips Hexer's Workshop: It's all about Hex (FMM21 and beyond)

[alfian]

6 minutes ago, jaymarvels said:

In FMM17, no. In FMM24, yes 

i mean, how to change the kit color (in match field) fmm 2024 using the hex edit method, someone said it was after the club nationality code, but after i tried, i didn't find the color code combination there.

[freezedriedpop]

Has anyone made any attempts to apply this binary reading/writing to the full game as well? Or are the .dat files for that completely different?

Does anyone have any idea what tool/library has been used to create each file? I thought perhaps there might be some artefacts left behind that make indicate that.

[jaymarvels]

1 hour ago, freezedriedpop said:

Has anyone made any attempts to apply this binary reading/writing to the full game as well? Or are the .dat files for that completely different?

Does anyone have any idea what tool/library has been used to create each file? I thought perhaps there might be some artefacts left behind that make indicate that.

I have read in all (most) base data files.

It's all in house custom code that creates each file.

[freezedriedpop]

Damn. I'd love to try and keep FM25 alive forever as a sort of "Classic FM" but I feel like being able to edit the .dat's will be alot better than trying to do it through the pre game editor.

[freezedriedpop]

@jaymarvels Do you know if there's anything in the .dat files which specifies which game it can be used with? I imagine if something like that could be edited then new data files could be used with old game version.

Although I imagine finding that within the binary would be very tricky.

[jaymarvels]

1 hour ago, freezedriedpop said:

@jaymarvels Do you know if there's anything in the .dat files which specifies which game it can be used with? I imagine if something like that could be edited then new data files could be used with old game version.

Although I imagine finding that within the binary would be very tricky.

No, base data files aren't transferable for obvious reasons 

[freezedriedpop]

I realise they're not transferrable. My question was more about the mechanism that makes them not transferrable. If there's something in the .dat that simply says min:2400 or something and that could be edited the same way as anything else in the .dats

[jaymarvels]

1 minute ago, freezedriedpop said:

I realise they're not transferrable. My question was more about the mechanism that makes them not transferrable. If there's something in the .dat that simply says min:2400 or something and that could be edited the same way as anything else in the .dats

Different game each year so different dats that's why things like editors, save game viewers etc take time after each game and update.

[freezedriedpop]

Sorry we seem to be talking past each other. Or maybe i'm just misunderstanding you, sorry if I am.

I realise they are different .dat files. Presumably the game must have some way of knowing whether or not it can use a particular .dat when you put it in the appropriate folder.

I was theorising that this would be inside the .dat somewhere e.g. an integer specifying a minimum version number. In which case, it might be possible to modify this version number and allow a different game to open that .dat.

Either i'm completely barking up the wrong tree and there's another way for the game to know which dat's it can and can't use.

Or people have tried to look for such a thing and can't find it.

Or it's impossible / very difficult to look for it because we've no idea what it might look like.

Or nobody has ever tried.

But simply saying they're different .dat's seems to miss the point.

It's possible my question is just incredibly stupid and makes no sense, apologies if that's the case.

[jaymarvels]

7 minutes ago, freezedriedpop said:

Sorry we seem to be talking past each other. Or maybe i'm just misunderstanding you, sorry if I am.

I realise they are different .dat files. Presumably the game must have some way of knowing whether or not it can use a particular .dat when you put it in the appropriate folder.

I was theorising that this would be inside the .dat somewhere e.g. an integer specifying a minimum version number. In which case, it might be possible to modify this version number and allow a different game to open that .dat.

Either i'm completely barking up the wrong tree and there's another way for the game to know which dat's it can and can't use.

Or people have tried to look for such a thing and can't find it.

Or it's impossible / very difficult to look for it because we've no idea what it might look like.

Or nobody has ever tried.

But simply saying they're different .dat's seems to miss the point.

It's possible my question is just incredibly stupid and makes no sense, apologies if that's the case.

There is no "indicator" it's built purely for a specific game version and reflects classic object orientated programming. The OOP is what defines it.  Over the years there may have been instances where an object hasn't changed, but these would still be incompatible due to internal workings and indexing .