Jump to content

GlitchDex/RB:000: Difference between revisions

>Torchickens
No edit summary
 
(7 intermediate revisions by 3 users not shown)
Line 1:
{{GPInfoGenIRB
{{GPInfoGenI
|name='M (00) [[File:MS Man RB.png]]
|frontsprite=Front: GB=[[File:MissingNo. RB GB.png]]
|backspriteFront Gray=Back: [[File:RB Backsprite FamilyMissingNo. 000Gray.png]]
|Front GBC R=[[File:MissingNo. R GBC.png]]
|Front GBC B=[[File:MissingNo. B GBC.png]]
|Front SGB=[[File:MissingNo. RB SGB.png]]
|Back GB=[[File:R Backsprite Family 000 GB.png]]
|Back Gray=[[File:R Backsprite Family 000 Gray.png]]
|Back GBC R=[[File:R Backsprite Family 000 GBC.png]]
|Back GBC B=[[File:B Backsprite Family 000 GBC.png]]
|Back SGB=[[File:RB Backsprite Family 000 SGB.png]]
|bulbapedia=[[bp:'M (00)|'M (00)]]
|equivalent={{gdex|Y:000|3TRAINERPOKé₽ ({{CYellow|Yellow}})}}
Line 57 ⟶ 65:
==Evolution(s)==
 
{{Evolution2S|1=[[File:RBGlitch211.png|link=GlitchDex/RB:225]]<br>[[GlitchDex/RB:225|'v (hex:E1)]]|C=<br>Level 56|2=[[File:MissingNo. RB SGB.png]]<br>'M (00)}}
 
{{Evolution2S|1=[[File:RBGlitch081.png|link=GlitchDex/RB:252]]<br>[[GlitchDex/RB:252|O (hex:FC)]]|C=<br>Level 56|2=[[File:MissingNo. RB SGB.png]]<br>'M (00)}}
 
{{Evolution2S|1=[[File:MissingNo. RB SGB.png]]<br>[[GlitchDex/RB:000|'M (00)]]|C=<br>Level 1|2=[[File:RB Kangaskhan front.png]]<br>KANGASKHAN (02)}}
 
{{Evolution2S|1=[[File:MissingNo. RB SGB.png]]<br>[[GlitchDex/RB:000|'M (00)]]|C=<br>Level 128|2=[[File:RB Clefairy front.png]]<br>CLEFAIRY (04)}}
 
==Pokédex data==
Line 101 ⟶ 109:
{{BasestatsGenI
|HP=33
|Attack=137136
|Defense=0
|Special=296
|Speed=629
|HPL50Range=93-139
|AttackL50Range=142141-188187
|DefenseL50Range=5-51
|SpecialL50Range=3411-8057
|SpeedL50Range=1134-5780
|HPL100Range=176-269
|AttackL100Range=279277-372370
|DefenseL100Range=5-98
|SpecialL100Range=6317-156110
|SpeedL100Range=1763-110156
}}
 
 
==Notes==
'M (00) and [[MissingNo.]] in Red/Blue are actually the only English glitch Pokémon to be part [[Bird type|Bird-type]]. The Bird-type is an unused type not to be confused with Flying-type that never made it into the final game.
 
When the player catches 'M (00), the battle will continue as if it hasn't been caught, but the "enemy Pokémon transformed" flag will be set, meaning that if it is caught again, it will [[Transform assumption glitch|become a Ditto]] and the battle will end. This is due to the battle engine using $D11C ($D11B in Yellow) to determine if the battle should end because the enemy has been caught. This address is initialized to 0 and then set to the index number of the caught Pokémon, so catching 'M (00) will not change it. However, the "enemy Pokémon transformed" flag is always set when a wild Pokémon is caught, so the next time a Ditto is caught instead, allowing the battle to end.<ref>[https://www.youtube.com/watch?v=Z_z4FOz0Yzo Three unexplained side effects of Pokemon glitches] by Crystal_</ref>
When you initiate a battle with 'M (00), the battle will continue after catching it, but not defeating it. If "'M" is captured again, the battle will truly end and the Pokémon will become Ditto.
 
Since 'M (00)'s Pokédex number is 000, it is considered Pokémon #256. This glitch Pokémon is popular for the duplication of item #6 in the inventory. Upon encountering 'M (00) the game will look up its encounter flag beyond the end of the table and 'register the glitch Pokémon as seen in the Pokédex' by adding 128 to item #6's quantity (if already less than 128). Specifically this sets bit 0x7 of address D329.
 
== References ==
<references />
 
[[Category:GlitchDex articles]]
Cookies help us deliver our services. By using our services, you agree to our use of cookies.