Yeah, you can use an absolute path for the ROM too if you want. Otherwise the ROM should be in the engine folder. Keep in the mind that the engine is hardly stable, so you might not want to add it to a hack - I believe there are bugs with the OW expander. Otherwise make a patch before and after you apply so you can easily remove it should problems arise.
Should the rom be in the engine folder? Annd, oooooh... I have Devkitarm. But yeah, it's a bit complicated. I just want to apply the engine and ave it for later, since I want to tackle Assembly in the very near future. Ok, so all I do is configure it to the file path of DevKitArm, and run it?
You just modify the config.ini and then run the script. At the moment its fairly complicated for a newbie (you need to configure it to use DevKitARM), but unfortunately I don't really have the time to fix it. A GUI is really low down on my to-do list, as it just takes away time I could be spending on features and other projects.
Hello, Mr. Touched? I was just wondering about how exactly your hacked engine module for Emerald is to be applied in python, as I am unfamiliar with the software. :\ Also, will you ever develop a gui for the engine? Just curious about you as a programmer, is all.