If I've forgotten anything, then just let me know and I can post them. There are some things which I cannot answer, but it doesn't hurt to ask. I should be able to help out if anything is missing, spo just post here. I hope this is useful - it's all off the top of my head so there might be things missing or slightly innaccurate. At the start of index.dat, there are 2 (unused) LONGs which you'll need to read in too. The table IDs can be ignored as they are used internally when loading/saving the database files. The table versions can be ignored, this is when we add a field during development and don't want to break old version saved games. The ID for the first one, instead of being 0, should be the number of club teams, and from there on it's incremented as normal. nat_club.dat is an exception, as this contains CLUBS records for national teams. Record IDs are generally the same as the index in the corresponding table. The others are simpler, because there is only one type of structure within the file, so all the offsets are 0.

Then there's the next 4 bytes which is the count of nonplayers, and so on. The second 4 bytes is the count of staff records, and then the offset is this * sizeof( STAFF ). In the case of staff.dat, the first 4 bytes is the count of overall staff, and the first offset is 0. Each of these correspond to one of the structures inside database_types.h, except staff.dat which contains staff, then nonplayer, then player data. It contains a quick overview of each of the *.dat files used in the game. This is the index to the database, and you'll need to read/write this when changing the data. To round things off, you'll need the format of index.dat. The language structure(s) will follow too. If you add/delete a team, nation, comp, award, city, state or injury then you'll need to update (reproduce) these files. In additions to what is defined in these files, the language files (*.lng in the data/database folder) are also part of the database.

Graeme kelly savegame editor