Error message

Error redirects here. For errors in the game's programming, see 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 Red, Blue, and Yellow, there are several unused error codes (Japanese: エラー) that are only available through glitching or hacking. Error codes normally appear when the game prints an internal '00' character code in the middle of a text string. In Pokémon Red and Blue they appear in the form of '(x) ERROR.', while in Pokémon Yellow they appear in the form of '(x) error.' The error code is normally the index number of the text box that contains the '00' character. When an error code is printed on the screen, the game ignores all text that follows it.

The memory address $FF8C usually stores the identifier of the text box after the message is closed. When displaying Game Corner prizes, it is used to store the current window. Error codes can appear during Trainer escape glitches. For example, in Pokémon Red and Blue, fleeing from the long-range Trainer on Route 6, re-enabling the ability to use the start menu with a Trainer in a location other than Route 6 and returning to Route 6 after reading the PokéMart sign in Vermilion City will bring up a '9 ERROR.' This is because the PokéMart sign in Vermilion City has a text identifier of 09h, stored in the memory address $CF13. Upon returning to Route 6, the game attempts to print text box 09h but the corresponding text for Route 6 doesn't exist and is presumably just a single 00 character, so the game prints a '9 ERROR.'

'Mixed errors'

Mixed error codes is a misnomer for false error codes that can appear to have large numbers. In glitch dialog, numbers can precede the 00 character that prints an error code, giving the impression that the error code number is larger than it actually is.

Gallery

• 

  A 0 Error in Pokémon Red

• 

  A 4 Error in Pokémon Red

• 

  A 5 Error in Pokémon Red

• 

  A 6 Error in Pokémon Red

• 

  A 48 Error in Pokemon Red

• Ngmpdex.png

  A 56 Error in Pokémon Blue

• 

  A 16 Error in Pokémon Red

• 

  A 2 Error in Pokémon Red

• 

  A 30 Error in Pokémon Yellow

In Generation II

Pokémon Gold, Silver, and Crystal feature a more detailed method of handling errors compared to Red, Blue and Yellow, although error messages are uncommon in-game without using cheating devices.

Name	Possible Cause/Description
'Object Event'	This text will appear when trying to talk to an object which has no event set for it. [1]
'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 [2]
'The window save area was exceeded.'	Theoretically would appear when too many overlapping popup windows are displayed. [3]
'Corrupted Event!'	Causes of this message are unknown, probably displays if the object the player is talking at has an invalid event set for it . [4]
'BG Event'	Would appear when the player triggers a hidden event (such as leaving New Bark Town without a Pokémon) which has no script defined. [5]
'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 unstable or is completely depleted. [6]

Related articles

• Glitch
• 0 ERROR

Glitches in the Pokémon games Multiple generations Transform glitches • Glitch Trainers • Cloning glitches • Error messages • Arbitrary code execution Generation I Glitches • Battle glitches • Overworld glitches -- • 0 ERROR • Broken hidden items • Cable Club escape glitch • Dual-type damage misinformation Experience underflow glitch • Fight Safari Zone Pokémon trick • Glitch City • Item duplication glitch • Item underflow Mew glitch • Old man glitch • Pewter Gym skip glitch • Pokémon merge glitch • Rhydon glitch • Rival twins glitch Select glitches (dokokashira door glitch, second type glitch) • Super Glitch Time Capsule exploit • Walking through walls • ZZAZZ glitch Generation II Glitches • Battle glitches Bug-Catching Contest glitch • Celebi Egg glitch • Coin Case glitches • Experience underflow glitch Glitch dimension • Glitch Egg • Teru-sama • Time Capsule exploit • Trainer House glitches • GS Ball mail glitch Generation III Glitches • Battle glitches • Overworld glitches Berry glitch • Dive glitch • Pomeg glitch • Glitzer Popping Generation IV Glitches • Battle glitches • Overworld glitches Acid rain • GTS glitches • Pomeg glitch • Rage glitch Surf glitch • Tweaking • Pal Park Retire glitch Generation V Glitches • Battle glitches • Overworld glitches Charge Beam additional effect chance glitch • Charge move replacement glitch • Choice item lock glitch Frozen Zoroark glitch • Sky Drop glitch Generation VI Glitches • Battle glitches • Overworld glitches Charge Beam additional effect chance glitch • Charge move replacement glitch • Choice item lock glitch Lumiose City save glitch • Symbiosis Eject Button glitch • Toxic sure-hit glitch Generation VII Glitches • Battle glitches Charge Beam additional effect chance glitch • Charge move replacement glitch • Choice item lock glitch Toxic sure-hit glitch • Rollout storage glitch Generation VIII Glitches Charge Beam additional effect chance glitch • Charge move replacement glitch • Choice item lock glitch Toxic sure-hit glitch • Rollout storage glitch • Party item offset glitch Generation IX Glitches Glitch effects Game freeze • Glitch battle • Glitch song Gen I only: Glitch screen • TMTRAINER effect • Inverted sprite Gen II only: Glitch dimension Lists Glitches (GO • Mystery Dungeon • TCG GB • Spin-off) Glitch Pokémon (Gen I • Gen II • Gen III • Gen IV • Gen V • Gen VI • Gen VII • Gen VIII) Glitch moves (Gen I) • Glitch types (Gen I • Gen II)

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