Anonymous user
Stable unstable MissingNo.: Difference between revisions
no edit summary
>Torchickens |
>Torchickens No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
Line 3:
'''Stable unstable MissingNo.''' is a specific iteration of a [[glitch battle]] in English {{Yellow}}, describing how usually regular [[MissingNo.|Yellow MissingNo.]] will never freeze the game if encountered on real hardware from a save file wiped with Up+Select+B. The save file must also have not encountered other glitch Pokémon with problematic sprites (such as some which cause [[Hall of Fame corruption]]), or had the SRAM tampered with in other ways.
This type of glitch battle was documented by the Pokémon Speedruns community, and it is useful for [[glitch]]es that require [[unterminated name glitch Pokémon]], such as [[oobLG]] (within Generation I) and [[0x1500 control code arbitrary code execution]] for Pokémon traded into Generation II. It is also useful for [[item duplication]] and its sub-glitches, such as [[dry underflow glitch]].
The name of this glitch is an oxymoron. Fossil/Ghost MissingNo. (IDs 182-184) are often called "stable MissingNo.", yet unstable MissingNo. (that can be invoked using other IDs), while with a high chance of freezing the game, do not necessarily freeze
==Specifics of the glitch battle and activation==
| |||