Easy and Crude Walk Through Walls guide

[Helder]

Just in case anyone tries to do traces on the SNES9x Debugger you need to press * key to turn on and off the tracing feature. Try to activate tracing at a break or right before it occurs since SNES9X makes small 4Mb files and if left on for too long you will have a bunch to sift through.

[Professor-X]

I recently came up with a new routine that will allow you to see what addresses are changing within a stack routine. The downfall is that it's a little complex because you have to find the right location within the stack to hook it to. It's more of a logger, that will print out the address of its location that it found from the values of the addresses that were changing. I came up with this because the ps2 scene doesn't have nitepr to view ram. Again it's only for use of someone with great understanding of stack routines. I'll post it later. (This helps me with creating new codes for games, most programs or plugins be using the less than and greater than to find changes in ram but mines work with both.) A little of knowledge of what I'm talking about...

Lets say registers t9 holds a value of 0x27bdffe0 and t8 holds 0xffffffff? The routine that I made is verifying or checking back to that address to see if the value has change by instructions xor t7, t9, t8; have they change? if it did not change then the value would be 0; slt t6, $0, t7; is my value greater than zero? flag slt t5, t7, 0; this was for the use of checking for negative values if it went to that.... finally or t4, t6, t5; if either one of the registers was flag by one then that means we had a change in value.

I just wanted to share and this was my first time in 7 years using MIPS that I used instruction "xor" lol

[xxphillips]

Thanks Helder

Your Easy and Crude Walk Through Walls guide helped me understand making these type of codes more and I filled in a request

Cyber Knight (Japan) Walk through walls 018A1D:8D

Take care

http://gamehacking.org/requests/133