Edit saves
A save is one file on a memory card: a 512-byte header that the BIOS card menu reads, then a byte-for-byte copy of the live game state. Editing a save means changing bytes of that copy and fixing one checksum. File layout: memory card save. State: persistent state. Field names: game records. Nothing on the disc holds a save.
Where the data is
Section titled “Where the data is”- File. One card block per file, named
BASLUS-00422BOF3plus a slot number00,01or02(file summary). - Header. File offsets 0 to 511: the
SCmagic, the title, the icon palette and three icon frames (layout). - Payload. 4,272 bytes at file offset
0x200, a copy of the RAM block that starts at0x801448D8. File offsetnof0x200or more is RAM address0x801446D8 + n. - Checksum. A 16-bit value at file offset
0x270, inside the payload (checksum).
What to change
Section titled “What to change”- Find the field in persistent state (party records, inventory, zenny, flags) and convert its RAM address to a file offset: subtract
0x801446D8. - Change the bytes. Every field keeps its width.
- Recompute the checksum with the checksum rule. Set the value at
0x270to 0, sum the payload, and store the low 16 bits of the sum at0x270, low byte first. - Write the file back to the card under the same name, or any name that follows the pattern above.
Limits and pitfalls
Section titled “Limits and pitfalls”- The checksum is the only check on load. The game tests no magic, title, icon, version or per-record value (validation). A wrong sum shows the card error and stops the load.
- A bad file still changes memory. The game copies the payload into live memory before it checks the sum. After a failed load, the bad bytes stay there until the next load or a new game
[inferred]. - File name. The load screen lists only names that start with
BASLUS-00422BOF3and end in 00, 01 or 02. Other names do not show. - File size. Keep the size that the game writes (file summary): the header, the payload and a zero pad.
- Header and icons. They affect only the BIOS menu. Whether the BIOS rejects a damaged
SCheader is[unknown]. - Unnamed bytes. Some payload bytes have no known meaning (open questions). Leave them as they are.
- Disc data is not in the save. Item rows, enemy stats and text come from the disc. To change them for every save, edit the disc data (items, characters, text).
Check in the game
Section titled “Check in the game”Put the card in the slot that matches the file name. Open the continue menu, check that the save is listed with the expected summary, load it and read the changed value on the status or inventory screen. A card error after a load means the checksum is wrong.
Related
Section titled “Related”- Memory card save: the file layout, icons, title and checksum.
- Persistent state: the block that the payload copies.
- Saving and loading: how the game writes, reads and validates a file.
- Game records: the names of the save fields.
- Edit characters and enemies: the starting table that a save does not follow.