Please remember to follow the manual of style and code of conduct at all times.
Check the Bulbagarden home page for up-to-date Pokémon news and discuss it on the forums or in the Bulbagarden Discord server.

Berry glitch: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
mNo edit summary
(31 intermediate revisions by 15 users not shown)
Line 1: Line 1:
{{GlitchResearch|Needs the exact cause of this glitch}}
The '''Berry glitch''' (Japanese: '''{{tt|きのみ問題|きのみもんだい}}''' ''Berry problem'') is a [[glitch]] only found in early versions of {{game|Ruby and Sapphire|s}} which affects the game's internal calendar. The name of the glitch comes from the fact that the first thing a player will usually notice is that all [[Berry|Berries]] that have been planted have ceased growing. The glitch occurs 366 days after the game is first started, or 366 days after the internal battery is replaced, and causes all calendar-based events to be delayed by 366 days. After the glitch was officially acknowledged by [[Nintendo]] and [[The Pokémon Company]], they provided several methods to mitigate the effects of the glitch, and incorporated a permanent fix into later production runs of the game.
The '''Berry glitch''' is a glitch only found in the coding of {{game|Ruby and Sapphire|s}} which seems to stop the game's day counter. The name of the glitch comes from the fact that the first thing the player will notice is usually that all [[Berry|Berries]] that have been planted but have not been harvested have ceased growing. The glitch typically occurs after about a year of owning either game, or to games that have been played over 100 hours.


==Other affected areas==
==Explanation==
As the Berry glitch affects the game's day counter and timer, other areas of the game are affected by the glitch.
The game cartridge contains a real-time clock (RTC) which keeps track of the year, month, day, hour, minute, second, and day of the week. When the RTC is first turned on, its date is set to January 1, 2000. Because the game has no need for an actual calendar system, it converts the RTC's year, month, and day data into a single "day number". The conversion function has a flaw, however: it will only count years (adding 365 or 366 days for each year or leap year) starting from 2001. So, while the RTC clock is reporting the year as 2000 or 2001, in both cases, the conversion equates this to "add 0 days to the day number". This means that, for the first 366 days the RTC runs (starting from January 1, 2000), the game's day number will count from 1 to 366 normally, but when the RTC clock reports January 1, 2001, the game's day number will start from 1 again.


* [[Lilycove Dept. Store]] never has any sales.
If, for example, a [[Sitrus Berry]] was planted on December 31, 2000 according to the RTC, which the game interprets as day 366, it will be scheduled to be fully grown on day 367. Due to the glitch, "day 367" will not happen until the RTC reaches January 2, 2002. The result is that the growth of the Berry appears to be frozen for 366 days. Other effects of this glitch include:
* Lilycove Dept. Store stops allowing the player to [[Pokémon Lottery Corner|draw a Lotto Ticket]].
* The [[Mauville Game Corner]] never has any service days.
* The [[Energy Guru]] never sells vitamins cheap.
* The tide in [[Shoal Cave]] never changes.
* The man who gives out {{TM|27|Return}} and {{TM|21|Frustration}} in [[Pacifidlog Town]] stops giving out [[TM]]s.
* Those that hand out free Berries don't hand them out anymore.
* [[Mirage Island]]'s random number will never change.
* {{p|Eevee}} will only be able to evolve into {{p|Espeon}} or {{p|Umbreon}}.
* {{rt|119|Hoenn}} and {{rt|123|Hoenn}} are stuck with the same weather condition.


