5,638
edits
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
This is a '''list of glitches''' that occur in the [[Generation III]] [[Pokémon games]]. | This is a '''list of glitches''' that occur in the [[Generation III]] [[Pokémon games]]. | ||
== | ==Ruby and Sapphire== | ||
===256× item selling glitch=== | ===256× item selling glitch=== | ||
When selling 256 or more of an item, even though the [[Poké Mart]] states the correct price, for every 256 the total price is actually counted as {{PDollar}}0 and the player loses {{PDollar}}2560 for every multiple of 256. For example, selling 999 Berries gives {{PDollar}}2310 (0 for 768, +2310 for 231). This is normally only possible with [[Berry|Berries]] because they are the only items that the player can hold more than 99 of, although through cheating the glitch can be performed with other items as well. | When selling 256 or more of an item, even though the [[Poké Mart]] states the correct price, for every 256 the total price is actually counted as {{PDollar}}0 and the player loses {{PDollar}}2560 for every multiple of 256. For example, selling 999 Berries gives {{PDollar}}2310 (0 for 768, +2310 for 231). This is normally only possible with [[Berry|Berries]] because they are the only items that the player can hold more than 99 of, although through cheating the glitch can be performed with other items as well. | ||
Line 63: | Line 63: | ||
{{youtubevid|h2XCR0s6mfQ|Wooggle|apricorn}} | {{youtubevid|h2XCR0s6mfQ|Wooggle|apricorn}} | ||
== | ==FireRed and LeafGreen== | ||
===Infinite Nugget glitch=== | ===Infinite Nugget glitch=== | ||
{{GlitchResearch|Check the Japanese version.}} | {{GlitchResearch|Check the Japanese version.}} | ||
Line 83: | Line 83: | ||
If a [[roaming Pokémon]] uses {{m|Roar}} to flee from battle, it will permanently disappear from the game. Most notably, this means that if the {{p|Raikou}} or {{p|Entei}} player encounters during the post-game uses Roar before it is caught, it cannot be encountered again, unless the game is reset to the state which it was in before the encounter. | If a [[roaming Pokémon]] uses {{m|Roar}} to flee from battle, it will permanently disappear from the game. Most notably, this means that if the {{p|Raikou}} or {{p|Entei}} player encounters during the post-game uses Roar before it is caught, it cannot be encountered again, unless the game is reset to the state which it was in before the encounter. | ||
== | ==Ruby, Sapphire, FireRed, and LeafGreen== | ||
===Roaming IV glitch=== | ===Roaming IV glitch=== | ||
This glitch causes [[roaming Pokémon]] to have extremely low {{IV}}s. | This glitch causes [[roaming Pokémon]] to have extremely low {{IV}}s. | ||
Line 89: | Line 89: | ||
In [[Generation III]], the data for a Pokémon's IVs are stored in a [[Individual values#Generation III|32-bit integer]]. However, when a roaming Pokémon is captured, only the last eight bits are transferred. While the {{stat|HP}} IV is unaffected, the Pokémon can only have a maximum {{stat|Attack}} IV of 7. The other IVs will always be 0. | In [[Generation III]], the data for a Pokémon's IVs are stored in a [[Individual values#Generation III|32-bit integer]]. However, when a roaming Pokémon is captured, only the last eight bits are transferred. While the {{stat|HP}} IV is unaffected, the Pokémon can only have a maximum {{stat|Attack}} IV of 7. The other IVs will always be 0. | ||
== | ==Emerald== | ||
===Battle Tower cloning glitch=== | ===Battle Tower cloning glitch=== | ||
{{main|Cloning glitches#Generation III}} | {{main|Cloning glitches#Generation III}} | ||
Line 113: | Line 113: | ||
{{youtubevid|Y2_4MZXoPak|Sato|emerald}} | {{youtubevid|Y2_4MZXoPak|Sato|emerald}} | ||
== | ==Ruby, Sapphire, and Emerald== | ||
===Dive glitch=== | ===Dive glitch=== | ||
{{main|Dive glitch}} | {{main|Dive glitch}} | ||
Line 146: | Line 146: | ||
The details on the description for the move {{m|Vital Throw}} show it as having 100% {{stat|accuracy}}, despite the move hitting the opposing Pokémon regardless of accuracy and {{stat|evasion}}. | The details on the description for the move {{m|Vital Throw}} show it as having 100% {{stat|accuracy}}, despite the move hitting the opposing Pokémon regardless of accuracy and {{stat|evasion}}. | ||
{{-}} | {{-}} | ||
== | =={{pkmn|Colosseum}}== | ||
===Experience glitch=== | ===Experience glitch=== | ||
{{GlitchResearch|Do volatile status ailments like confusion, Leech Seed, and Curse cause this too?}} | {{GlitchResearch|Do volatile status ailments like confusion, Leech Seed, and Curse cause this too?}} |
edits