Man, you really are great! How did you figure out so fast what all these addresses and stuff mean though? Did you have to painstakingly hunt down the variables in the ROM or do you have the ROM extract its files and code into a more convenient readable format(before this editor came out anyway!)?
When I first started hacking these games a year ago I basically knew nothing about how to rom hack, so what I did back then was just changing random parts of the rom file (using this program
) and seeing what it affected, eventually narrowing it down to the part of the rom that had stuff I wanted to edit. This was a very slow, painful process that I don't recommend to anyone, but it's what got me into hacking.
I gradually figured out better methods though, and nowadays what I do when I want to find something usually boils down to three steps:
1. Use DeSmuMe's RAM search feature to find certain variables in ram. For example if I wanted to find the player's STR I could search for numbers equal to the player's current STR, then equip different gear and search again for the new value, etc, until I've narrowed it down to just a couple values.
2. Once I know where a variable is in RAM I use No$gba Debugger to set a breakpoint on that address. This lets me find the code that writes/reads that variable, and then I can read the code to find out what it does. Usually this lets me find the location of a list of useful data without too much trouble.
3. Then I just play around with the data in the list to see what changing it at random affects, documenting what all the different values do. Once I've figured out a good chunk of it I can write a program that reads and edits this list.