Talk:Berry glitch: Difference between revisions

(Undo revision 1721597 by Pkmnerd (talk)vandal)
Line 598: Line 598:
:::If so, then yes. --[[User:SnorlaxMonster|<span style="color:#A70000">'''Snorlax'''</span>]][[User talk:SnorlaxMonster|<span style="color:#0000A7">'''Monster'''</span>]] 07:39, 7 February 2012 (UTC)
:::If so, then yes. --[[User:SnorlaxMonster|<span style="color:#A70000">'''Snorlax'''</span>]][[User talk:SnorlaxMonster|<span style="color:#0000A7">'''Monster'''</span>]] 07:39, 7 February 2012 (UTC)
:::I have a game that has the glitch but a live battery (though it was replaced manually) - trainers do rebattle there.  I'll update the article. [[User:AySz88|AySz88]] 07:46, 29 February 2012 (UTC)
:::I have a game that has the glitch but a live battery (though it was replaced manually) - trainers do rebattle there.  I'll update the article. [[User:AySz88|AySz88]] 07:46, 29 February 2012 (UTC)
== Similar glitch in a patched game with a newly-replaced battery ==
I have symptoms very very similar to the Berry Glitch in a Ruby Version that has been patched, had the internal battery run dry, but has had the internal battery replaced. I have confirmed the clock to be running in-game; berries still will not grow, however. Does running out of battery break time-based events in the current save regardless of whether the battery is currently good? The precise effects of the internal battery running dry aren't particularly well documented.