♀ .: Difference between revisions

♀ . (view source)

Revision as of 11:34, 8 May 2015

3 bytes removed , 8 May 2015

I'm fairly certain that the glitchy sounds it causes are a result of memory corruption, and that its actual cry is just that of Raticate's.

Selvah

88

edits

@@ Line 34: / Line 34: @@
 [[File:YGlitchNameC1.png|link=]] can be obtained by doing Method #3 of the [[Mew glitch]] with a Pokémon with a special stat of '''193''', by trading a [[ゥ (C1)]] from {{game3|Red and Blue|Red/Blue|s}} to Yellow, or via the [[Johto guard glitch]] with {{p|Meganium}}.
-The Pokédex number for [[File:YGlitchNameC1.png|link=]] is #205, which makes this glitch's National Pokédex equivalent {{p|Forretress}}. [[File:YGlitchNameC1.png|link=]] will usually [[game freeze|freeze]] the player's game when it is encountered using the Mew glitch due to its extremely long cry (its length varies from encounter to encounter; its cry has been sped up but the end of it has never been reached, so it may just be a continuous loop). Its Red/Blue equivalent, ゥ, also freezes the game. On rare occasions, [[File:YGlitchNameC1.png|link=]] may appear without freezing.
+The Pokédex number for [[File:YGlitchNameC1.png|link=]] is #205, which makes this glitch's National Pokédex equivalent {{p|Forretress}}. When encountered, [[File:YGlitchNameC1.png|link=]] seems to corrupt parts of the game's memory responsible
+for sound, as it will terminate the battle music and load for a considerable time (longer than [[Missingno.]]) before appearing. [[File:YGlitchNameC1.png|link=]] can also replace the battle music with never-ending glitchy sounds that don't allow its cry (which is identical to {{p|Raticate}}'s) to play, effectively locking up the game.
 [[File:YGlitchNameC1.png|link=]]'s Pokédex entry can be bypassed by having seen a {{p|Haunter}}.