Pokecrystal "Make" and GBC Save?

[ImperatorScientia]

I am new to learning how to hack with Pokecrystal disassembly. My question is how to apply changes in the code to an existing GBC game that has been created with the "make" command.

It seems every time "make" is executed, it creates an entirely NEW game that requires you to start a new Pokemon game when launched in a program like OpenEmu. However, this is obviously inefficient, since in order to test your changes, you would have to keep starting over. How do I apply the changes made in the .asm files to an existing saved game in order to test my changes? Am I doing something wrong in the repository?

 

[Anon822]

I am new to learning how to hack with Pokecrystal disassembly. My question is how to apply changes in the code to an existing GBC game that has been created with the "make" command.

It seems every time "make" is executed, it creates an entirely NEW game that requires you to start a new Pokemon game when launched in a program like OpenEmu. However, this is obviously inefficient, since in order to test your changes, you would have to keep starting over. How do I apply the changes made in the .asm files to an existing saved game in order to test my changes? Am I doing something wrong in the repository?

Compiling the disassembly always creates a new rom, there's no way to get around that.
However, your save data is stored in a separate save file which is not affected by the compilation. Unless you make code changes that affect how the game handles saving, you should be able to load a save file made with a previous build.

Perhaps your emulator doesn't load the save because it considers the rom to be different, in which case changing emulators might fix the issue.

 

[ImperatorScientia]

Compiling the disassembly always creates a new rom, there's no way to get around that.
However, your save data is stored in a separate save file which is not affected by the compilation. Unless you make code changes that affect how the game handles saving, you should be able to load a save file made with a previous build.

Perhaps your emulator doesn't load the save because it considers the rom to be different, in which case changing emulators might fix the issue.

That was it, thank you. OpenEmu is not suitable for rom hacking, evidently, but a switch to mGBA did the trick.