==Similar effects with dead battery==
* Random events which are calculated once per day, including [[Energy Guru]] and [[Lilycove Dept. Store]] sales, service days at the [[Mauville Game Corner]], the random number for {{gdis|Mirage Island|III}}, and weather conditions on {{rt|119|Hoenn}} and {{rt|123|Hoenn}}, will be frozen until 366 days after the game was last played before the glitch took effect.
The glitch results in problems very similar to what happens when the game cartridge's {{wp|List_of_battery_sizes#Lithium_cells|CR1616 internal battery}} runs dry, which stops the game's clock. However, in cartridges that have a dead battery, there is a message after the title screen that warns of the dry battery and thus clock-based events will no longer occur. In contrast, games being affected by the glitch will not have that message.
* Drawings at the [[Pokémon Lottery Corner]], NPCs who offer free Berries daily, and the man in [[Pacifidlog Town]] who gives {{TM|27|Return}} or {{TM|21|Frustration}} weekly, will be frozen until 366 days after these events were last used.
Cartridges that report a dead battery may or may not be afflicted with the berry glitch but the methods mentioned later will not fix the affected areas. This may cause the illusion that an Emerald cartridge is affected by the glitch. In order to fix the issues, the battery has to be replaced.  
* The number of successful rocket launches at the [[Mossdeep Space Center]] will be reset to 1.


==Similar effects after replacing a dead battery==
The glitch does not affect the evolution of {{p|Eevee}} into {{p|Espeon}} or {{p|Umbreon}}, or the tides in [[Shoal Cave]], because these events are based only on the current time, not the day number.
Cartridges that had their battery replaced may experience similar affected areas. The RTC chip's value is reset to a value prior to the "last-saved-field" of the savegame thus causing the game to not register time as passed. Most of the effects mentioned rely on countdowns and will still be visible on cartridges after the battery has replaced. This may cause the illusion that a cartridge is affected by the glitch when it is not.


However, the clock in the player's room and the Eevee evolution are based on "real time" and therefore be correct. Thus, if a cartridge allows different Eevee evolutions and shows time passing on the clock in the player's room but the other effect are visible.
==Similar effects with a dead or replaced battery==
===Dead battery===
When the game cartridge's {{wp|List_of_battery_sizes#Lithium_cells|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.


These issues can be fixed by creating a new savegame (and therefore resetting the "last-saved"-field). Using additional hardware, it may be possible to set the RTC value or edit the "last-saved"-field in a savegame.
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.
 
===Replaced battery===
Cartridges that have had their battery replaced may also experience similar problems. When the supply of power from the battery is interrupted, the RTC is reset to January 1, 2000. As with the Berry glitch, this reset causes all scheduled calendar-based events to be frozen until the RTC reaches the expected value, which may take many years. This can be solved by starting a new game, or (with additional hardware) by altering the timestamp stored in the save file so it is lower than the RTC value, or by setting the RTC forward so it is greater than the save file timestamp.<ref>[http://furlocks-forest.net/wiki/?page=Pokemon_Ruby/Sapphire_New_Battery_Glitch Pokemon Ruby/Sapphire New Battery Glitch at Furlock's Forest]</ref>


==Fixing the glitch==
==Fixing the glitch==
The glitch can be fixed by downloading a patch from [[Pokémon FireRed and LeafGreen Versions|Pokémon FireRed, LeafGreen]], {{v2|Emerald}}, {{g|Colosseum}}, {{Pokémon XD}}, {{g|Channel}}, {{g|Box Ruby & Sapphire}}, the [[e-Reader]], a specific interactive demo disc, or by sending the affected game to Nintendo.
The glitch can be fixed with the Berry Program Update from {{game2|FireRed|LeafGreen|Emerald}}; a patch from {{g|Colosseum}}, {{Pokémon XD}}, {{g|Channel}}, {{g|Box Ruby & Sapphire}}, the [[e-Reader]], or a specific interactive demo disc; or by sending the affected game to [[Nintendo]].
 
If the Berry glitch has not yet begun, these programs will set the RTC forward by 366 days, which prevents the effects of the glitch. If the game is already affected by the Berry glitch, these programs will set the RTC forward to January 2, 2002, the date at which all effects of the glitch end. If the cartridge battery is replaced and a new game is started, the fix will need to be applied again.


===Pokémon FireRed, LeafGreen and Emerald patch===
===Pokémon FireRed/LeafGreen/Emerald patch===
[[File:Berry Program Update FRLG.png|thumb|right|The main screen in FireRed and LeafGreen]]
[[File:Berry Program Update E.png|thumb|right|The main screen in Emerald]]
# Load FireRed, LeafGreen, or Emerald until the title screen is displayed.
# Load FireRed, LeafGreen, or Emerald until the title screen is displayed.
# Press the Select and B buttons. After the new screen loads, press A.
# 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.
# Insert the Link Cable so that FireRed, LeafGreen, or Emerald is connected to the P1 cable port and Ruby or Sapphire is connected to the P2 port. Once this is done, press A.
# Turn on the device with Ruby or Sapphire while holding the Start and Select buttons.
# Turn on 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.
# Refer to the FireRed, LeafGreen or Emerald game display for further instructions. The patch should be transferred at this time.


Line 44: Line 42:


===Pokémon Box patch===
===Pokémon Box patch===
Linking an affected game to {{g|Box Ruby & Sapphire}}, accessing the Go To Adventure mode<!--Does this happen when using the storage part of box too?-->, 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. (Note that this option is not available for Japanese versions.)
Linking an affected game to {{g|Box Ruby & Sapphire}}, accessing the Go To Adventure mode<!--Does this happen when using the storage part of box too?-->, 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.)


