Will add the search feature soon, haven't been working on the debugger recently. Also, I will be adding an in-line debugging option. In order to keep it from lagging the GPU as harshly, it will have to be 1~2 lines. Too much data / looping will cause the console to lag the game really badly...
Possible in-line debugger menu setup:
-- Inline Debugger Setup --
Main Menu (Memory Browser, Codes, Patches, Search, Return):
MM> M C P S R
Memory Browser (Address, Data):
MB> XXXXXXXX XXXXXXXX
Memory Editor (Address, Data):
ME> XXXXXXXX XXXXXXXX
Go To (Address):
GT> XXXXXXXX
Codes (code_name, On|Off):
CD> xxxxxxxxxxxxxxx {O|F}
Patches (Address, Data, Activate|Deactivate):
PT> XXXXXXXX XXXXXXXX {A|D}
Search (Start, Stop, Value, Bits):
SR> XXXXXXXX XXXXXXXX XXXXXXXX XX
Controller inputs will be the same as the full debugger, the only difference is instead of it exiting the game loop it will run inline with the game. So you can watch a value change when it happens (for instance bullet count, or health amount, etc.)
Possible in-line debugger menu setup:
-- Inline Debugger Setup --
Main Menu (Memory Browser, Codes, Patches, Search, Return):
MM> M C P S R
Memory Browser (Address, Data):
MB> XXXXXXXX XXXXXXXX
Memory Editor (Address, Data):
ME> XXXXXXXX XXXXXXXX
Go To (Address):
GT> XXXXXXXX
Codes (code_name, On|Off):
CD> xxxxxxxxxxxxxxx {O|F}
Patches (Address, Data, Activate|Deactivate):
PT> XXXXXXXX XXXXXXXX {A|D}
Search (Start, Stop, Value, Bits):
SR> XXXXXXXX XXXXXXXX XXXXXXXX XX
Controller inputs will be the same as the full debugger, the only difference is instead of it exiting the game loop it will run inline with the game. So you can watch a value change when it happens (for instance bullet count, or health amount, etc.)



It's an easy thing to implement.
Comment