ZZAZZ glitch: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
No edit summary
(Added a video link to Jacred (ZZAZZ variant))
(47 intermediate revisions by 30 users not shown)
Line 1: Line 1:
[[Image:GlitchTrainer3.PNG|thumb|right|The [[Glitch Trainer]] encountered using method #3 of the [[Mew glitch]] with a special stat of 252, triggering the ZZAZZ glitch]]
[[File:ZZAZZ.png|200px|thumb|right|The player encounters one of several [[glitch Trainer]]s which can trigger the ZZAZZ glitch.]]
The '''ZZAZZ glitch''' is a [[glitch]] found in the [[Generation I]] {{pkmn|games}}. It is encountered by using the [[Mew glitch]] that has a decimal number of 251, 252, 254 or 255. This makes the {{player}} encounter a glitch {{pkmn|Trainer}} that in turn allows this glitch to occur. Attempting to attack this trainer will cause the game to crash, but the player can escape by using an item.


One trait of this glitch is that it causes one of the opponent's Pokémon, usually a [[Charizard 'M]], to have an extremely high amount {{stat|HP}}. This is also a side-effect of using {{m|Super Glitch}}.
The '''ZZAZZ glitch''' is a data-corrupting [[glitch]] found in the [[Generation I]] {{pkmn|games}}. It can be triggered by using the {{DL|Mew glitch|Ditto glitch}} with a {{stat|Special}} stat of 251, 252, 254 or 255. This makes the {{player}} encounter a [[glitch Trainer]] that in turn causes this glitch to occur.


A side effect of ZZAZZ causes the trainer's name to become replaced with one that is much longer, composed mostly of A's and Z's. It also causes the [[Pokémon]] in the player's party to become glitchy as well, in addition to the player's sprite. Additionally, it makes three of the Pokémon's moves {{m|Explosion}}. Another known effect is that some or all of the player's Pokémon turn into {{p|Bulbasaur}}. A possible explanation to this is that the glitch overwrites certain variables with the hex value 99, since the hex value equals to 'Z' as a character, Explosion as a move and Bulbasaur as a Pokémon.
The glitch is directly caused by a multiplication routine used to calculate the amount of [[money]] awarded at the end of the battle. As money in Generation I is stored as {{wp|binary-coded decimal}}, the game must perform several arithmetic functions in order to load the proper value into memory; as part of this loading, the game attempts to ensure that the money value is capped at {{PDollar}}9999. However, since the glitch Trainers encountered have an invalid money value unlike normal {{pkmn|Trainer}}s, the arithmetic functions fail to behave as expected, corrupting a pointer and causing the byte 0x99 to be written to the first two out of every three bytes each time the calculated award would exceed {{PDollar}}9999 after the first. For the Trainers that trigger the ZZAZZ glitch, this happens over two hundred times, destroying many important game variables.


