Kodewerx

The idea is that the save file reads and writes only the addresses that matter. in other-words, the routines that make a save file in the CPU should point to all addresses that store permanent data. If you could collect all the methods used to find these routines and read which addresses they read from and write to in RAM, you would have a good selection of codes that could be saved.

if a program or debugger exists like this, let me know what it is and how it works. If not, it might be a good tool!

If you're the mastersord I think of, long time no see !

About the sav files I'm not quite sure. However as each game is different (some use plain addresses, other pointers), I believe each programmer is free to do whatever he wants, meaning there might not be universal routines that would read/save the .sav file.

But some (most? all?) games just copy/paste a block of RAM into the .sav file. By that I mean that if you look at a .sav file (with an hex editor), then make a search in RAM for its values, you'll have good chances to find 'permanent' addresses right away. That's actually what I did with Geometry Wars (I looked into the .sav file that had the wii level unlocked, compared it with a file that didn't have it unlocked to find the 'unlock' bit, then searched in RAM for the .sav files values, found what was the actual address of the unlock bit in ram. Then I just had to put a bpr on it, and I was able to make some code to unlock it).

One and the same! The GBA scene cooled down last year, so i found myself with too much free time. I got a DS for christmas and thought "maybe there's a hardware solution for game hacking"

It's good to speak to you again! If it's porting a straight, full block all the time, then yeah, that would work. I wonder why I never tried that with GBA stuff?