Glitch battle: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
m (It said pokemon instead of Pokémon)
(→‎Examples: fixed)
(14 intermediate revisions by 11 users not shown)
Line 1: Line 1:
A '''Glitch battle''' is a type of battle in which a [[glitch Pokémon]] initaites. It is when the glitch Pokémon completely corrupts all of the games data values and turns them random.  
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.


==Events==
==Effects==
#Whole screen scrambles shortly
 
#Player is withdrawn
Glitch battles most commonly follow a constant string of events:
#{{tt|Glitch block|This is not the same as a glitch Pokémon. It is simply corrupted data, not a real Pokémon.}} is sent out.
 
#Glitch block faints
# The screen tiles graphics get scrambled, as a result of corrupting the screen data. This step may not happen every time.
#Nothing is sent out
# 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.
#[[Game freeze]]s
# 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.


==Effects==
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.
*Enemy HP is randomized
 
**Player's is gone
==Examples==
*Enemy receives a random status ailment.
 
*Random text appears, covering parts of the screen.
* [[4(h4?]] is the most appropriate example, since its encounter sequence clearly showcases all features of a glitch battle.  
*Music cuts out and is replaced by droning.
* [[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]].
*User sends out a {{tt|glitch block|Again, this is not the same as a glitch pokemon. It is simply corrupted data, not a real Pokémon.}}
* [[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.
*Eventually causes the game to freeze.
* [[♀ .]] 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.


==Gallery==
==Gallery==
<gallery widths="160px" heights="144px" perrow="2">
<gallery>
File:Glitchbattle.png| A glitch battle
File:Glitchbattle.png| [[4(h4?]]'s glitch battle, after screen corruption.
File:Glitchbattle2.png| A glitch block in play
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>
</gallery>


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


{{Glitches}}<br>
{{Glitches}}<br>

Revision as of 01:40, 16 August 2015

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 memory corruption. Glitch battles often feature a series of unpredictable effects. Every glitch battle eventually causes the game to 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's and Missingno.'s Hall of Fame data corruption.

Effects

Glitch battles most commonly follow a constant string of events:

  1. The screen tiles graphics get scrambled, as a result of corrupting the screen data. This step may not happen every time.
  2. The game refreshes the corrupted values and makes the changes visible. This includes Pokémon receiving random status conditions, opponent name changing, or glitchy strings of text appearing on the screen.
  3. 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.
  4. 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.
  5. Eventually, the game 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 Pokémon Red and Blue'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 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.
  • 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.
  • Certain glitch Pokémon, like PkMnaPkMnゥ ♂ fPkMnk, crash the game instantly and do not give enough time to see any glitch battle effects.

Gallery

Video

By Krauser912
This video is not available on Bulbapedia; instead, you can watch the video on YouTube here.


By Missingno3000
This video is not available on Bulbapedia; instead, you can watch the video on YouTube here.



Multiple
generations
Transform glitchesGlitch TrainersCloning glitchesError messagesArbitrary code execution
Generation I GlitchesBattle glitchesOverworld glitches
--0 ERRORBroken hidden itemsCable Club escape glitchDual-type damage misinformation
Experience underflow glitchFight Safari Zone Pokémon trickGlitch CityItem duplication glitchItem underflow
Mew glitchOld man glitchPewter Gym skip glitchPokémon merge glitchRhydon glitchRival twins glitch
Select glitches (dokokashira door glitch, second type glitch) • Super Glitch
Time Capsule exploitWalking through wallsZZAZZ glitch
Generation II GlitchesBattle glitches
Bug-Catching Contest glitchCelebi Egg glitchCoin Case glitchesExperience underflow glitch
Glitch dimensionGlitch EggTeru-samaTime Capsule exploitTrainer House glitchesGS Ball mail glitch
Generation III GlitchesBattle glitches
Berry glitchDive glitchPomeg glitchGlitzer Popping
Generation IV GlitchesBattle glitchesOverworld glitches
Acid rainGTS glitchesPomeg glitchRage glitch
Surf glitchTweakingPal Park Retire glitch
Generation V GlitchesBattle glitchesOverworld glitches
Charge Beam additional effect chance glitchCharge move replacement glitchChoice item lock glitch
Frozen Zoroark glitchSky Drop glitch
Generation VI GlitchesBattle glitchesOverworld glitches
Charge Beam additional effect chance glitchCharge move replacement glitchChoice item lock glitch
Lumiose City save glitchSymbiosis Eject Button glitchToxic sure-hit glitch
Generation VII GlitchesBattle glitches
Charge Beam additional effect chance glitchCharge move replacement glitchChoice item lock glitch
Toxic sure-hit glitchRollout storage glitch
Generation VIII Glitches
Charge Beam additional effect chance glitchCharge move replacement glitchChoice item lock glitch
Toxic sure-hit glitchRollout storage glitchParty item offset glitch
Generation IX Glitches
Glitch effects Game freezeGlitch battleGlitch song
Gen I only: Glitch screenTMTRAINER effectInverted sprites
Gen II only: Glitch dimension
Lists Glitches (GOMystery DungeonTCG GBSpin-off)
Glitch Pokémon (Gen IGen IIGen IIIGen IVGen VGen VIGen VIIGen VIII)
Glitch moves (Gen I) • Glitch types (Gen IGen II)


Project GlitchDex logo.png This article is part of Project GlitchDex, a Bulbapedia project that aims to write comprehensive articles on glitches in the Pokémon games.