Reading code
Disassembly
Section titled “Disassembly”Ctrl+D on anything with an address opens it as code. View > New disassembly opens a blank one, then Ctrl+G to go somewhere.
Addresses show as game.exe+0x1A2B3C where they can, and names from your address list and plugins show up too.
F2 replaces an instruction. Type the new one and it’s patched in right away. Good for quick experiments. Write a tweak when you want to keep it.
Breakpoints
Section titled “Breakpoints”| Key | Does |
|---|---|
F9 |
Toggle a breakpoint |
Shift+F9 |
Toggle a hardware breakpoint |
Ctrl+F9 |
Enable or disable one |
Ctrl+Shift+F9 |
Delete them all |
A normal breakpoint writes an int3 into the code. A hardware one uses a debug register instead and leaves the code alone, for games that check their own code. There are only four of those.
In Breakpoints you choose what each one stops. Just its thread, every game thread, or nothing.
When it stops
Section titled “When it stops”The thread shows up in Debug > Threads, and Registers shows what it had. You can change them.
| Key | Does |
|---|---|
F5 |
Continue |
F11 |
Step into |
F10 |
Step over |
Ctrl+Shift+F10 |
Set the next instruction |
Setting the next instruction jumps without running anything in between. The stack stays as it was, so jumping out of a function usually crashes.
Crashes stop here too, so you can look around before the game goes down.
Signatures
Section titled “Signatures”Pick Scans in the Names panel to see every signature that’s been scanned and what each one found. Rescan all checks them again, which is the quickest way to see what broke after a game update.
Diagnostics > Hooks and Diagnostics > Claims show who’s changed what code. Useful when two mods fight over the same function.
Made with ♥ by Asgard