Although the player's name will glitch, the [[OT]] values of the party Pokémon will stay the same, tricking the game into thinking that they are not the player's. The combination of this, and the Pokémon's levels being at 153, causes them to disobey the trainer (as not even the [[Earth Badge]] is programmed to make Pokémon over level 100 obey the player.) On top of this, checking the Pokémon menu will usually cause the game to freeze.  
The glitch Trainer is usually seen sending out a [[level]] 153 [['M (FF)]]{{sup/1|RB}} or a [[Q ◣]]{{sup/1|Y}} with an extremely long {{stat|Hit Points|HP}} bar; attempting to use a [[move]] or even just view the [[party]] will cause the game to freeze due to the corruption. However, the Trainer can be easily escaped by using any [[item]] (as long as it does not display the party, such as a [[Poké Ball]]); doing so automatically causes the battle to end (also due to the corruption). During and after the battle the player can see that every Pokémon in their party except each third one has been changed to a level 153 {{p|Bulbasaur}} whose first, second, and fourth moves are all {{m|Explosion}}; the player's name except for every third letter has also been overwritten with capital Z's (hence the name of the glitch). All of these correspond to index number 0x99.


Any Trainer battle fought during the glitch will become a battle against a glitch trainer with the player's sprite. He will either borrow the player's original name, their ZZAZZ-glitched name, or sometimes a different glitched name. His party will consist mainly of [[Charizard 'M]]s, and he is unbeatable, because at some point he will send out a Charizard 'M that has a glitched HP bar that can never be depleted.
Less immediately noticeable effects of the widespread corruption include changes to in-game interfaces such as the [[menu]]. If a player attempts to [[save]] the game, the cursor scrolls over 'yes' and 'no' causing the game to crash. Although the player's name has been corrupted, the [[Original Trainer|OT]] values of the party Pokémon have not, causing them to be treated as [[outsider Pokémon]]. Combined with the fact that most of them are level 153, they will always disobey the the player (as not even the {{badge|Earth}} is programmed to make Pokémon over level 100 obey).


The abnormalities listed above occur in {{game|Red and Blue|s}}; the {{v|Yellow}} abnormalities which occur are different.
If the player attempts to battle a regular Trainer after triggering the glitch, that Trainer will become a glitch Trainer with the player's sprite. Their name will either be the player's original name, their ZZAZZ-glitched name, or sometimes a different glitched name, and their party will again consist mainly of several [['M (FF)]] or [[Q ◣]]. Attempting to battle this Trainer will not outright cause the game to crash, although attempting to view the player's party still will. Using items will not end the battle this time. The Trainer is almost impossible to defeat, as the player's Pokémon will not obey (and/or will [[faint]] themselves with Explosion, causing the party menu to appear and crash the game), and at least one of the Trainer's level 153 Pokémon has an extremely large amount of HP.
 
The corrupted menu can be partially fixed by talking to a [[Pokémon Center]] nurse, allowing the player to save the game; saving is also possible via changing [[PC]] [[Pokémon Storage System|boxes]]. Doing so is very hazardous, as if the player's name is longer than 10 characters (likely due to the corruption), the save file will be destroyed, forcing the player to start a new game. This can be mitigated by having a name exactly 2, 5, or 8 characters long, as since every third character is not corrupted, the terminating 0x50 character at position 3, 6, or 9 will stop the name from extending.
 
There is also a ZZAZZ variant of [[Glitch Trainer|Jacred]], caused by using the Ditto glitch with a Special stat of 200 and Growl one or two times. Because this is a ZZAZZ variant, battles can be escaped using a Poké Ball, though the [[Bag]] will be corrupted. The screen is almost fully covered by PokéTrainer, but it is still possible to scroll down over Cancel, find a Poké Ball, and escape the battle. After escaping the battle, the player will be in a different Glitch City. The game will not be able to be saved, because when the party is opened, the game will lock. The city has no PC to indirectly save the game, nor a Pokémon Center where the save option can be restored by healing the player's party.
 
{{youtubevid|5hjoHakpe_c|Pokéfan95|Glitch}}
 
==Video==
{{youtubevid|D3iVFfKjklk|Newopkmn|Glitch}}


==External link==
*[http://www.youtube.com/watch?v=D3iVFfKjklk Video of the ZZAZZ Glitch]
{{Glitches}}
{{Glitches}}
[[Category:Glitches]]
{{Project GlitchDex notice|no}}
 
[[fr:ZZAZZ bug]]

Revision as of 06:30, 6 April 2015

The player encounters one of several glitch Trainers which can trigger the ZZAZZ glitch.

The ZZAZZ glitch is a data-corrupting glitch found in the Generation I games. It can be triggered by using the Ditto glitch with a Special stat of 251, 252, 254 or 255. This makes the player encounter a glitch Trainer that in turn causes this glitch to occur.

The glitch is directly caused by a multiplication routine used to calculate the amount of money awarded at the end of the battle. As money in Generation I is stored as binary-coded decimal, the game must perform several arithmetic functions in order to load the proper value into memory; as part of this loading, the game attempts to ensure that the money value is capped at $9999. However, since the glitch Trainers encountered have an invalid money value unlike normal Trainers, the arithmetic functions fail to behave as expected, corrupting a pointer and causing the byte 0x99 to be written to the first two out of every three bytes each time the calculated award would exceed $9999 after the first. For the Trainers that trigger the ZZAZZ glitch, this happens over two hundred times, destroying many important game variables.

The glitch Trainer is usually seen sending out a level 153 'M (FF)RB or a Q ◣Y with an extremely long HP bar; attempting to use a move or even just view the party will cause the game to freeze due to the corruption. However, the Trainer can be easily escaped by using any item (as long as it does not display the party, such as a Poké Ball); doing so automatically causes the battle to end (also due to the corruption). During and after the battle the player can see that every Pokémon in their party except each third one has been changed to a level 153 Bulbasaur whose first, second, and fourth moves are all Explosion; the player's name except for every third letter has also been overwritten with capital Z's (hence the name of the glitch). All of these correspond to index number 0x99.

Less immediately noticeable effects of the widespread corruption include changes to in-game interfaces such as the menu. If a player attempts to save the game, the cursor scrolls over 'yes' and 'no' causing the game to crash. Although the player's name has been corrupted, the OT values of the party Pokémon have not, causing them to be treated as outsider Pokémon. Combined with the fact that most of them are level 153, they will always disobey the the player (as not even the Earth Badge is programmed to make Pokémon over level 100 obey).

If the player attempts to battle a regular Trainer after triggering the glitch, that Trainer will become a glitch Trainer with the player's sprite. Their name will either be the player's original name, their ZZAZZ-glitched name, or sometimes a different glitched name, and their party will again consist mainly of several 'M (FF) or Q ◣. Attempting to battle this Trainer will not outright cause the game to crash, although attempting to view the player's party still will. Using items will not end the battle this time. The Trainer is almost impossible to defeat, as the player's Pokémon will not obey (and/or will faint themselves with Explosion, causing the party menu to appear and crash the game), and at least one of the Trainer's level 153 Pokémon has an extremely large amount of HP.

The corrupted menu can be partially fixed by talking to a Pokémon Center nurse, allowing the player to save the game; saving is also possible via changing PC boxes. Doing so is very hazardous, as if the player's name is longer than 10 characters (likely due to the corruption), the save file will be destroyed, forcing the player to start a new game. This can be mitigated by having a name exactly 2, 5, or 8 characters long, as since every third character is not corrupted, the terminating 0x50 character at position 3, 6, or 9 will stop the name from extending.

There is also a ZZAZZ variant of Jacred, caused by using the Ditto glitch with a Special stat of 200 and Growl one or two times. Because this is a ZZAZZ variant, battles can be escaped using a Poké Ball, though the Bag will be corrupted. The screen is almost fully covered by PokéTrainer, but it is still possible to scroll down over Cancel, find a Poké Ball, and escape the battle. After escaping the battle, the player will be in a different Glitch City. The game will not be able to be saved, because when the party is opened, the game will lock. The city has no PC to indirectly save the game, nor a Pokémon Center where the save option can be restored by healing the player's party.

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


Video

By Newopkmn
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.