===e-Reader patch===
===e-Reader patch===
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.
[[File:Berry Problem Repair Program.jpg|thumb|Japanese [[e-Reader]]+ cards containing the Berry Program Update, with explanation of the glitch from Nintendo and The Pokémon Company.]]
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 containing the Berry Program Update (Japanese: '''きのみ問題修理プログラム''' ''Berry Problem Repair Program'').
 
===GameCube Interactive Demo patch===
Specially-marked GameCube demo discs <!--Interactive Multi-Game Demo Disc version 14, 16 and Monthly Nintendo, Dec. 2003 - Mar. 2004-->were released to select stores across U.S. and Japan, so players could visit these stores and download the patch from the disc. In addition, players will also receive a {{shiny}} {{p|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.


===Interactive demo patch===
===GBA cartridge patch===
Specially-marked demo discs <!--Interactive Multi-Game Demo Disc version 14, 16 and Monthly Nintendo, Dec. 2003 - Mar. 2004-->were released to selected stores across U.S. and Japan, so players can visit these stores and download the patch from the disc. By downloading the patch from a demo disc, player will also receive a {{shiny}} {{p|Zigzagoon}} holding a [[Liechi Berry]] as a bonus. However, since the program does not block fixed games, players can receive multiple Zigzagoon by downloading to the same cartridge again.
Specially made GBA cartridges, with the same function as the GameCube demo discs, were released to select stores across the UK. Players could visit these stores and connect to a GBA system containing one of these cartridges via link cable to download the patch, as well as receiving a shiny Zigzagoon holding a Liechi Berry. As with the GameCube demo discs, the program does not block fixed games, so the Zigzagoon can be received by the same cartridge multiple times.


===Sending cartridge to Nintendo===
===Sending cartridge to Nintendo===
Line 58: Line 60:
* [http://www.nintendo.com/consumer/berryfaq.jsp Nintendo.com]
* [http://www.nintendo.com/consumer/berryfaq.jsp Nintendo.com]
* [http://www.nintendo.co.jp/n08/axvp/kinomi/index.html Nintendo.co.jp]
* [http://www.nintendo.co.jp/n08/axvp/kinomi/index.html Nintendo.co.jp]
==References==
<references />


{{Glitches}}<br>
{{Glitches}}<br>
Line 64: Line 69:
[[de:Beeren-Glitch]]
[[de:Beeren-Glitch]]
[[fr:Bug de l'horloge interne]]
[[fr:Bug de l'horloge interne]]
[[it:Glitch delle bacche]]
[[ja:きのみ問題]]
[[ja:きのみ問題]]

Revision as of 05:33, 4 June 2017

The Berry glitch (Japanese: きのみ問題 Berry problem) is a glitch only found in early versions of Pokémon Ruby and Sapphire which affects the game's internal calendar. 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 have ceased growing. The glitch occurs 366 days after the game is first started, or 366 days after the internal battery is replaced, and causes all calendar-based events to be delayed by 366 days. After the glitch was officially acknowledged by Nintendo and The Pokémon Company, they provided several methods to mitigate the effects of the glitch, and incorporated a permanent fix into later production runs of the game.

Explanation

The game cartridge contains a real-time clock (RTC) which keeps track of the year, month, day, hour, minute, second, and day of the week. When the RTC is first turned on, its date is set to January 1, 2000. Because the game has no need for an actual calendar system, it converts the RTC's year, month, and day data into a single "day number". The conversion function has a flaw, however: it will only count years (adding 365 or 366 days for each year or leap year) starting from 2001. So, while the RTC clock is reporting the year as 2000 or 2001, in both cases, the conversion equates this to "add 0 days to the day number". This means that, for the first 366 days the RTC runs (starting from January 1, 2000), the game's day number will count from 1 to 366 normally, but when the RTC clock reports January 1, 2001, the game's day number will start from 1 again.

If, for example, a Sitrus Berry was planted on December 31, 2000 according to the RTC, which the game interprets as day 366, it will be scheduled to be fully grown on day 367. Due to the glitch, "day 367" will not happen until the RTC reaches January 2, 2002. The result is that the growth of the Berry appears to be frozen for 366 days. Other effects of this glitch include:

The glitch does not affect the evolution of Eevee into Espeon or Umbreon, or the tides in Shoal Cave, because these events are based only on the current time, not the day number.

Similar effects with a dead or replaced battery

Dead 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.

Replaced battery

Cartridges that have had their battery replaced may also experience similar problems. When the supply of power from the battery is interrupted, the RTC is reset to January 1, 2000. As with the Berry glitch, this reset causes all scheduled calendar-based events to be frozen until the RTC reaches the expected value, which may take many years. This can be solved by starting a new game, or (with additional hardware) by altering the timestamp stored in the save file so it is lower than the RTC value, or by setting the RTC forward so it is greater than the save file timestamp.[1]

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; or by sending the affected game to Nintendo.

If the Berry glitch has not yet begun, these programs will set the RTC forward by 366 days, which prevents the effects of the glitch. If the game is already affected by the Berry glitch, these programs will set the RTC forward to January 2, 2002, the date at which all effects of the glitch end. If the cartridge battery is replaced and a new game is started, the fix will need to be applied again.

Pokémon FireRed/LeafGreen/Emerald patch

The main screen in FireRed and LeafGreen
The main screen in Emerald
  1. Load FireRed, LeafGreen, or Emerald until the title screen is displayed.
  2. Press the Select and B buttons. After the new screen loads, press A.
  3. Insert the Link Cable so that FireRed, LeafGreen, or Emerald is connected to the P1 cable port and Ruby or Sapphire is connected to the P2 port. Once this is done, press A.
  4. Turn on Ruby or Sapphire while holding the Start and Select buttons.
  5. 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.)

e-Reader patch

Japanese e-Reader+ cards containing the Berry Program Update, with explanation of the glitch from Nintendo and The Pokémon Company.

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 containing the Berry Program Update (Japanese: きのみ問題修理プログラム Berry Problem Repair Program).

GameCube Interactive Demo patch

Specially-marked GameCube demo discs were released to select stores across U.S. and Japan, so players could 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.

GBA cartridge patch

Specially made GBA cartridges, with the same function as the GameCube demo discs, were released to select stores across the UK. Players could visit these stores and connect to a GBA system containing one of these cartridges via link cable to download the patch, as well as receiving a shiny Zigzagoon holding a Liechi Berry. As with the GameCube demo discs, the program does not block fixed games, so the Zigzagoon can be received by the same cartridge multiple times.

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.

External links

References

  1. ↑ Pokemon Ruby/Sapphire New Battery Glitch at Furlock's Forest


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
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 sprites
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)


Project GlitchDex logo.png This article is part of Project GlitchDex, a Bulbapedia project that aims to write comprehensive articles on glitches in the Pokémon games.
Retrieved from "https://bulbapedia.bulbagarden.net/w/index.php?title=Berry_glitch&oldid=2649210"