100
edits
Talk:ZZAZZ glitch: Difference between revisions
technical info yay
Chickasaurus (talk | contribs) No edit summary |
HyperHacker (talk | contribs) (technical info yay) |
||
| Line 1: | Line 1: | ||
I read this on Glitchcity.info: "BTW, there's a pattern to this glitch: Bulbasaur is HEX 153, Explosion is HEX 153, the letter Z is HEX 153, and the Bulbasaurs are Level 153. The glitch just sets all of the game's variables to HEX 153. Also for some reason the Pokemon, the third letter in your name, and the third move in you Pokemon's move set are spared. three is the magic number." This should be mentioned.[[User:Kiryu|Kiryu]] 00:19, 2 February 2009 (UTC) | I read this on Glitchcity.info: "BTW, there's a pattern to this glitch: Bulbasaur is HEX 153, Explosion is HEX 153, the letter Z is HEX 153, and the Bulbasaurs are Level 153. The glitch just sets all of the game's variables to HEX 153. Also for some reason the Pokemon, the third letter in your name, and the third move in you Pokemon's move set are spared. three is the magic number." This should be mentioned.[[User:Kiryu|Kiryu]] 00:19, 2 February 2009 (UTC) | ||
:It's interesting that 153 = 0x99, as the game does use Binary-Coded Decimal for some values; for example your money ($999,999 = 99 99 99 rather than 0x0F423F). However I think this is a coincidence. From a technical standpoint, this glitch overwrites several areas of memory with two different patterns. Your Pokémon's stats all become 153, which (being 16-bit values) indicate the entire status block is overwritten with the byte pattern 0099. However your name becomes ZZxZZxZZxZZx (where x is unchanged), which indicates that block is overwritten with a different pattern: write two bytes of 99, then skip one. | |||
:Having played with the game code a fair bit, this seems familiar to me: I suspect it's actually the graphic decompression routine gone out of control due to the Pokémon having garbage graphic data. The graphic compression routines include commands such as "fill with 2-byte pattern" (0099 in this case) and "fill with byte, skipping every third." These exactly match the symptoms. Another hint is that it corrupts the player's trainer and Pokémon graphics - the first place an out-of-control graphic decompression routine is going to trash is the other graphics right nearby. [[User:HyperHacker|HyperHacker]] 03:45, 16 December 2009 (UTC) | |||
What exactly are the Yellow variations of this glitch? This can be answered by putting the Yellow variations on the page.--[[User:Dragonbeastx|<font color="blue">DRAGON</font>]][[User talk:Dragonbeastx|<font color="yellow">BEAST</font>]][[User:Dragonbeastx/The Aura Spot|<font color="red"><sup>X</sup></font>]] 07:05, 23 February 2009 (UTC) | What exactly are the Yellow variations of this glitch? This can be answered by putting the Yellow variations on the page.--[[User:Dragonbeastx|<font color="blue">DRAGON</font>]][[User talk:Dragonbeastx|<font color="yellow">BEAST</font>]][[User:Dragonbeastx/The Aura Spot|<font color="red"><sup>X</sup></font>]] 07:05, 23 February 2009 (UTC) | ||