You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to see if I could emulate breakpoint behavior in PyBoy using hooks, I found that setting the hook to one instruction ahead and changing PC to the instruction I actually wanted to hook was causing tick to never return.
While trying to see if I could emulate breakpoint behavior in PyBoy using hooks, I found that setting the hook to one instruction ahead and changing PC to the instruction I actually wanted to hook was causing tick to never return.
Specifically, in my disassembly of Medarot 3:
where Main.mainGameLoop is defined as:
If I instead opt to have my breakpoint at +4 (at the call instead), tick seems to properly return.
This Tick behavior seems to be unintended or undefined, but if it is intended, then I think it would be useful to have it documented.
The text was updated successfully, but these errors were encountered: