From Bulbapedia, the community-driven Pokémon encyclopedia.
|| This article contains old or outdated information, or has not been updated in a while. Please check the content of this article and update it as required.
|| The contents of this article have been suggested to be split into Dead battery quirks (Generation III).|
Please discuss it on the talk page for this article.
The Berry glitch is a glitch only found in Pokémon Ruby and Sapphire which stops the game's internal clock. The name of the glitch comes from the fact that the first thing a player will usually notice is that all Berries that have been planted but have not been harvested have ceased growing. The glitch typically occurs after about a year of owning the game, or to games that have been played for over 100 hours, but the exact mechanics of its cause are currently unknown.
Other affected areas
As the game's internal clock has been frozen, any time-based events in the game in addition to Berries are also affected by the glitch:
Similar effects with a dead or replaced battery
When the game cartridge's CR1616 internal battery runs dry, the in-game clock will also stop, resulting in very similar symptoms to the above. However, cartridges that have a dead battery will display a message after the title screen warning of the dry battery and the fact that clock-based events will no longer occur. In contrast, games being affected by the Berry glitch will not display this message.
The only way to fix this issue is to replace the battery. It is also possible for a game with a dead battery to be affected by the Berry glitch, however, meaning replacing the battery will not fix time-based events. To further complicate matters, replacing the battery may also cause issues of its own, as explained below.
Cartridges that have had their battery replaced may also experience similar problems. When the supply of power from the battery is interrupted, the cartridge's "real-time" timestamp (which is normally always updating, even when the game is not being played) reverts to zero. Many of the game's time-based events will only function properly if the cartridge's timestamp is greater than the timestamp that is recorded in the current save data. This means that, if a game was saved before the battery was replaced, loading that save file will load the old, high timestamp and prevent many time-based events from working. By contrast, when a new game is started, there is no such previous time stamp (until the game is first saved), so all time-based events will work as expected in new games.
The time-based effects that will reliably work after a battery is replaced include: the clock in the player's room, AM/PM recognition for time-based evolutions like Espeon and Umbreon, and the tide in Shoal Cave. The proper functioning of these events distinguishes this issue from the Berry glitch.
If the cartridge has a saved game from before the battery was replaced, short of starting a new game, there are a few possible solutions to restore time-based events.
- Wait for the cartridge's timestamp to catch up to the saved timestamp. This, of course, may take a very long time, depending on when in the previous battery's life the game was saved.
- Manually alter the timestamp in the save file (so it is less than the cartridge's timestamp).
- Manually alter the timestamp on the cartridge (so it is greater than the save file's timestamp).
Either of the last two options will require some sort of additional hardware.
Fixing the glitch
The glitch can be fixed with the Berry Program Update from Pokémon FireRed, LeafGreen, and Emerald, a patch from Pokémon Colosseum, Pokémon XD, Pokémon Channel, Pokémon Box Ruby & Sapphire, the e-Reader, or a specific interactive demo disc, as well as by sending the affected game to Nintendo.
Pokémon FireRed/LeafGreen/Emerald patch
- Main article: Berry Program Update
- Load FireRed, LeafGreen, or Emerald until the title screen is displayed.
- Press the Select and B buttons. After the new screen loads, press A.
- Insert the Link Cable so that the system that the FireRed, LeafGreen or Emerald game is connected to the Player 1 cable port and the Ruby or Sapphire game is connected to the Player 2 port. Once this is done, press A.
- Turn on the device with Ruby or Sapphire while holding the Start and Select buttons.
- Refer to the FireRed, LeafGreen or Emerald game display for further instructions. The patch should be transferred at this time.
Pokémon Colosseum and XD patch
Linking an affected game to Colosseum or Pokémon XD for trading or battling will automatically download the patch. In addition, the Bonus Disc that came with pre-orders of Colosseum can be used to download Jirachi into a game; when this happens, the patch is downloaded as well.
Pokémon Channel patch
Downloading Jirachi from a PAL version of Pokémon Channel will automatically download the patch.
Pokémon Box patch
Linking an affected game to Pokémon Box Ruby & Sapphire, accessing the Go To Adventure mode, and then saving the game whilst playing will also automatically fix this glitch, with the message "The Berry Program was updated" appearing with the save confirmation. (This option is not available for Japanese versions.)
For Japanese versions, a special set of e-Reader cards (ID# 16-A001 & 16-A002) were distributed with Pokémon Scoop's Winter 2004 issue to allow players to fix this glitch by using e-Readers.
Interactive demo patch
Specially-marked demo discs were released to select stores across U.S. and Japan, so players can visit these stores and download the patch from the disc. In addition, players will also receive a Shiny Zigzagoon holding a Liechi Berry as a bonus. However, since the demo disc program does not block fixed games, players can receive multiple Zigzagoon by downloading to the same cartridge again.
Sending cartridge to Nintendo
If the player had no opportunity to download the patch, the game could be sent to Nintendo to have it fixed. However, as of August 2012, Nintendo stopped offering to patch the Berry glitch.
- ↑ Pokemon Ruby/Sapphire New Battery Glitch at Furlock's Forest