Arbitrary sprites: Difference between revisions

Jump to navigation Jump to search
Content added Content deleted
>Torchickens
>Torchickens
Line 23: Line 23:
Addresses D0C2 (sprite dimension) and D0C3-D0C4 (front sprite pointer) (D0C1 and D0C2-D0C3 in Yellow) may be locked using [[OAM DMA hijacking]] or a [[cheating device]] to load a custom front sprite for every opposing Pokémon.
Addresses D0C2 (sprite dimension) and D0C3-D0C4 (front sprite pointer) (D0C1 and D0C2-D0C3 in Yellow) may be locked using [[OAM DMA hijacking]] or a [[cheating device]] to load a custom front sprite for every opposing Pokémon.


D0C2-D0C3 reads pointer expressed in little-endian form, for example, $DA7F for Yellow would be represented by $7F at $D0C2 and $80 at $D0C3
D0C2-D0C3 reads pointer expressed in little-endian form, for example, $DA7F for Yellow would be represented by $7F at $D0C2 and $80 at $D0C3.


For a cheating device like the GameShark, the following codes will replicate the same effects as locking these values with OAM DMA hijacking (assuming the sprites were properly patched):
For a cheating device like the GameShark, the following codes will replicate the same effects as locking these values with OAM DMA hijacking (assuming the sprites were properly patched):
Line 34: Line 34:


The first person to use this exploit is unknown, but it was popularized by pokeglitch and Torchickens.
The first person to use this exploit is unknown, but it was popularized by pokeglitch and Torchickens.



===With 9ゥ (E6)'s backsprite (Yellow)===
===With 9ゥ (E6)'s backsprite (Yellow)===