If you have a cheat you by design know where it lands in memory and can either set a simple break on write to it to have an emulator tell you what instruction changed it, and instead change the code to do something else.
which is also what your average cheat device does.Ģ) You find the routine dealing with the item in question and edit that to nerf it, change a sub to an add or similar. I already went in one of the links above but for the sake of a relatively complete reply here.ġ) You find say a vblank routine (a section of code that the console runs ever frame, and devs/hackers/cheaters stick code into to run) and chuck in a little "write this to this area of memory" (maybe with a check to see if something else happened) such that every frame the game itself overwrites your health/ammo/mana/items/double jump count/. It is possible to patch in memory cheats to games, though most place the limit at doing it easily on anything post 16 bit, and even then I don't have any particularly good choices compared to the GBA and DS (see GBAATM, Gabsharky, GBA-ATM rebirth and DSATM) for the PS1 and N64 (though some are doing some things here that people are working on). Classically the game genie codes are ROM cheats, which is to say "this area of the ROM, make it this instead" which is why they are usually trivial to patch into the ROM once you understand the compression and encrytptions used.Įnhacklopedia, wherever it happens to be this week, usually carries a nice list of code descriptions for older consoles and newer stuff is usually documented in places as well. PAR/AR/gameshark/raw/codebreaker/goldfinger.
0 kommentar(er)
