H POKé: Difference between revisions

m
no edit summary
mNo edit summary
Line 30: Line 30:
[[File:RBGlitchNameC3.png]] ([[List of Japanese Pokémon names|Japanese]]: '''アム''' ''Amu'') is a dual-type {{2t|Ghost|Poison}} [[Glitch Pokémon]], found in {{game|Red and Blue|s}}.
[[File:RBGlitchNameC3.png]] ([[List of Japanese Pokémon names|Japanese]]: '''アム''' ''Amu'') is a dual-type {{2t|Ghost|Poison}} [[Glitch Pokémon]], found in {{game|Red and Blue|s}}.


[[File:RBGlitchNameC3.png]] can be encountered via Method #3 of the [[Mew Glitch]], with a special stat of '''195'''. [[File:RBGlitchNameC3.png]] is a relatively safe glitch Pokémon to use, as it is a hybrid of {{p|Gengar}}, but it can be difficult to catch and train because normally when [[File:RBGlitchNameC3.png]] is caught, its [[Pokédex]] data (which consists of chaotic [[glitch song#chaotic|glitch song]]s and visual glitches) will lock up the game. The frozen [[Pokédex]] data can be avoided if the Trainer catching [[File:RBGlitchNameC3.png]] has a {{p|Gengar}} registered in their [[Pokédex]] as "owned". A Red/Blue player can also have a [[ゥ ( Z4]] ([[File:RBGlitchNameC3.png]]'s Yellow version equivalent) traded from Yellow.  
[[File:RBGlitchNameC3.png]] can be encountered via Method #3 of the [[Mew Glitch]], with a special stat of '''195'''. [[File:RBGlitchNameC3.png]] is a relatively safe glitch Pokémon to use, as it is a hybrid of {{p|Gengar}}, but it can be difficult to catch and train because normally when [[File:RBGlitchNameC3.png]] is caught, its [[Pokédex]] data (which consists of chaotic [[glitch song#chaotic|glitch song]]s and visual glitches) will lock up the game. The frozen [[Pokédex]] data can be avoided if the Trainer catching [[File:RBGlitchNameC3.png]] has a {{p|Gengar}} registered in their [[Pokédex]] as "owned". A Red/Blue player can also have a [[ゥ ( Z4]] ([[File:RBGlitchNameC3.png]]'s Yellow version equivalent) traded from Yellow.  


[[File:RBGlitchNameC3.png]]'s [[cry]] is long, glitched, and different every time its stats are checked, depending on the last cry heard. On rare occasions, [[File:RBGlitchNameC3.png]]'s cry may freeze the game.
[[File:RBGlitchNameC3.png]]'s [[cry]] is long, glitched, and different every time its stats are checked, depending on the last cry heard. On rare occasions, [[File:RBGlitchNameC3.png]]'s cry may freeze the game.
Line 164: Line 164:
* [[File:RBGlitchNameC3.png]]'s [[cry]] changes depending on the last Pokémon's cry played. Because this includes its own cry, viewing its stats multiple times in succession can cause long glitchy strings of sound, sometimes minutes long. Sometimes its cry never even ends, effectively locking up the game.
* [[File:RBGlitchNameC3.png]]'s [[cry]] changes depending on the last Pokémon's cry played. Because this includes its own cry, viewing its stats multiple times in succession can cause long glitchy strings of sound, sometimes minutes long. Sometimes its cry never even ends, effectively locking up the game.
* [[File:RBGlitchNameC3.png]], when compared to all other Pokémon, is tied with [[♀ .]] for being the [[List of Pokémon by height|tallest]] Pokémon.
* [[File:RBGlitchNameC3.png]], when compared to all other Pokémon, is tied with [[♀ .]] for being the [[List of Pokémon by height|tallest]] Pokémon.
* With 6,099 lbs (2766.5 kg), [[File:RBGlitchNameC3.png]] can be considered as the heaviest Pokémon which can be obtained without the use of a [[cheating]] device.
* With 6,099 lbs (2766.5 kg), [[File:RBGlitchNameC3.png]] can be considered as the heaviest Pokémon which can be obtained without the use of a [[cheating]] device.


==External links==
==External links==