I'm investigating some graphics glitches and occasional crashes in Geiger's Debugger for Arcana FastROM patch
, decided to disassemble it. There are countless 00->80 byte changes, and some functions were replaced with ASM jumps (with no evidence that the overwritten code was accounted for so far), and there's some minor subroutines that ORA 80 to the bank number every time the main loop is called.
Vast majority of the code though, seems to be constantly updating a range of RAM values. Wall of code procedes:Pastebin
The indented code is from a different trace than the rest.
My thing is, staring at all this, I'm tempted to gut it altogether and return to manually editing bank 00 to 80 for traced code rather than relying on a tool to "recognize" function calls and such. But, I'm not entirely sure how important this constantly-initializing code is. (I've also been putting it off because of the reverting process having patch conflicts)