Roaming Pokémon Roar glitch: Difference between revisions
>Torchickens (Need a little confirmation about exact details, will try and work through firered) |
>Torchickens mNo edit summary |
||
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Misc Gen 3}} |
{{Misc Gen 3}} |
||
{{Bulbapedia2|List of minor glitches#Roaming Pokémon glitch 2}} |
{{Bulbapedia2|List of minor glitches#Roaming Pokémon glitch 2}} |
||
{{Researchneeded|Check if this occurs in Japanese {{RS}} with the [[Latias and Latios glitch]].}} |
|||
{{clr}} |
|||
The '''Roaming Pokémon Roar glitch''' (not to be confused with the [[Roaming Pokémon IV glitch]]) is a relatively minor [[glitch]] that occurs with the [[bp:Roaming Pokémon|Roaming]] [[bp:Legendary Beasts|Legendary Beasts]] in {{FRLG}}. |
|||
Usually when one of the [[bp:Legendary Beasts|Legendary Beasts]] flees, it should still be available but may have moved to a different route. |
|||
The '''Roaming Pokémon Roar glitch''', sometimes shortened as the '''Roaming Pokémon glitch''' but not to be confused with the [[Roaming Pokémon individual values issue]] is a relatively minor [[glitch]] present within the [[bp:Generation III|Generation III]] Pokémon games, however through normal gameplay it only exists within Pokémon FireRed and LeafGreen because in those games, Raikou and Entei are the only Pokémon naturally capable of learning [[bp:Roar|Roar]] by levelling up. |
|||
However, if one of the Legendary Beasts uses Roar it will cause the Pokémon to become unavailable. |
|||
Usually when one of the [[bp:Legendary Beasts|Legendary Beasts]] flees, it should still exist within the game but would have fleed to a different route. If one of the Legendary Beasts uses Roar however, the game will not set this byte, suggesting that the player has run away or that he or she has defeated the Legendery Beast instead. |
|||
==See also== |
|||
*[[Roaming Pokémon IV glitch]]. |
|||
[[Category:Generation III glitches]] |
Latest revision as of 21:22, 15 September 2016
Exclusive to Ruby and Sapphire:
256x item selling price glitch | Amazing Trainers | Berry glitch | Draining hitpoints animation glitch | Evolution animation glitch | Sticky Hold glitch | Mossdeep City Skitty glitch | Truck glitch | Nightmare glitch | Mossdeep City Skitty glitch
Acro Bike instability glitches (Japanese only) | Dark red selector glitch (International only) | Excessive doll arrangement glitch (Japanese only) | Mail and Trick glitches (Japanese only) | Surf on land (Japanese only)
Exclusive to FireRed and LeafGreen:
Celadon City origin glitch | Pokédex species glitch | Roaming Pokémon Roar glitch
Exclusive to Emerald:
Battle Pike poison knockout glitch | Black curtains glitch | Mart worker glitch | Mover Vigoroth cry glitch (Japanese only)
In various or all entries:
Azurill gender glitch | Boss HP recruit glitch (Mystery Dungeon) | Decamark-specific glitches | Dewford Gym footprint glitch | Evolution move-learning glitch | Focus Punch glitch | Roaming Pokémon IV glitch | Sky Pillar glitch | Thunderbolt glitch | VBlank RNG interrupt glitch
Bulbapedia also has an article about Roaming Pokémon Roar glitch. |
More research is needed for this article.
| |
Reason given: Check if this occurs in Japanese Pokémon Ruby and Sapphire with the Latias and Latios glitch. |
The Roaming Pokémon Roar glitch (not to be confused with the Roaming Pokémon IV glitch) is a relatively minor glitch that occurs with the Roaming Legendary Beasts in Pokémon FireRed and LeafGreen.
Usually when one of the Legendary Beasts flees, it should still be available but may have moved to a different route.
However, if one of the Legendary Beasts uses Roar it will cause the Pokémon to become unavailable.