AttackDex/C:000: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>CasualPokePlayer (Additional info for Move 0x00's type and ways to avoid crashes.) |
>CasualPokePlayer m (minor grammar issue from previous edit) |
||
Line 6: | Line 6: | ||
In battle it may appear as a Normal-type move. Using it may result in the text "(POKéMON) used ど ◄öSど◄:E 30!" however the move seems to have low accuracy. If the move is successful it may result in an animation and the enemy Pokémon becoming badly poisoned. |
In battle it may appear as a Normal-type move. Using it may result in the text "(POKéMON) used ど ◄öSど◄:E 30!" however the move seems to have low accuracy. If the move is successful it may result in an animation and the enemy Pokémon becoming badly poisoned. |
||
On the moves list, this glitch move will take the type 0xD1. This type's name is sourced from $8091, which is VRAM for the second icon of the party screen. Using specific party icons with terminator bytes in the data (i.e. ICON_FOX, ICON_MONSTER, and ICON_POLIWAG) the type name can be safely terminated, albeit with a chance to not terminate due to VRAM inaccessibility. If the name does not terminate, it will result in a crash, sometimes resetting |
On the moves list, this glitch move will take the type 0xD1. This type's name is sourced from $8091, which is VRAM for the second icon of the party screen. Using specific party icons with terminator bytes in the data (i.e. ICON_FOX, ICON_MONSTER, and ICON_POLIWAG) the type name can be safely terminated, albeit with a chance to not terminate due to VRAM inaccessibility. If the name does not terminate, it will result in a crash, sometimes resetting to the "[[This Game Pak is designed only for use on the Game Boy Color.]]" message. |
||
==Accessing the glitch move== |
==Accessing the glitch move== |