Hacking Post your WiiU cheat codes here!

  • Thread starter Thread starter LawnMeower
  • Start date Start date
  • Views Views 2,114,838
  • Replies Replies 9,274
  • Likes Likes 52
No sorry.... I mean this error is this normal? It happens when I put a big range in the search... This happen for example just with the default search set to 10000000-15000000
28vbyft.png
Install 64-bit Java.
 
Last edited by BullyWiiPlaza,
Anyone got any cheat codes for Captain Toad: Treasure Tracker?

No idea, but I did upload my 100% save on this site if you'd like that instead. It's a US save.

EDIT: Never mind. I just realized you don't live in the US. Sorry about that :(

And here you go @Macopride64. If the RAM is wrong please tell me. Thanks again!
 

Attachments

Last edited by RedRose30,
Hello ! I tried the code:
Always crushed / squish
00120000 4443BB4C
40D9F1EC 47AD84A8
00000004 60000000
But it don't work in PAL, but when I go to "memory viewer", and I put 4443BB4C I find a value that is not true. So I just wanted to know if with this code we can find the true value (the one where you can see the value that is put) ? or is there a similar code for PAL ?
I use +144
 
I have problems, I'm looking to edit some sparks (currency) on a game and I found only one address with that value, but when I poke it to another value it resets to the previous one. I have searched so many times and the same address appears.
How do I edit my coins if i only got an address that doesnt work if i change it?

The game is Disney Infinity 3.0 and I'm looking in a memory range of 10000000 to 400000000 for a value of 32 bits since my current sparks are 134,009. I really need help.

Thanks
 

Attachments

  • dis.png
    dis.png
    17.6 KB · Views: 192
Has anyone made an updated XML for Hyrule Warriors 1.12.0? Especially with the Adventure Map item offsets? Even if you have just the addresses or offset, I suppose I could be arsed to put them in an XML myself.
 
Last edited by Ailuros27,
Because the new codehandler shifted the addresses
Wait. So we have to find all our codes again? Or is the offset the same +2000 for everything? Because if I have to find everything again every time the codehandler changes then I'm done using JGecko U until the codehandler stops changing. :nayps3:
 
Last edited by Ailuros27, , Reason: For clarity.
Wait. So we have to find all our codes again? Or is the offset the same +2000 for everything? Because if I have to find everything again every time the codehandler changes then I'm done using JGecko U until the codehandler stops changing. :nayps3:
Apparently the same +0x2000 for everything compared to the "old" layout (from the browser).
 

Site & Scene News

Popular threads in this forum