Berry glitch: Difference between revisions

not the same as a dead battery
(+note on confusion between this glitch and the battery in the cartridge literally running dry)
(not the same as a dead battery)
Line 1: Line 1:
{{GlitchResearch|Needs exact cause, and symptoms need to be disentangled from effects of the cartridge battery literally running dry}}
{{GlitchResearch|Needs exact cause}}
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 reason for its name is because the first thing the player will notice is 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.
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 reason for its name is because the first thing the player will notice is 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.


Games afflicted by the glitch will display the following message upon start up:
The glitch results in problems similar to the game cartridge's CR1616 internal battery running down, which stops the game's clock.  However, in games afflicted by a dead battery, this message displays just after the start screen: "The internal battery has run dry. The game can be played. However, clock-based events will no longer occur." Games being affected by the glitch will ''not'' have that message.
"The internal battery has run dry. The game can be played. However, clock-based events will no longer occur."


==Other affected areas==
==Other affected areas==
152

edits