View source for Error message

{{redirect|Error|errors in the game's programming|glitch}}
In the Pokémon games, there are several '''error codes''' which can appear when the game is not functioning properly. These codes were probably intended to help developers by indicating the nature of the error and roughly where to look for it.

==In [[Generation I]]==
In {{game|Red and Blue|s}}, there are several error codes that appear when the game is not functioning correctly. The error message is mapped to internal character code 0. Only glitched messages contain this code, no actual messages do. These error codes are read from the memory location $FF8C. In the overworld, this value is used to store the current NPC or other object the game is trying to display text for, with the special value 0 assigned to the start menu. When displaying [[Game Corner]] prizes, it is used to store the current window. Heavy memory corruption can destroy this value, producing garbage error codes. These are some of the generally-accepted codes:

{| align="center" style="background: #{{kanto color dark}}; {{roundy|5px}}; border: 2px solid #{{kanto color}}"
|- align="center" style="background:#{{kanto color}}; color:#FFF"
! style="{{roundytl|5px}}" | Number
! Text that appears on screen
! style="{{roundytr|5px}}" | Possible reason for error
|- style="background: #fff"
| 0
| 0 error.
| A problem occured while trying to display the Start menu text.
|- style="background: #fff"
| 1
| 1 error.
| The game is unable to complete an event. For example, this error message can appear when the player is talking to someone and the game does not have anything valid to say. This can be seen in Pokémon Yellow when the player finishes the game with 152 entries in the Pokédex.<!-- look for "Pokémon Yellow completed in 1 minute" on YouTube for this.-->
|- style="background: #fff"
| 01
| I error.
| This error can occur when the game confuses battle events with regular events; sometimes when the player switches Pokémon beyond the sixth slot or incorrectly performs the [[Dokokashira door glitch]], this can lead the player into a fight with a [[glitch Pokémon]], or [[game freeze|freeze the game]].
|- style="background: #fff"
| 2
| 2 error.
| There is an error displaying in-game text when reading objects such as signs and TVs.
|- style="background: #fff"
| 02
| The file data is destroyed!
| This error can appear when the game data has been damaged to a point of no repair, sometimes through the use of glitches which can alter the game save, or when a cross-language trade is attempted. More commonly, this error appears when the internal battery inside the game cartridge inevitably stops working.
|- style="background: #fff"
| 4
| 4 error.
| Text error
|- style="background: #fff"
| 5
| 5 error.
| The current position of the [[player character]] is unrecognized. This can cause strange or glitchy characters to appear. [https://lh5.googleusercontent.com/-Wgm68w-5ey0/TmKmeRINuQI/AAAAAAAAAWQ/r9oKZBTAz_w/s912/89%252520Gp%2525208%2525208%2525204%2525208%2525205%252520ERROR.%252520PC%252520AAAAAAA.jpg]
|- style="background: #fff"
| 6
| 6 error.
| Text error
|- style="background: #fff"
| 7
| 7 error.
| The game is unable to display the correct/required text.
|- style="background: #fff"
| 9
| 9 error.
| This error message can appear when a game attempts to perform an event but the Pokémon in the player's party is unrecognized. For example, when the player attempts to trade a non-hybrid [[glitch Pokémon]] with a non-playable character.
|- style="background: #fff"
| 20
| 20 error.
| Text error
|- style="background: #fff"
| 40
| 40 error.
| The sound clip that is playing is unrecognized, this can sometimes play random Pokémon cries.
|- style="background: #fff"
| 48
| 48 error.
| When this error occurs, the screen will turn white and the words "48 ERROR" pop up before quickly reverting back to whatever the player was previously doing. This error can be caused by the glitch Pokémon [[a]] for unknown reasons.
|- style="background: #fff"
| 56
| 56 error.
| The game is unable to display the correct/required text. The [[glitch Pokémon]] [['Ng'Mp]]'s Pokédex entry triggers this error.
|- style="background: #fff"
| 59
| 59 error.
| This error is similar to a 5 Error, however it has also been seen after text such as "''This is my graThe trainer blocked the ball! I2''"
|- style="background: #fff"
| 98
| 98 error.
| This error can occur when data transferred between two cartridges via [[link cable]] is damaged, corrupted, or otherwise glitched.
|- style="background: #fff"
| 99
| 99 error.
| This error can occur when data transferred between the [[Game Boy Tower]] and the Game Boy game is damaged, corrupted, or otherwise glitched by the [[Transfer Pak]].
|}

===Mixed errors===
Sometimes the game will seem to mix error codes in between text; for example "9" with 2 Error. This would display "92 Error." but this is not an official error code.

===Gallery===
<gallery>
File:Glitchy 4.png|A 0 Error in Pokémon Red
File:4 Error.png|A 4 Error in Pokémon Red
File:5 Error.png|A 5 Error in Pokémon Red
File:6 Error.png|A 6 Error in Pokémon Red
File:48ERROR.png|A 48 Error in Pokemon Red
File:Ngmpdex.png| A 56 Error in Pokémon Blue
File:16 Error.png|A 16 Error in Pokémon Red
</gallery>

==In [[Generation II]]==
{{game2|Gold|Silver|Crystal}} feature a more detailed method of handling errors compared to Red, Blue and Yellow, although error messages are uncommon in-game without the use of a [[cheating]] device.

{| align="center" style="background: #{{johto color dark}}; {{roundy|5px}}; border: 2px solid #{{johto color}}"
|- align="center" style="background:#{{johto color}}; color:#FFF"
! Name
! Possible Cause/Description
|- style="background: #fff"
| 'Object Event'
| This text appears when the player attempts to talk to a character who normally cannot be talked to and thus has no talk event defined. [http://i4.photobucket.com/albums/y128/MithosYggdrasil/MissingNO/ObjectEvent.jpg]
|- style="background: #fff"
| 'No windows avail-able for popping.'
| This text appears when an event attempts to bring up a message window yet the specified text/function is undefined - notably appears when HM06 is used outside of the TM/HM pocket [http://forums.glitchcity.info/index.php/topic,1050.msg14487.html#msg14487]
|- style="background: #fff"
| 'The window save area was exceeded.'
| Theoretically would appear when too many overlapping popup windows are displayed. [http://iimarck.us/dumps/dcrystal.txt]
|- style="background: #fff"
| 'Corrupted Event!' 
| It is currently unknown when this may appear. A possible error regarding an event which has invalid data<!--This may appear in some of the more unstable glitches?-->. [http://iimarck.us/dumps/dcrystal.txt]
|- style="background: #fff"
| 'BG Event'
| Theoretically would appear when the player triggers a hidden event (such as leaving New Bark Town without a Pokémon) which has no script defined. [http://iimarck.us/dumps/dcrystal.txt]
|- style="background: #fff"
| 'The save file is corrupted!'
| This error message commonly appears when the player attempts to select Continue but the game has no valid data to load. For example, the game may give this message when data has been corrupted by a cross-region trade. This may also occur if the internal battery inside the game cartridge is dying or has died. [http://iimarck.us/dumps/dcrystal.txt]
|}

==Related articles==
* [[Glitch]]
* [[0 ERROR]]
{{-}}
{{Glitches}}
{{-}}
{{Project GlitchDex notice|no}}
[[Category:Glitches]]