Been a while since I posted here.

I can't tell you how to do it directly, but there is a method.

If you have FCEUX, open up the RAM viewer, and save your state just before a boomboom fight. Choose another save state slot, and, just before it jumps, save state in a new slot. Then, as the boomboom jumps, keep your eye on the RAM values and see if any of them correlate. If you see one that does, you can freeze this value to see if his behavior has changed. If it has, then there is code writing to this value. If there isn't any change, unfreeze that value and try again, loading the state each time he jumps. (You can do the same thing for # of hits- look for changing values, likely to be 02, then 01, then 00)

After you found the byte in RAM that correlates to jump height (or # of hits) then you can then trace the code. Open up the Debugger and set a write breakpoint to the value you found in RAM. (To avoid confusion, just load state to right before you expect the value to change) and there would be your likely point of code to modify. For # of hits, you probably can't just change the amount, because each phase has a certain style, who knows what'll happen if you just go above that set value.

Been a while since I just opened this up, I'm afraid I can't be more specific than that.

____________________