Hacking Different memory ranges on tcpgecko

  • Thread starter Thread starter wiitendo84
  • Start date Start date
  • Views Views 2,133
  • Replies Replies 4

wiitendo84

Well-Known Member
Member
Joined
Jan 3, 2014
Messages
1,420
Solutions
1
Reaction score
2,067
Trophies
3
Age
42
Location
New Albany, Indiana
XP
4,130
Country
United States
Alright so this might sound like a noob question but I was wondering what each of the memory ranges actually do? Is there a way to actually use them for cheats or is that a no.
 
I am assuming you mean the client (like tcpGecko.NET)
You will want to select the 10 range ( 0x10000000 - 0x45000000 ). This is where the codes live in most cases. I have seen some go lower and some go higher - but going higher than 0x45000000 causes errors in almost every case.
If you are searching - that is you search range.
If you are in the memory viewer that is the range of memory you are viewing.
In either case - once you find an address (or confirm an address for a code you have works) you will need to poke the value, of that code into memory, at that address.
JGeckoU also works for memory editing (code handler does not function on loadiine and loadiine has different offsets for the codes than retail - and even a new nightly builds can affect that offset) and hopefully soon there will be searching implemented.

Also, if you like python, pyGecko is pretty neat.


Sorry left out an important link - there is a lot of info about all of this stuff here :)
https://gbatemp.net/threads/post-your-wiiu-cheat-codes-here.395443/
 
Last edited by rbsk,
The reason why I'm asking is that I have been trying to make cheats for Donkey Kong Tropical Freeze and so far its a no go. I didn't know if using any of the other memory ranges would help or not.
 

Site & Scene News

Popular threads in this forum