View source for Glitch battle

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==

Glitch battles most commonly follow a constant string of events:

# The screen tiles get scrambled, as a result of corrupting the screen data. This step may not happen every time.
# The game refreshes the corrupted values and makes the changes visible. This includes Pokémon receiving random [[status condition]]s, opponent name changing, or glitchy strings of text appearing on the screen.
# Music usually fades into a single sound, or is replaced with static or a low pitched droning noise. Sometimes the low HP beeping loop will start to play for no reason.
# The game will try operating on the corrupted values. It may include sending out nonexistent glitch Pokémon, or trying to continue the battle in a glitched state.
# 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 [[Missingno.]], whose sprite slightly corrupts the save data by corrupting the Hall of Fame records, but does not destroy any important information.

==Examples==

* [[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 glitches up 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 severely messes up the music and affects graphics after returning to overworld. Other than that, it's completely safe.
* [[♀ .]] slightly corrupts some memory addresses responsible for music and graphics, but 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.

==Gallery==
<gallery>
File:Glitchbattle.png| [[4(h4?]]'s glitch battle, after screen corruption.
File:Glitchbattle2.png| [[4(h4?]]'s glitch battle, the game trying to continue the battle.
File:YGlitch250_encounter.png| Encountering [[4 4]] via [[Mew glitch]].
File:YGlitch250_battle.png| Encountering [[4 4]] in a trainer battle.
</gallery>

==Video==
{{youtubevid|UbiYeciV_LE|Krauser912|???}}

{{youtubevid|cyojMBQ81lg|Missingno3000|???}}

{{Glitches}}<br>
{{Project Glitchdex notice|no}}

[[Category:Glitch effects]]