3
edits
List of glitches (Generation III): Difference between revisions
List of glitches (Generation III) (view source)
Revision as of 04:13, 9 September 2020
, 9 September 2020→added link to purification and rematch tab
Timeforweej (talk | contribs) |
|||
| (10 intermediate revisions by 8 users not shown) | |||
| Line 76: | Line 76: | ||
===Stuck audio freeze=== | ===Stuck audio freeze=== | ||
In some copies of {{game|Ruby and Sapphire|s}}, using {{m|Thunder}} or {{m|Thunderbolt}} may cause the [[Game freeze|game to freeze]] during the animation sequences of the [[move]]s. This can be remedied by turning off the [[battle effects]] in the [[options]]. | In some copies of {{game|Ruby and Sapphire|s}}, using {{m|Thunder}} or {{m|Thunderbolt}} may cause the [[Game freeze|game to freeze]] during the animation sequences of the [[move]]s. This can be remedied by turning off the [[battle effects]] in the [[options]]. | ||
==={{m|Toxic}} catch rate bug=== | |||
If the {{pkmn2|wild}} Pokémon is {{DL|Status condition|badly poisoned}}, no status condition bonus is applied to the catch rate. This was fixed in {{2v2|FireRed|LeafGreen}}. | |||
===Trainer approach oversights=== | ===Trainer approach oversights=== | ||
{{GlitchResearch|Check all languages.}} | {{GlitchResearch|Check all languages.}} | ||
There are three [[Non-player character|NPCs]] who may move on top of an obstacle. This | There are three [[Non-player character|NPCs]] who may move on top of an obstacle. This only occurs in the English versions as these {{pkmn|Trainer}}s have a different visual range from the other versions. | ||
If the player stands in {{rt|118|Hoenn}}'s {{tc|Aroma Lady}} Rose, {{rt|121|Hoenn}}'s {{tc|Gentleman}} Walter, or [[Abandoned Ship]]'s {{tc|Tuber}} Charlie's line of sight while directly behind the [[ledge]], fence, or wall, the Trainer will notice the player and walk over these obstacles and {{pkmn|battle}}. | If the player stands in {{rt|118|Hoenn}}'s {{tc|Aroma Lady}} Rose, {{rt|121|Hoenn}}'s {{tc|Gentleman}} Walter, or [[Abandoned Ship]]'s {{tc|Tuber}} Charlie's line of sight while directly behind the [[ledge]], fence, or wall, the Trainer will notice the player and walk over these obstacles and {{pkmn|battle}}. | ||
| Line 126: | Line 129: | ||
===Sootopolis Gym wall oversight=== | ===Sootopolis Gym wall oversight=== | ||
In [[Sootopolis Gym]], the player can walk one step into the wall to the right-down of the stairs, causing them to stop working until | In [[Sootopolis Gym]], the player can walk one step into the wall to the right-down of the stairs, causing them to stop working until they step back onto the floor. | ||
{{YouTubeEmbed|jtVnvwFGGWA|channel/UCG11xx7bQcbXB4ThsgsYs7w|name=EricchiYukia|Ice}} | {{YouTubeEmbed|jtVnvwFGGWA|channel/UCG11xx7bQcbXB4ThsgsYs7w|name=EricchiYukia|Ice}} | ||
| Line 197: | Line 200: | ||
That's because the sounds in the game fall into four groups: {{tt|BGM|Background music}}, {{tt|BGS|Background sounds}}, {{tt|ME|Music effects}} and {{tt|SE|Sound effects}}. Accessing the Help System stops all the sounds that fall into the {{tt|ME|Music effects}} group. This doesn't occur in any of the Japanese versions of the game, or if the button mode is set to '''L+A'''. | That's because the sounds in the game fall into four groups: {{tt|BGM|Background music}}, {{tt|BGS|Background sounds}}, {{tt|ME|Music effects}} and {{tt|SE|Sound effects}}. Accessing the Help System stops all the sounds that fall into the {{tt|ME|Music effects}} group. This doesn't occur in any of the Japanese versions of the game, or if the button mode is set to '''L+A'''. | ||
{{YouTubeEmbed|QZatzouUnXc|GlitchyGarchomp|status}} | {{YouTubeEmbed|QZatzouUnXc|GlitchyGarchomp|status}} | ||
{{YouTubeEmbed|r8wCy8TV-rU| | {{YouTubeEmbed|r8wCy8TV-rU|UCGem9_-WFL4gBAL02NVYdKw|name=Keyacom|normal|fairy}} | ||
===Roaming Roar bug=== | ===Roaming Roar bug=== | ||
| Line 232: | Line 235: | ||
===Status condition delayed cure glitch=== | ===Status condition delayed cure glitch=== | ||
If a Pokémon with a [[status condition]] that has an [[Ability]] that cures that status condition (e.g. a {{status|paralysis|paralyzed}} Pokémon with {{a|Limber}}) is sent into battle as one of the lead Pokémon or to replace a fainted Pokémon, or gains that Ability due to {{a|Trace}}, it will not be cured of its status condition until after a Pokémon takes its turn (uses a move, switches out, etc.). However, it will be immediately cured of the status condition if it is switched in to replace a switched out Pokémon. | If a Pokémon with a [[status condition]] that has an [[Ability]] that cures that status condition (e.g. a {{status|paralysis|paralyzed}} Pokémon with {{a|Limber}}) is sent into battle as one of the lead Pokémon or to replace a fainted Pokémon, or gains that Ability due to {{a|Trace}}, it will not be cured of its status condition until after a Pokémon takes its turn (uses a move, switches out, etc.). However, it will be immediately cured of the status condition if it is switched in to replace a switched out Pokémon (including if switched in via {{m|Baton Pass}}). | ||
Likewise, if a Pokémon with {{a|Trace}} is {{status|confusion|confused}} due to obtaining it from {{m|Baton Pass}}, if it gains {{a|Own Tempo}} via Trace it will not be cured of confusion until after a Pokémon takes its turn (uses a move, switches out, etc.). | Likewise, if a Pokémon with {{a|Trace}} is {{status|confusion|confused}} due to obtaining it from {{m|Baton Pass}}, if it gains {{a|Own Tempo}} via Trace it will not be cured of confusion until after a Pokémon takes its turn (uses a move, switches out, etc.). | ||
| Line 257: | Line 260: | ||
{{GlitchResearch|Does Hail trigger this too? Is the Exp. Share required? Does the opposing Pokémon need to be immune to weather damage? What happens if both of the Player's Pokémon would hit zero?}} | {{GlitchResearch|Does Hail trigger this too? Is the Exp. Share required? Does the opposing Pokémon need to be immune to weather damage? What happens if both of the Player's Pokémon would hit zero?}} | ||
If the last opposing {{OBP|Pokémon|species}} is defeated with Perish | If the last opposing {{OBP|Pokémon|species}} is defeated with Perish Song while {{m|Sandstorm}} is active, the opposing Pokémon that fainted was immune to Sandstorm, and at least one if the player's Pokémon is about to also reach zero, then the battle will continue on with the player's Pokémon also fainting. Those Pokémon that were out with that Pokémon and any Pokémon holding an [[Exp. Share]] will gain experience as if it was an opposing Pokémon before the battle concludes. | ||
===Poké Ball amount bug=== | ===Poké Ball amount bug=== | ||
| Line 274: | Line 277: | ||
===Shiny Shadow Pokémon bug=== | ===Shiny Shadow Pokémon bug=== | ||
Like in the [[core series]] games, in {{g|Colosseum}} there is a 1/8192 chance | Like in the [[core series]] games, in {{g|Colosseum}} there is a 1/8192 chance for [[Shadow Pokémon]] to be {{Shiny}}. When fighting a trainer with a Shadow Pokémon for the first time, its information will be decided and there is a 1/8192 chance of spontaneously becoming Shiny for the player after capturing it, but never for the opponent. If the player loses without capturing the Pokémon and decides to [[rematch]] the trainer, the information for that Pokémon will be locked in and ''can'' be shiny for the opponent, and will only be shiny for the player if it would have been the first time the trainer was fought. Shadow Pokémon retain shininess through [[purification]]. | ||
This bug occurs because when the player captures a Shadow Pokémon, their [[Trainer ID number]] overwrites the [[original Trainer]]'s ID number, unlike with [[trade]]d Pokémon; because the Trainer ID number is a factor in Shiny calculation, this may cause the Pokémon to acquire (or lose) their Shiny status. This is similar to the oddity of a hatched {{pkmn|Egg}} changing from normal to Shiny (or vice-versa) if it was traded to another player before hatching. | This bug occurs because when the player captures a Shadow Pokémon, their [[Trainer ID number]] overwrites the [[original Trainer]]'s ID number, unlike with [[trade]]d Pokémon; because the Trainer ID number is a factor in Shiny calculation, this may cause the Pokémon to acquire (or lose) their Shiny status. This is similar to the oddity of a hatched {{pkmn|Egg}} changing from normal to Shiny (or vice-versa) if it was traded to another player before hatching. | ||
| Line 316: | Line 319: | ||
[[es:Lista de glitches de la tercera generación]] | [[es:Lista de glitches de la tercera generación]] | ||
[[fr:Liste des bugs de la troisième génération]] | [[fr:Liste des bugs de la troisième génération]] | ||
[[it:Elenco glitch | [[it:Elenco glitch in terza generazione]] | ||
[[zh:遊戲漏洞（第三世代）]] | [[zh:遊戲漏洞（第三世代）]] | ||