er........
details are kinda......lacking?
there are 3 types of codes:
static codes: places in memory that dont move around
pointer codes: requires a little more experience, creates whats known as a pointer or address loader to another location. this type of code is for when addresses move around.
asm code: (if you have no programming exp at all, this will challenging....) code that alters game programming.
what game are you trying to make a code for?
details are kinda......lacking?
there are 3 types of codes:
static codes: places in memory that dont move around
pointer codes: requires a little more experience, creates whats known as a pointer or address loader to another location. this type of code is for when addresses move around.
asm code: (if you have no programming exp at all, this will challenging....) code that alters game programming.
what game are you trying to make a code for?
Have tried to find codes with Breeze but somehow I have not managed it. The hardest part is how to use Breeze, I can't figure it out, even the tutorials don't make it easy.
A little video on how to find simple codes would help me a lot. Pointer codes and the rest I would create myself
A little video on how to find simple codes would help me a lot. Pointer codes and the rest I would create myself
If this is for the Switch you might be jumping in at the deep end somewhat. I will do a more general case.
Generally speaking and skipping save based approaches for this one.
Games store the amounts of things you have, or states your game/character is or is in using the memory.
However even on the NES the amount of memory makes it unproductive to guess randomly so you need to narrow it down.
The easiest cheats to make then being things you can manipulate consistently. Money, potions, health... where you can lose one, search for changes, lose one, search for changes...
States are a bit harder via said searches as you have two choices so you get poisoned, cure it, get it again, cure it... to make an immune to poison state cheat. You will see such binary states referred to as flags a lot as well.
Cheat making, and hacking in general, then being about figuring out ways to get to the data you want and its greater implications. Greater implications is how people do things like make end game weapon cheats, hidden weapons, hidden characters and the like.
Weapon cheats for instance probably won't see the cheat maker play to the end of the game and 20 hour sidequest, instead infinite first town sword is easy enough to do (give yourself infinite money first) and then the game will either have an identifier associated with the weapon or it will be in a fixed location in a table, go next value up or next location and it is on from there. This is also how play as boss cheats, and debug items get made. Walk through walls cheats, assuming they are not a flag, tend to be this but for location within the game world.
You may also have to design a cheat to work around a limitation -- RPGs tend to have a battle you are forced to lose so a basic infinite health cheat can break that, press button to refill health (assuming you don't want to use the device or emulator to turn it on and off, or make a more exotic code to recognise this is a can't win event and go from there*).
*this is known as conditional cheats. Most encounter them first when they want to make a button activator cheat where it looks for a certain button combo to have been pressed to do what it needs but you can watch other areas of memory to have it do something in turn, indeed said area of memory might be one you set yourself with another cheat if you wanted. If you have ever done loops in programming this is part of that. IF ELSE being the main one, but FOR loops do appear as well where it is commonly called a slide code (say you want 999 of each item in a game, you could do one line for each of the say 500 items in the game but that is annoying when you can say "from here to here put 999 in the values column", same for health for each member of a party), and fairly easy to get the WHILE loop going on (check to see if this value is one thing, do this action if so, maybe set the value to the not going to do it next time if you wanted) as well.
Pointers. Whether as a form of anti cheat because modern coding approaches can assign and release memory at will to reduce the amount of memory needed (in your average NES game a section of memory once designated in code is likely to be that forever more/reason you can't reboot/until the next radically different minigame, and thus not free to use on something else unless you account for it). There is still a fixed area but rather than being the whole amount of data it is instead a location that points the way as it were to another location, and yes you can have a pointer to a pointer to a pointer... it is actually an exam question in many cases, a method of anti cheat and also the result of dubious coding but yours is not necessarily to reason why but deal with the results.
Anti cheat is a whole other aspect but if it is not pointer based (maybe the current location switches between different things) usually it involves some other number running in parallel (copies, inverted, checksum... it matters little) or means of obscuring the real number.
Assembly codes, or game genie codes to most of cheat making, do speak to the game itself.
In most modern devices the game's code is loaded into memory and operates from there. As you can edit memory you can also edit the code.
Here then you would either dump the code from memory (or the ROM) and figure out how it deals with the thing you want to deal with, usually by having a memory cheat and setting a debugger to watch what edits that area or some other known aspect of memory like sprite location or watching what happens as a result of a button press/what is watching for the button press.
Rather than holding the lives counter in memory you can instead find what subtracts from it and edit it to be an add instead, which can be many things (all the ways you can die in the average game might be separate). This is also how you understand how the mechanics work in most cases (observation in play is hard with hidden things doing hidden maths) as you can watch how it takes atk of sword, strength of player, def of enemy, probably some random numbers, weakness to elemental and whatever else to do the deed.
Older devices did not have code in memory, or exclusively in memory (the GBA was the last device to keep it on the ROM, and even then can and does have some things in memory) and thus if you sat your cheat device between the cart and the system it could intercept reads for specific locations and send back whatever it likes. This is also what hardpatching game genie codes into old games is trivial where patching memory codes into old games is actually a technical feat in most systems, with only a handful of more powerful devices and simpler devices having some kind of automated process.
Emulators will often provide a cheat search option. Others will attach programs to emulators (emuhaste, art money, cheat engine... all examples of such things). More modern systems will have options to have memory read by other programs running on the machine, or spit out the contents of memory via network/USB/whatever to external devices which do much the same.
Either way you can take dumps of memory (some do this with savestates, a process known to some as savestate hacking even if it is a more long winded version of this), do the change (and preferably nothing else or as little else as you can), search for the change, do another change, search for it... until the list of possible options is narrow enough or obvious enough that you have the location and what is stored there to have the cheat (basic cheats being a type, a location where you want it and maybe something to write there once you do, assuming you don't say just hold it at whatever it is) Some things will offer greater than or less than searches to speed it up (assuming it behaves as you expect), specific value searches (again assuming it behaves like that). If say your game has a timer running in the background or some idle animations code ticking over in the background you might instead opt to leave what you care about for a search cycle and instead search for things that remained the same. Sometimes people will also use savestates to restore saves and presumably also the states (back to the poison thing if you had to go into a battle and wait to get hit, cure it and repeat that is annoying, a savetate being restored quickly to give it back, and possibly also wait a few seconds leaving it alone to clear out the background timers...). Of course the assembly hacker would note that poison damages health so would instead put a breakpoint on the health location, and when the poison damages because time/moved a pace/... it will flash up saying something damaged health, if it is more subtle than that then there is probably something on screen. At the same time find one state and in most cases they will be all next to each other so burned, paralysed, stone and whatever else in the imaginary RPG we are using in this example will be likely next to it, or nearby if it instead stores the poison states of all the characters in the party, then the burned states, the the paralysed... though this is rare to see for states and instead that arrangement is something I associate more with states (all the atk stats, all the def, all the int, all the con... rather than one party member's list, then another's).
The guides in this are good stuff, I do also usually link
and https://doc.kodewerx.org/ (if that link is down search for enhacklopedia) at times like these.
More advanced cheat engines will also do boolean logic. This is mostly used to set specific bits in a place or go the other way and extra specific bits -- 32 bits of value where everything else has a meaning and could be anything means you can't say set this value, or add a value without it potentially breaking everything. Likewise 32 bits of value is 2 to the power of 32 combinations which you don't want to check every combo for. Instead a boolean AND with everything but the thing you care about set to 0 means the result will be a single choice for your cheat as it forcibly sets the rest to 0. OR with everything else set to 0 and the thing you want to set to 1 being 1 means that bit is going to be high regardless and everything else is unchanged. You can discover and contemplate how XOR might work for you on your own time, and everything else is basically the inverse.
Back on the assembly/game genie thing then this video contains one of the clearer examples of the mindset I have ever seen, bit old (the list of previously executed instructions on anything vaguely modern would be far larger and thus far nicer to work back from) but again super clear
Generally speaking and skipping save based approaches for this one.
Games store the amounts of things you have, or states your game/character is or is in using the memory.
However even on the NES the amount of memory makes it unproductive to guess randomly so you need to narrow it down.
The easiest cheats to make then being things you can manipulate consistently. Money, potions, health... where you can lose one, search for changes, lose one, search for changes...
States are a bit harder via said searches as you have two choices so you get poisoned, cure it, get it again, cure it... to make an immune to poison state cheat. You will see such binary states referred to as flags a lot as well.
Cheat making, and hacking in general, then being about figuring out ways to get to the data you want and its greater implications. Greater implications is how people do things like make end game weapon cheats, hidden weapons, hidden characters and the like.
Weapon cheats for instance probably won't see the cheat maker play to the end of the game and 20 hour sidequest, instead infinite first town sword is easy enough to do (give yourself infinite money first) and then the game will either have an identifier associated with the weapon or it will be in a fixed location in a table, go next value up or next location and it is on from there. This is also how play as boss cheats, and debug items get made. Walk through walls cheats, assuming they are not a flag, tend to be this but for location within the game world.
You may also have to design a cheat to work around a limitation -- RPGs tend to have a battle you are forced to lose so a basic infinite health cheat can break that, press button to refill health (assuming you don't want to use the device or emulator to turn it on and off, or make a more exotic code to recognise this is a can't win event and go from there*).
*this is known as conditional cheats. Most encounter them first when they want to make a button activator cheat where it looks for a certain button combo to have been pressed to do what it needs but you can watch other areas of memory to have it do something in turn, indeed said area of memory might be one you set yourself with another cheat if you wanted. If you have ever done loops in programming this is part of that. IF ELSE being the main one, but FOR loops do appear as well where it is commonly called a slide code (say you want 999 of each item in a game, you could do one line for each of the say 500 items in the game but that is annoying when you can say "from here to here put 999 in the values column", same for health for each member of a party), and fairly easy to get the WHILE loop going on (check to see if this value is one thing, do this action if so, maybe set the value to the not going to do it next time if you wanted) as well.
Pointers. Whether as a form of anti cheat because modern coding approaches can assign and release memory at will to reduce the amount of memory needed (in your average NES game a section of memory once designated in code is likely to be that forever more/reason you can't reboot/until the next radically different minigame, and thus not free to use on something else unless you account for it). There is still a fixed area but rather than being the whole amount of data it is instead a location that points the way as it were to another location, and yes you can have a pointer to a pointer to a pointer... it is actually an exam question in many cases, a method of anti cheat and also the result of dubious coding but yours is not necessarily to reason why but deal with the results.
Anti cheat is a whole other aspect but if it is not pointer based (maybe the current location switches between different things) usually it involves some other number running in parallel (copies, inverted, checksum... it matters little) or means of obscuring the real number.
Assembly codes, or game genie codes to most of cheat making, do speak to the game itself.
In most modern devices the game's code is loaded into memory and operates from there. As you can edit memory you can also edit the code.
Here then you would either dump the code from memory (or the ROM) and figure out how it deals with the thing you want to deal with, usually by having a memory cheat and setting a debugger to watch what edits that area or some other known aspect of memory like sprite location or watching what happens as a result of a button press/what is watching for the button press.
Rather than holding the lives counter in memory you can instead find what subtracts from it and edit it to be an add instead, which can be many things (all the ways you can die in the average game might be separate). This is also how you understand how the mechanics work in most cases (observation in play is hard with hidden things doing hidden maths) as you can watch how it takes atk of sword, strength of player, def of enemy, probably some random numbers, weakness to elemental and whatever else to do the deed.
Older devices did not have code in memory, or exclusively in memory (the GBA was the last device to keep it on the ROM, and even then can and does have some things in memory) and thus if you sat your cheat device between the cart and the system it could intercept reads for specific locations and send back whatever it likes. This is also what hardpatching game genie codes into old games is trivial where patching memory codes into old games is actually a technical feat in most systems, with only a handful of more powerful devices and simpler devices having some kind of automated process.
Emulators will often provide a cheat search option. Others will attach programs to emulators (emuhaste, art money, cheat engine... all examples of such things). More modern systems will have options to have memory read by other programs running on the machine, or spit out the contents of memory via network/USB/whatever to external devices which do much the same.
Either way you can take dumps of memory (some do this with savestates, a process known to some as savestate hacking even if it is a more long winded version of this), do the change (and preferably nothing else or as little else as you can), search for the change, do another change, search for it... until the list of possible options is narrow enough or obvious enough that you have the location and what is stored there to have the cheat (basic cheats being a type, a location where you want it and maybe something to write there once you do, assuming you don't say just hold it at whatever it is) Some things will offer greater than or less than searches to speed it up (assuming it behaves as you expect), specific value searches (again assuming it behaves like that). If say your game has a timer running in the background or some idle animations code ticking over in the background you might instead opt to leave what you care about for a search cycle and instead search for things that remained the same. Sometimes people will also use savestates to restore saves and presumably also the states (back to the poison thing if you had to go into a battle and wait to get hit, cure it and repeat that is annoying, a savetate being restored quickly to give it back, and possibly also wait a few seconds leaving it alone to clear out the background timers...). Of course the assembly hacker would note that poison damages health so would instead put a breakpoint on the health location, and when the poison damages because time/moved a pace/... it will flash up saying something damaged health, if it is more subtle than that then there is probably something on screen. At the same time find one state and in most cases they will be all next to each other so burned, paralysed, stone and whatever else in the imaginary RPG we are using in this example will be likely next to it, or nearby if it instead stores the poison states of all the characters in the party, then the burned states, the the paralysed... though this is rare to see for states and instead that arrangement is something I associate more with states (all the atk stats, all the def, all the int, all the con... rather than one party member's list, then another's).
The guides in this are good stuff, I do also usually link
Members-only download
More advanced cheat engines will also do boolean logic. This is mostly used to set specific bits in a place or go the other way and extra specific bits -- 32 bits of value where everything else has a meaning and could be anything means you can't say set this value, or add a value without it potentially breaking everything. Likewise 32 bits of value is 2 to the power of 32 combinations which you don't want to check every combo for. Instead a boolean AND with everything but the thing you care about set to 0 means the result will be a single choice for your cheat as it forcibly sets the rest to 0. OR with everything else set to 0 and the thing you want to set to 1 being 1 means that bit is going to be high regardless and everything else is unchanged. You can discover and contemplate how XOR might work for you on your own time, and everything else is basically the inverse.
Back on the assembly/game genie thing then this video contains one of the clearer examples of the mindset I have ever seen, bit old (the list of previously executed instructions on anything vaguely modern would be far larger and thus far nicer to work back from) but again super clear
yeah bro i already do this with game on my pc like minecraft ... ( using cheat engine )
but idk how to do this on my 3ds maybe use an emulator ?
Assuming you are talking about making cheat code for Switch that runs on Atmosphere
Simple cheat can be easily made with Breeze.
First step search for value the game shows to you.
Second step change the value and search again. Repeat this step until you have just a few candidates.
Third step hack the value and see if you have found any good candidate.
Fourth step add candidate to bookmark. Create dump for pointer searcher SE. Restart the game and see if the bookmark is still good (static case).
Fifth step add the bookmark to cheat if static case. Do pointer search if not. Import pointers into Breeze and see if any of them are good. Add bookmark to cheat if yes.
Sixth step save cheat created to file and publish it if you like.
These steps should be good enough for you to make some cheats and call yourself a cheat maker.
A simple example to make cheat for ACNH ( a notable example of static value )
1. Have something on slot one that is more than 1.
2. Start search for qty -1 with data type u32.
3. Change the qty by playing the game.
4. Continue Search.
5. Repeat 3 and 4 until there is a small list of candidates.
6. Hack to see which one.
7. Add candidate to bookmark.
8. Add bookmark to cheat.
You have made your first cheat
Simple cheat can be easily made with Breeze.
First step search for value the game shows to you.
Second step change the value and search again. Repeat this step until you have just a few candidates.
Third step hack the value and see if you have found any good candidate.
Fourth step add candidate to bookmark. Create dump for pointer searcher SE. Restart the game and see if the bookmark is still good (static case).
Fifth step add the bookmark to cheat if static case. Do pointer search if not. Import pointers into Breeze and see if any of them are good. Add bookmark to cheat if yes.
Sixth step save cheat created to file and publish it if you like.
These steps should be good enough for you to make some cheats and call yourself a cheat maker.
A simple example to make cheat for ACNH ( a notable example of static value )
1. Have something on slot one that is more than 1.
2. Start search for qty -1 with data type u32.
3. Change the qty by playing the game.
4. Continue Search.
5. Repeat 3 and 4 until there is a small list of candidates.
6. Hack to see which one.
7. Add candidate to bookmark.
8. Add bookmark to cheat.
You have made your first cheat
Last edited by TomSwitch,
I wanted to ask if breeze is usable with emulators? if not is there is an alternative tool that can work with yuzu or ryjunix?
Similar threads
