53,544
edits
Glitch battle: Difference between revisions
m
clean up
SlySamurott (talk | contribs) (→Examples: fixed) |
m (clean up) |
||
| Line 1: | Line 1: | ||
A '''Glitch battle''' is a type of battle which a [[glitch Pokémon]] initiates. It happens when an encounter starts with a glitch Pokémon whose sprite causes {{wp|memory corruption}}. Glitch battles often feature a series of unpredictable effects. Every glitch battle eventually causes the game to [[Game freeze|freeze]]. There exist mild variants of glitch battles, which only corrupt a handful of addresses and do not cause the game to crash - like [['M (00)|'M]]'s and [[ | A '''Glitch battle''' is a type of battle which a [[glitch Pokémon]] initiates. It happens when an encounter starts with a glitch Pokémon whose sprite causes {{wp|memory corruption}}. Glitch battles often feature a series of unpredictable effects. Every glitch battle eventually causes the game to [[Game freeze|freeze]]. There exist mild variants of glitch battles, which only corrupt a handful of addresses and do not cause the game to crash - like [['M (00)|'M]]'s and [[MissingNo.]]'s [[Hall of Fame]] data corruption. | ||
==Effects== | ==Effects== | ||
| Line 11: | Line 11: | ||
# Eventually, the game [[Game freeze|crashes]] in its confusion. | # Eventually, the game [[Game freeze|crashes]] in its confusion. | ||
Some glitch Pokémon sprites corrupt enough memory to affect the game, but do not corrupt enough to make it unplayable. The most common example is {{game|Red and Blue|s}}'s version of [[ | Some glitch Pokémon sprites corrupt enough memory to affect the game, but do not corrupt enough to make it unplayable. The most common example is {{game|Red and Blue|s}}'s version of [[MissingNo.]], whose sprite slightly corrupts the save data by corrupting the Hall of Fame records, but does not destroy any important information. | ||
==Examples== | ==Examples== | ||
* [[4(h4?]] is the most appropriate example, since its encounter sequence clearly showcases all features of a glitch battle. | * [[4(h4?]] is the most appropriate example, since its encounter sequence clearly showcases all features of a glitch battle. | ||
* [[4 4]] crashes the game upon encounter. However, before the game crashes, it is possible to see the glitched battle screen for a brief moment. When it is sent out in a trainer battle, it severely alters the game screen and freezes the game shortly afterwards. It shares these traits with two other glitch Pokémon, [[8B 4 8]] and [[ゥ' B]]. | * [[4 4]] crashes the game upon encounter. However, before the game crashes, it is possible to see the glitched battle screen for a brief moment. When it is sent out in a trainer battle, it severely alters the game screen and freezes the game shortly afterwards. It shares these traits with two other glitch Pokémon, [[8B 4 8]] and [[ゥ' B]]. | ||
* [[ | * [[MissingNo.#Yellow forms|Yellow form MissingNo.]]'s front sprite often crashes or freezes the game. It also heavily alters the music and affects graphics after returning to overworld. | ||
* [[♀ .]] slightly corrupts some memory addresses that are responsible for music and graphics, but generally keeps the game playable. | * [[♀ .]] slightly corrupts some memory addresses that are responsible for music and graphics, but generally keeps the game playable. | ||
* Certain glitch Pokémon, like [[PkMnaPkMnゥ ♂ fPkMnk]], crash the game instantly and do not give enough time to see any glitch battle effects. | * Certain glitch Pokémon, like [[PkMnaPkMnゥ ♂ fPkMnk]], crash the game instantly and do not give enough time to see any glitch battle effects. | ||