Anonymous user
Arbitrary sprites: Difference between revisions
no edit summary
>Torchickens (Created page with "thumb|right|160px|'Yoshi' as the backsprite of a Pokémon. '''Arbitrary sprite''' (or '''custom sprites''') or '''arbitrary sprites pointers''' refe...") |
>Torchickens No edit summary |
||
Line 3:
'''Arbitrary sprite''' (or '''custom sprites''') or '''arbitrary sprites pointers''' refers to a [[glitch technique]] in {{RBY}}, in which a [[glitch]] is used to insert data the player desires into a Pokémon, [[glitch Pokémon]], Trainer or [[glitch Trainer]]'s sprite.
It does not refer to hacking Pokémon sprites into the ROM, but rather refers to 'custom sprites' appearing due to modified [[RAM]].
For the later discovered methods, this requires that the source of the sprite is sourced from [[RAM|writable memory region]]. For the original method, an emulator and memory viewer may be needed.▼
▲For the later discovered methods, this requires that the source of the sprite is sourced from
The technique in its simplest form can be used to modify the sprite dimensions and data representing the sprite, in order to modify how glitches relying on glitch sprites affect data such as the Hall of Fame (see [[Hall of Fame corruption]]).
Line 51 ⟶ 53:
Using arbitrary code execution, a custom sprite (usually with internal dimension byte 0x77 meaning a 56x56 dimension sprite) can be written here just before entering the battle, however, the data is wiped after saving and resetting the game (and possibly other options that change the buffer like moving to another map).
==In later generations==
Arbitrary sprites are theoretically possible, but no vulnerability to do it have, as of yet been documented.
==See also==
| |||