Chaotic glitches: Difference between revisions

*In Pokémon and Green, [[ItemDexJP/RG:000|item 0x00]] has a seemingly random name as well, but research is currently incomplete.

*[[Arbitrary code execution]] will typically run a region of [[RAM]] as code; for this reason, changing one byte will change an entire opcode or operand; the effects can be very different, and can be affected by lots of seemingly unrelated factors other than them being variables in the RAM (anything from for instance Pokémon, to items, to play time, to states or movements on the overworld can be included as a requirement for the code). Additionally, the structure of the [http://gameboy.mongenel.com/dmg/asmmemmap.html memory map] is not necessarily organised for the player (for example, while inventory structures for the item and quantities (D31E-D346 (-1 in Yellow) go on in a continuous order, some data pertaining to various parts of the game is located further on (D347+), and Pokédex flags further back (D2F7-D31C (-1 in Yellow). The program counter can also attempt to run Echo RAM, HRAM (hardware RAM such as the zero page and I/O registers), SRAM, VRAM. For [[unintended ROM code execution]], the game will also have no way of distinguishing data from code.

**The combination of a glitch that corrupts SRAM and the use of [[ItemDex/RB:085|B1F]] is known for its hard to predict effects.

*The effects of nudging, tilting, or pulling out the Game Pak while the power is on are known for their 'randomness', but most of the time [[game freeze|freeze]] the game.

*Glitches which do not execute code from Echo RAM but access it (example: [[dokokashira door glitch]]).