Old man glitch: Difference between revisions
m (Rewording) |
m (typos fixed: Pokemon → Pokémon) |
||
Line 1: | Line 1: | ||
The '''old man glitch''' is a well-known [[glitch]] in {{game|Red and Blue|s}}, and an extension of the [[Fight Safari Zone Pokémon trick]]. It is one of the methods by which the [[player character|player]] can encounter [[ | The '''old man glitch''' is a well-known [[glitch]] in {{game|Red and Blue|s}}, and an extension of the [[Fight Safari Zone Pokémon trick]]. It is one of the methods by which the [[player character|player]] can encounter [[MissingNo.]] and [['M (00)]], and almost certainly the most famous method. Its name comes from the {{ka|old man}} in [[Viridian City]], who is required to begin the glitch. It should not be confused with the related [[item duplication glitch]], which is most easily performed by first performing the old man glitch. | ||
This glitch was not present in the Japanese [[Pokémon Red and Green Versions|Pokémon Red, Green]], or {{game|Blue|_(Japanese)}}. This glitch was fixed in some {{wp|European}} versions of Red and Blue, such as the {{pmin|Spain|Spanish}} and {{pmin|Italy|Italian}} versions, by making the shore tiles act as [[water tile]]s, but still remains in other European versions, such as the {{pmin|Germany|German}} version. In the {{pmin|France|French}} version, the glitch is present, but the game freezes every time a [[ | This glitch was not present in the Japanese [[Pokémon Red and Green Versions|Pokémon Red, Green]], or {{game|Blue|_(Japanese)}}. This glitch was fixed in some {{wp|European}} versions of Red and Blue, such as the {{pmin|Spain|Spanish}} and {{pmin|Italy|Italian}} versions, by making the shore tiles act as [[water tile]]s, but still remains in other European versions, such as the {{pmin|Germany|German}} version. In the {{pmin|France|French}} version, the glitch is present, but the game freezes every time a [[MissingNo.]] or [['M (00)]] appears. This glitch was removed in all versions of {{game|Yellow}} by blanking the data for wild Pokémon before overwriting it, and reprogramming shore tiles to not call any [[wild Pokémon]]. | ||
==Performing the glitch== | ==Performing the glitch== | ||
Line 11: | Line 11: | ||
The wild Pokémon that appear are based on the player's name. The third, fifth and seventh slots of the player's name are the species of Pokémon that will appear (see table below). The second slot of the player's name becomes the level of the Pokémon caused to appear by the third slot, the fourth slot for the fifth slot, and the sixth slot for the seventh slot. The game also reads the ninth and eleventh slots as wild Pokémon and the eighth and tenth slots as levels; however, due to the seven character name limit, these slots are not used, so are blank (00), causing [['M (00)]] to appear at level 0. | The wild Pokémon that appear are based on the player's name. The third, fifth and seventh slots of the player's name are the species of Pokémon that will appear (see table below). The second slot of the player's name becomes the level of the Pokémon caused to appear by the third slot, the fourth slot for the fifth slot, and the sixth slot for the seventh slot. The game also reads the ninth and eleventh slots as wild Pokémon and the eighth and tenth slots as levels; however, due to the seven character name limit, these slots are not used, so are blank (00), causing [['M (00)]] to appear at level 0. | ||
At the end of the player's name, there is a special character to mark the end of the name. This character can either cause | At the end of the player's name, there is a special character to mark the end of the name. This character can either cause MissingNo. to appear, or create the possibility for wild 'M (00) to be at level 80. | ||
The eighth through eleventh bytes are only 00 if using a custom name; using a [[#Preset names|preset name]] results in these extra bytes being filled by the series of other preset name separated by end of name markers (with NEW NAME after the last preset name). As such, 'M (00) will not appear when using a preset name. | The eighth through eleventh bytes are only 00 if using a custom name; using a [[#Preset names|preset name]] results in these extra bytes being filled by the series of other preset name separated by end of name markers (with NEW NAME after the last preset name). As such, 'M (00) will not appear when using a preset name. | ||
Line 22: | Line 22: | ||
|- | |- | ||
| | | | ||
{| border=1 width="100%" class="sortable" style="background: # | {| border=1 width="100%" class="sortable" style="background: #FFF; border:1px solid #{{unknown color light}}; border-collapse:collapse;" | ||
|- | |- | ||
! | ! | ||
Line 36: | Line 36: | ||
|{{tt| |end of name marker}} | |{{tt| |end of name marker}} | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|80 | |80 | ||
|- | |- | ||
|{{tt| |space}} | |{{tt| |space}} | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|127 | |127 | ||
|- | |- | ||
Line 76: | Line 76: | ||
|G | |G | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|134 | |134 | ||
|- | |- | ||
|H | |H | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|135 | |135 | ||
|- | |- | ||
Line 91: | Line 91: | ||
|J | |J | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|137 | |137 | ||
|- | |- | ||
Line 106: | Line 106: | ||
|M | |M | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|140 | |140 | ||
|- | |- | ||
Line 136: | Line 136: | ||
|S | |S | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|146 | |146 | ||
|- | |- | ||
Line 186: | Line 186: | ||
|: | |: | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|156 | |156 | ||
|- | |- | ||
Line 201: | Line 201: | ||
|] | |] | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|159 | |159 | ||
|- | |- | ||
|a | |a | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|160 | |160 | ||
|- | |- | ||
|b | |b | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|161 | |161 | ||
|- | |- | ||
|c | |c | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|162 | |162 | ||
|- | |- | ||
Line 266: | Line 266: | ||
|m | |m | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|172 | |172 | ||
|- | |- | ||
Line 276: | Line 276: | ||
|o | |o | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|174 | |174 | ||
|- | |- | ||
|p | |p | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|175 | |175 | ||
|- | |- | ||
Line 311: | Line 311: | ||
|v | |v | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.]] | ||
|181 | |181 | ||
|- | |- | ||
|w | |w | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.#Kabutops Fossil form|MissingNo. (Kabutops Fossil form)]] | ||
|182 | |182 | ||
|- | |- | ||
|x | |x | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.#Aerodactyl Fossil form|MissingNo. (Aerodactyl Fossil form)]] | ||
|183 | |183 | ||
|- | |- | ||
|y | |y | ||
|<center>[[File:AniMS_Missingno_I.png]]</center> | |<center>[[File:AniMS_Missingno_I.png]]</center> | ||
|[[ | |[[MissingNo.#Ghost form|MissingNo. (Ghost form)]] | ||
|184 | |184 | ||
|- | |- | ||
Line 399: | Line 399: | ||
====Pokémon Red==== | ====Pokémon Red==== | ||
The numbers in parentheses are the [[index number]] of the specific [[ | The numbers in parentheses are the [[index number]] of the specific [[MissingNo.]] in hexadecimal. | ||
{| style="margin:auto; background: #{{unknown color light}}; {{roundy|1em}}; border: 5px solid #{{unknown color}};" | {| style="margin:auto; background: #{{unknown color light}}; {{roundy|1em}}; border: 5px solid #{{unknown color}};" | ||
|- | |- | ||
| | | | ||
{| border=1 width="100%" style="background: # | {| border=1 width="100%" style="background: #FFF; border:1px solid #{{unknown color light}}; border-collapse:collapse;" | ||
|- | |- | ||
! Name | ! Name | ||
Line 423: | Line 423: | ||
| {{p|Golduck}} | | {{p|Golduck}} | ||
| 146 | | 146 | ||
| [[ | | [[MissingNo.]] (87) | ||
| 80 | | 80 | ||
| [[ | | [[MissingNo.]] (89) | ||
| 128 | | 128 | ||
| {{p|Golbat}} | | {{p|Golbat}} | ||
Line 431: | Line 431: | ||
| ASH | | ASH | ||
| 146 | | 146 | ||
| [[ | | [[MissingNo.]] (87) | ||
| 80 | | 80 | ||
| [[ | | [[MissingNo.]] (89) | ||
| 128 | | 128 | ||
| {{p|Golbat}} | | {{p|Golbat}} | ||
| 138 | | 138 | ||
| [[ | | [[MissingNo.]] (50) | ||
| 141 | | 141 | ||
| {{p|Snorlax}} | | {{p|Snorlax}} | ||
Line 445: | Line 445: | ||
| {{p|Golbat}} | | {{p|Golbat}} | ||
| 138 | | 138 | ||
| [[ | | [[MissingNo.]] (50) | ||
| 141 | | 141 | ||
| {{p|Snorlax}} | | {{p|Snorlax}} | ||
| 150 | | 150 | ||
| [[ | | [[MissingNo.]] (7F) | ||
| 141 | | 141 | ||
| {{p|Golduck}} | | {{p|Golduck}} | ||
Line 456: | Line 456: | ||
====Pokémon Blue==== | ====Pokémon Blue==== | ||
The numbers in parentheses are the [[index number]] of the specific [[ | The numbers in parentheses are the [[index number]] of the specific [[MissingNo.]] in hexadecimal. | ||
{| style="margin:auto; background: #{{unknown color light}}; {{roundy|1em}}; border: 5px solid #{{unknown color}};" | {| style="margin:auto; background: #{{unknown color light}}; {{roundy|1em}}; border: 5px solid #{{unknown color}};" | ||
|- | |- | ||
| | | | ||
{| border=1 width="100%" style="background: # | {| border=1 width="100%" style="background: #FFF; border:1px solid #{{unknown color light}}; border-collapse:collapse;" | ||
|- | |- | ||
! Name | ! Name | ||
Line 478: | Line 478: | ||
| {{p|Abra}} | | {{p|Abra}} | ||
| 132 | | 132 | ||
| [[ | | [[MissingNo.]] (50) | ||
| 134 | | 134 | ||
| {{p|Golduck}} | | {{p|Golduck}} | ||
Line 484: | Line 484: | ||
| {{p|Starmie}} | | {{p|Starmie}} | ||
| 80 | | 80 | ||
| [[ | | [[MissingNo.]] (87) | ||
|- | |- | ||
| GARY | | GARY | ||
Line 490: | Line 490: | ||
| {{p|Marowak}} | | {{p|Marowak}} | ||
| 152 | | 152 | ||
| [[ | | [[MissingNo.]] (50) | ||
| 137 | | 137 | ||
| {{p|Clefable}} | | {{p|Clefable}} | ||
Line 500: | Line 500: | ||
| JOHN | | JOHN | ||
| 142 | | 142 | ||
| [[ | | [[MissingNo.]] (87) | ||
| 141 | | 141 | ||
| [[ | | [[MissingNo.]] (50) | ||
| 141 | | 141 | ||
| {{p|Snorlax}} | | {{p|Snorlax}} | ||
| 150 | | 150 | ||
| [[ | | [[MissingNo.]] (7F) | ||
| 141 | | 141 | ||
| {{p|Golduck}} | | {{p|Golduck}} | ||
Line 533: | Line 533: | ||
Due to being able to find Pokémon over level 100, it is possible to trigger glitches relating to Pokémon with levels that are too high. If Pokémon over level 100 receives experience by battle, it will automatically go to level 100; Rare Candies will level up the Pokémon normally. If the Pokémon's remaining HP is already low, dropping to level 100 can cause the HP to drop to negative number, but it will be interpreted as a very high number, similarly to the [[Pomeg glitch]]. In {{eng|Pokémon Stadium}}, HP is shown as the actual amount; in [[Pokémon Stadium 2]], it will act as if its HP was full. | Due to being able to find Pokémon over level 100, it is possible to trigger glitches relating to Pokémon with levels that are too high. If Pokémon over level 100 receives experience by battle, it will automatically go to level 100; Rare Candies will level up the Pokémon normally. If the Pokémon's remaining HP is already low, dropping to level 100 can cause the HP to drop to negative number, but it will be interpreted as a very high number, similarly to the [[Pomeg glitch]]. In {{eng|Pokémon Stadium}}, HP is shown as the actual amount; in [[Pokémon Stadium 2]], it will act as if its HP was full. | ||
Reportedly, the first coast exploit discovered involved performing an in-game trade with an NPC and surfing on the coast.<ref>[http://www.gamefaqs.com/gameboy/367023-pokemon-red-version/faqs/38434 Okk's | Reportedly, the first coast exploit discovered involved performing an in-game trade with an NPC and surfing on the coast.<ref>[http://www.gamefaqs.com/gameboy/367023-pokemon-red-version/faqs/38434 Okk's MissingNo. guide]</ref> This results in five level 80 hex:50 MissingNo. because the encounters are affected by the trade Pokémon's [[Original Trainer|OT]] name. Specifically, grass data is overwritten with "5D 50 50 50 50 50 50 50 50 50 50". The 5D byte is a control character that prints "TRAINER" and the rest of the bytes are 'end name' characters. | ||
Trading or fighting in the [[Cable Club]] overwrites the wild | Trading or fighting in the [[Cable Club]] overwrites the wild Pokémon data with the opponent's name, and by using the poison method of the [[Cable Club escape glitch]] one may escape from the Cable Club and keep the stored grass Pokémon data that normally disappears after resetting the game (even after trading). Note that battling heals the user's Pokémon, meaning that the player has to do this glitch by bringing up the trade screen. | ||
This Cable Club coast exploit has an unexplained complication of affecting encounters further than uncommon Pokémon 1 (D891); for example, glitch Trainer FD can appear on the coast through this method. | This Cable Club coast exploit has an unexplained complication of affecting encounters further than uncommon Pokémon 1 (D891); for example, glitch Trainer FD can appear on the coast through this method. |
Revision as of 06:10, 6 March 2016
The old man glitch is a well-known glitch in Pokémon Red and Blue, and an extension of the Fight Safari Zone Pokémon trick. It is one of the methods by which the player can encounter MissingNo. and 'M (00), and almost certainly the most famous method. Its name comes from the old man in Viridian City, who is required to begin the glitch. It should not be confused with the related item duplication glitch, which is most easily performed by first performing the old man glitch.
This glitch was not present in the Japanese Pokémon Red, Green, or Pokémon Blue. This glitch was fixed in some European versions of Red and Blue, such as the Spanish and Italian versions, by making the shore tiles act as water tiles, but still remains in other European versions, such as the German version. In the French version, the glitch is present, but the game freezes every time a MissingNo. or 'M (00) appears. This glitch was removed in all versions of Pokémon Yellow by blanking the data for wild Pokémon before overwriting it, and reprogramming shore tiles to not call any wild Pokémon.
Performing the glitch
The glitch is a special case of the Fight Safari Zone Pokémon trick. To perform the glitch, the player must talk to the old man located in the north of Viridian City and allow him to demonstrate how to catch a Pokémon. After the demonstration, the player should immediately Fly to Cinnabar Island. Here, the player should surf up and down along the east coast of the island where the water is touching the land without leaving Cinnabar Island. Wild Pokémon will appear, based on the player's name.
| |
This video is not available on Bulbapedia; instead, you can watch the video on YouTube here. |
Effects
The wild Pokémon that appear are based on the player's name. The third, fifth and seventh slots of the player's name are the species of Pokémon that will appear (see table below). The second slot of the player's name becomes the level of the Pokémon caused to appear by the third slot, the fourth slot for the fifth slot, and the sixth slot for the seventh slot. The game also reads the ninth and eleventh slots as wild Pokémon and the eighth and tenth slots as levels; however, due to the seven character name limit, these slots are not used, so are blank (00), causing 'M (00) to appear at level 0.
At the end of the player's name, there is a special character to mark the end of the name. This character can either cause MissingNo. to appear, or create the possibility for wild 'M (00) to be at level 80.
The eighth through eleventh bytes are only 00 if using a custom name; using a preset name results in these extra bytes being filled by the series of other preset name separated by end of name markers (with NEW NAME after the last preset name). As such, 'M (00) will not appear when using a preset name.
Results
Custom name
This table demonstrates what Pokémon specific characters in the player's name will cause to appear, or the level of the Pokémon that they will cause to appear. Only characters possible to include in the player's name are included. Glitch Trainers are in bold.
Preset names
Choosing a preset name will result in different results to inputting a custom name. Inputting a custom name which is the same as a preset name will not cause the glitch to behave as if a preset name was chosen.
Preset names function differently because they are stored one after the other in the game data, separated by the end of name marker, whereas custom names are succeeded by zeros after the end of name marker. In English Pokémon Red, the player's name is stored as "RED<end>ASH<end>JACK<end>NEW NAME", starting from the selected name; in English Pokémon Blue, the player's name is stored as "BLUE<end>GARY<end>JOHN<end>NEW NAME", likewise starting from the selected name.
Due to the names extending past the usual seven character limit, the ninth and eleventh characters are also used to determine the wild Pokémon, and their levels are determined by the eighth and tenth characters, respectively. These characters are usually null, so cause 'M (00) to appear, and Pokémon to at level 0, respectively. Because of this, unlike when inputting a custom name, 'M (00) do not appear when using a preset name. Characters after the eleventh are ignored.
Pokémon Red
The numbers in parentheses are the index number of the specific MissingNo. in hexadecimal.
|
Pokémon Blue
The numbers in parentheses are the index number of the specific MissingNo. in hexadecimal.
|
Cause
When the game sets up the battle between the old man and a wild Weedle, it needs to temporarily change the player's name to "OLD MAN" so that it will display that name, rather than the player's entered name, during the battle.
The programmers decided to use the space where data for wild Pokémon found in the grass is stored (which is completely blank in Viridian City, as only Surfing and Fishing data is used) to save the player's name temporarily. Normally, this would cause no abnormal activity, as this data is overwritten when the player moves to a different area.
In all cities, however, this data remains blank, and so the data is never overwritten (as there is nothing new to overwrite it with), and thus, the data that was last entered (be it the player's name or the wild Pokémon data from another area) remains in place. This itself still causes no harm; however, an oversight in the programming of the tiles used to denote the shore of Cinnabar Island marks them as equivalent to grass. As all water routes have no real grass on them, likewise, the data is not overwritten, and so whatever data is in the slots for wild Pokémon found in the grass is used, be it the player's name or wild Pokémon found elsewhere, such as the Safari Zone.
The name of the player has six hexadecimal values in it. The game needs only three "slots" of wild Pokémon data to store this.
The species of wild Pokémon the player encounters along the coast are determined by the third, fifth, and seventh characters of the player's name, while their levels are determined by the second, fourth, and sixth characters, respectively. The game also reads the ninth and eleventh slots as wild Pokémon and the eighth and tenth slots as their respective levels; however, due to the seven character name limit, these slots are not used unless using a preset name, so are blank (00), causing 'M (00) to appear at level 0.
- See also: Fight Safari Zone Pokémon trick
Because Cinnabar Island has no wild Pokémon data but the potential for wild Pokémon to appear, and that wild Pokémon data is not formatted when entering a new area, any location that can be flown from can have its wild Pokémon available on the coast.
This includes the Safari Zone, so players can encounter Safari Pokémon under normal battling circumstances. Since the old man only writes to the first eleven wild Pokémon addresses, it means that extra Pokémon may be accessible even if the player's name is eleven characters long (which is possible with preset names). This grass Pokémon data is mapped to three 'uncommon encounters' and two 'rare encounters'.
Due to being able to find Pokémon over level 100, it is possible to trigger glitches relating to Pokémon with levels that are too high. If Pokémon over level 100 receives experience by battle, it will automatically go to level 100; Rare Candies will level up the Pokémon normally. If the Pokémon's remaining HP is already low, dropping to level 100 can cause the HP to drop to negative number, but it will be interpreted as a very high number, similarly to the Pomeg glitch. In Pokémon Stadium, HP is shown as the actual amount; in Pokémon Stadium 2, it will act as if its HP was full.
Reportedly, the first coast exploit discovered involved performing an in-game trade with an NPC and surfing on the coast.[1] This results in five level 80 hex:50 MissingNo. because the encounters are affected by the trade Pokémon's OT name. Specifically, grass data is overwritten with "5D 50 50 50 50 50 50 50 50 50 50". The 5D byte is a control character that prints "TRAINER" and the rest of the bytes are 'end name' characters.
Trading or fighting in the Cable Club overwrites the wild Pokémon data with the opponent's name, and by using the poison method of the Cable Club escape glitch one may escape from the Cable Club and keep the stored grass Pokémon data that normally disappears after resetting the game (even after trading). Note that battling heals the user's Pokémon, meaning that the player has to do this glitch by bringing up the trade screen.
This Cable Club coast exploit has an unexplained complication of affecting encounters further than uncommon Pokémon 1 (D891); for example, glitch Trainer FD can appear on the coast through this method.
Video of the trade NPC exploit:
| |
This video is not available on Bulbapedia; instead, you can watch the video on YouTube here. |
Video of the Cable Club trade exploit (which requires the Cable Club escape glitch)
| |
This video is not available on Bulbapedia; instead, you can watch the video on YouTube here. |
References
|
This article is part of Project GlitchDex, a Bulbapedia project that aims to write comprehensive articles on glitches in the Pokémon games. |