So the "crash" is actually the game closing itself. It has a check written in it to find out if a debugger has been attached. This is the case when you use the windows debugger. Cheat engine also has two other debuggers you can use. The VEH or Kernel debugger. The VEH debugger is the easiest one to use, but it comes with certain limitations. Its purpose is to allow you to debug and hide the fact you're debugging from the game. There is a certain region of memory that is called the "stack" and maybe other important areas that cannot be debugged with the VEH debugger or else it'll be detected. The other option, the kernel debugger, is great since the game shouldn't have permission to detect it and it can debug everything I think. You can use this without a problem on a 32-bit OS. If you want to use it on a 64 bit OS, you'll need to use dbvm and hope your whole computer doesn't crash. You can google and look up more specific details about this or anything I may be wrong about.Venator wrote: ↑Mon Sep 02, 2019 11:02 pmI was going to see if I could find out what writes to either zeni or TP medals, but my game seems to absolutely hate having the debugger attached. I get as far as locating read values for either one, and it attaches, but as soon as I try to load a buy menu, inventory, etc., the game crashes. Any help would be appreciated, even if it's just "Do X before attaching the debugger."
Certain cracked versions of the executable get unpacked and remove the debug checker. I notice this a lot in CODEX cracks. You could find one that has the check removed and is the exact same version of the official one and replace it so you can use the windows debugger.