I am new to assembly hacking and have had success with creating game genie codes with SNES9x Gieger and some simple NES games. I do understand basic assembly such as storing, loading, comparing and branching basics. My trouble is as a newbie, is how do you keep track of a routine that your in? If I find x player movement RAM address for example and set a break point, and my goal is to walk thru walls, or something bit more complicated, how should I go about of knowing if i am in correct routine? Example, if i want to do a walk thru walls code, would my RAM address appear somewhere near the routine? I have done some walk thru walls on SNES, but damn, so many routines, its hard to know if its relevant and instead of changing the branches one at a time and hoping for expected result, is there a better methodology? A simple act of walking into a wall then stopping a trace can produce thousands of lines of code! I do understand often times there will be repeat of routines you can keep going past, but what do you guys look for and how do you keep track if the routine is correct or not?
July 14, 2020, 03:18:29 pm - (Auto Merged - Double Posts are not allowed before 7 days.)
So with SNES 9x I can trace fine, but does FCEUX have a trace log that can output to a file inside of in the console?