Extended glitch Pokémon sprites: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens No edit summary |
>Torchickens No edit summary |
||
| Line 1: | Line 1: | ||
'''Extended glitch Pokémon sprites''' refer to glitch Pokémon sprites other than the usual ones encountered in a regular type of battle. |
'''Extended glitch Pokémon sprites''' refer to glitch Pokémon sprites other than the usual ones encountered in a regular type of battle. |
||
While each [[glitch Pokémon]] in {{RBY}} have one basic sprite (however the sprite may vary if it is located in RAM or is altered with [[inverted sprites]], or due to luck with glitch Pokémon with a zero (x256) sprite dimension (see also: [[freeze sprite glitch Pokémon]])), more glitch Pokémon sprites can be obtained if the original sprite is in a banked region of the [http://gameboy.mongenel.com/dmg/asmmemmap.html Game Boy Memory Map] (such as region 4000-7FFF or in SRAM). |
While each [[glitch Pokémon]] in {{RBY}} have one basic front sprite and one basic back sprite (however the sprite may vary if it is located in RAM or is altered with [[inverted sprites]], or due to luck with glitch Pokémon with a zero (x256) sprite dimension (see also: [[freeze sprite glitch Pokémon]])), more glitch Pokémon sprites can be obtained if the original sprite is in a banked region of the [http://gameboy.mongenel.com/dmg/asmmemmap.html Game Boy Memory Map] (such as region 4000-7FFF or in SRAM). |
||
By default, glitch Pokémon 0xBF-0xFF are in sprite bank 0x0D as per [[bp:Pokémon base stats data structure in Generation I#Sprites|this documentation]], but with a glitch, it is possible to force the same two byte sprite pointer but loaded from another bank (possible other banks include 0x01, 0x09, 0x0A, 0x0B, 0x0C), effectively loading a completely different sprite. |
By default, glitch Pokémon 0xBF-0xFF are in sprite bank 0x0D as per [[bp:Pokémon base stats data structure in Generation I#Sprites|this documentation]], but with a glitch, it is possible to force the same two byte sprite pointer but loaded from another bank (possible other banks include 0x01, 0x09, 0x0A, 0x0B, 0x0C), effectively loading a completely different sprite. |
||