So on the last couple of weeks I've been working on several cheat methods (RAM hacking, ROM hacking and Save Data Editing) but one thing I can't figure out are pointers!
Sure dumping a few times the RAM and finding then changing a static value is extremely easy to do, but finding the address that writes on that dynamic address is the real challenge.
Now, obviously pointers are extremely easy to find when running (or reading memory live) a game on an emulator like Citra, but the problem is that not all games are supported on this moment. I have found several pointers on FE:A with Citra and Cheat Engine and it was extremely easy!
The question is, how can I find pointers while dumping memory with ntr debugger?
Is there any way I can read live the ram memory of the 3ds? If so, that would be extremely helpful on finding pointers.
Another thing I've found is that it seems that Gateway can help in finding pointers with some PC software and dumping ram, but it seems that it uses very different memory regions than that of ntr debugger. (Physical or virtual memory, perhaps?!)
I've been searching around and really haven't found any way to find pointers with memory dumps so I'm wondering what people here say/know about it.
Sure dumping a few times the RAM and finding then changing a static value is extremely easy to do, but finding the address that writes on that dynamic address is the real challenge.
Now, obviously pointers are extremely easy to find when running (or reading memory live) a game on an emulator like Citra, but the problem is that not all games are supported on this moment. I have found several pointers on FE:A with Citra and Cheat Engine and it was extremely easy!
The question is, how can I find pointers while dumping memory with ntr debugger?
Is there any way I can read live the ram memory of the 3ds? If so, that would be extremely helpful on finding pointers.
Another thing I've found is that it seems that Gateway can help in finding pointers with some PC software and dumping ram, but it seems that it uses very different memory regions than that of ntr debugger. (Physical or virtual memory, perhaps?!)
I've been searching around and really haven't found any way to find pointers with memory dumps so I'm wondering what people here say/know about it.