• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Our weekly protagonist poll is now up! Vote for your favorite Trading Card Game 2 protagonist in the poll by clicking here.
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

Save file structure for Gen 3 and an unknown 4-byte value

  • 3
    Posts
    3
    Years
    • Seen Nov 12, 2021
    Bulbapedia has a page on the save structure for Gen 3, including the 4KB save sections that each include data, a checksum, an ID, and an index. The thing is, the offset for the section ID is at 0xFF6, and is 2 bytes long. The offset for the checksum is at 0xFFC, and is 4 bytes long. That means there are 4 bytes between the end of the section ID and the start of the checksum, and, it appears in my battery file which I have inspected in a hex editor, these 4 bytes hold
    Code:
    25 20 01 08
    in each of the 28 sections (14 sections per each of 2 save blocks). I can't find any documentation on what this is. Does anyone know what these bytes or for or what that value means?
    For context, I'm working on a Fire Red rom hack with well over 420 species (the maximum capacity of the PC), and was thinking of making a utility that can import/export boxes from a save file so a player can kind of hold a living dex without needing to start multiple save files and/or trade many Pokemon individually.
     
    Bulbapedia has a page on the save structure for Gen 3, including the 4KB save sections that each include data, a checksum, an ID, and an index. The thing is, the offset for the section ID is at 0xFF6, and is 2 bytes long. The offset for the checksum is at 0xFFC, and is 4 bytes long. That means there are 4 bytes between the end of the section ID and the start of the checksum, and, it appears in my battery file which I have inspected in a hex editor, these 4 bytes hold
    Code:
    25 20 01 08
    in each of the 28 sections (14 sections per each of 2 save blocks). I can't find any documentation on what this is. Does anyone know what these bytes or for or what that value means?
    For context, I'm working on a Fire Red rom hack with well over 420 species (the maximum capacity of the PC), and was thinking of making a utility that can import/export boxes from a save file so a player can kind of hold a living dex without needing to start multiple save files and/or trade many Pokemon individually.

    I'm guessing it's this value.
     
    Thanks, Anon. I couldn't find documentation anywhere on it. So it looks like it's just a magic number used for checking integrity, and it's the same across all the Gen 3 main entry games.
     
    Back
    Top