The code pictured is from the "State 2" mentioned in my first post.
I'm still not quite getting some of this, so thank you very much for taking the time and helping a beginner like me out:
I read through the code posted in the picture. The second half of the code (below the first "RTS") peaked my interest. Both routines involve three elements: D1, offset ffe173, and the conditional "Z" flag (one of 5 on/off flags that the 68k employs).
cmpi.b #-$2, $ffe173 - This command subtracts hex value 02 from the longword at offset ffe173
The next line of code checks the Z flag condition, and results in altering the value at D1.
This is repeated below, with significant variation.
I figured that this code might have something to do with deciding whether or not my attack was successful and then alters the enemies hit points. First, I decided to check the value of the longword at ffe173. I loaded up my hex editor, and checked the offset...
It doesn't have that many offsets...
Not even close...
Grr... So that's the first issue. Why is the PC running a program on an offset that doesn't exist?
ISSUE NUMBER TWO:
I wanted to know whether or not I was even looking in the right place, so I figured I would experiment a bit and debug a couple more save states. I loaded the game in the same spot as before and ran the debugger several times. I figured that irrelevant portions of the code would change, affecting graphics and sound, but the relevant game data would replicate itself.
I tried over and over again, but each save state is displaying drastically different code. This is sort of the same problem I had in the beginning, I guess. I don't understand how to find view the code I'm looking for -only how to view the most immediate lines of code. I'm having trouble coming up with the question, since I don't have the answer... Maybe someone with more experience will know what I mean?