Talk:Berry glitch

Whiat's the 'Celebi Glitch?'--[1]]Sonic Pikachu(No.1fan)[[2]] 16:18, 22 September 2007 (UTC)

It's a "glitch" that allows you to see Celebi in the wild in early English R/S carts, but they're so called "rarer than shinies". Pfff.. v__v; TinaTheKirlia 16:21, 22 September 2007 (UTC)

Please help! I get an error saying "Unable to update berry program" ~GT4GTR

And what's with the Pfff? The Celebi glitch is all too real, yet you seem to be insinuating the opposite. I'm Missingno. Master, and I approve this message. 13:42, 18 May 2008 (UTC)

Technical Information?

PuppyBoy: TALK - 11:01, 9 October 2008 (UTC) Does anyone have any technical information on this such as why it actually occurs and what the patch does?

It freezes time, liekly likely due to the internal battery running dry (This happened to me plenty of times).Θρtιmαtum♏_Talk|Links 11:10, 9 October 2008 (UTC)

PuppyBoy: TALK - 13:23, 9 October 2008 (UTC) No, I mean on an actual technical level - Does the clock have a limit to how high it can count? Does the patch reset the clock if it gets too high? How does the patch work exactly? Is it saved in the actual save file and will it carry over if the player's file is corrupt or they restart? Would it just be a few lines of ASM? It wouldn't be due to the battery running dry as this would undoubtedly prevent the clock from ever running again until the battery was replaced. They can't be recharged.

I believe it has something to do with reprogramming the ROM to use the time a different way, i could be wrong though... (GT4GTR 08:19, 22 December 2008 (UTC))

I'm also very interested in how this patch works. They can't "reprogram the ROM", it's Read-Only Memory. They have to be doing something in the save file. My theories are they suspected this would happen and added a flag in the save file to use alternate code, or they implemented some sort of patching system allowing them to insert code into the save file. I would guess they simply reset the day counter, but then wouldn't it happen again? HyperHacker 05:10, 11 April 2009 (UTC)

Still curious about this, also, saving code would be a bad idea, what with the hackers and space constraints. SavageWolf 20:11, 11 October 2009 (UTC)

I had a thought about the cause; it's said to happen after "about 100 hours" of play time? Perhaps 128? If the game were to mistakenly treat this as a signed number, up to 127 would work fine, but 128 would roll over to -128. That could cause some crazy calculation errors. HyperHacker 04:08, 16 December 2009 (UTC)

Some Questions

PuppyBoy: TALK - 10:27, 5 November 2008 (UTC) I have a few quick questions: In-Game Clock Does the berry glitch cause the clocks in yours and your rival's bedrooms to stop? Espeon/Umbreon Would a game effected only produce one or the other regardless of AM/PM? I suppose this would be answered by the first question... Patch from DP? Does DP patch RS when migrating pokémon?

In game clock - Yes, it does stop

Espeon/Umbreon - Yes, i believe only one can evolve depending on where the time stopped...

Patch from DP - No.

(GT4GTR 08:21, 22 December 2008 (UTC))

Some more questions

This showed up on my saphire game, about4 years ago...i havent really played it anymore since then, but i still wanna find out what has happened, so ive got some questions:

1. How do i find out if my game is berry-glitch'd or if the internal battery has actually run dry?

2. Do all of the listed effect happen? IIRC, i got the message, but still was able to plant and harvest berries...i havent tested all of the other effects, but i think i havent had any sale days on the roof of the supermarket (forgive my lack of proper names, havent played this in an eternity)

thanks in advance, Frznbxy 16:31, 24 July 2010 (UTC)

hello? anyone? D: Frznbxy 19:19, 27 July 2010 (UTC)

To check if its a berry glitch or you internal battery has actuallly run dry, try patching it. There's no harm in doing so if its fine. Anyway, It's highly unlikely your internal battery would have actually run dry in such a short space of time. Number 2, it should stop berries from growing, planting and harvesting should be unaffected. Sale days aren't overly likely, so you are probably just unlucky. There will be an ad on the in-game TV a few days in advance of the sale too. --SnorlaxMonster 08:23, 28 July 2010 (UTC)

okay, thank you. i dont have access to a patch this easily, but ill stay tuned on it. and a stupid question: i know berries still grow...even if the glitch occured, do berries still grow WHILE im playing the game? that could explain it...does the patch keep ALL berries from growing, or only while i am not playing the game? technically, the game gets powered by my gba anyways while i play it...am i missing something? thanks again Frznbxy 17:14, 29 July 2010 (UTC)

All you need is a Generation III Pokémon game (if its a handheld game, you'll need 2 GBAs, if its a console game, you'll need a GameCube), and a means of communication (link cable, wireless adapter, etc.). The only Generation III Pokémon game you won't be able to do it with is a non-PAL version of Pokémon Channel. It shouldn't hard at all to get the patch.

Also, time is recorded by an internal battery inside the game cartridge (like what the message says has run dry). This battery ensures that time always flows, even when no power is connected to the cartridge. While playing the game, it is possible that berries will still grow, I don't know enough about how it works to know this for certain. However, I would think that it relies solely on the internal battery to keep time, due to the error message saying that time-based events will not occur.

Also, the patch does not stop any berries from growing, it allows them to grow. This sort of question is better to ask on the forums, as it does not help the article. --SnorlaxMonster 03:10, 31 July 2010 (UTC)

Happens after a year???

This is inaccurate and misleading, it happened to my pokemon ruby after about 3 years and Sapphire's still working today after about 6 years and 300 hours... i think that should bhe changed... (GT4GTR 08:18, 22 December 2008 (UTC))

Anyone??? I'd change it but i don't know what to. (GT4GTR 12:13, 9 August 2009 (UTC))

It says typically. That doesn't mean that the glitch always shows up after a year. Maybe you got lucky. —darklordtrom 23:32, 9 August 2009 (UTC)

Fair enough. My sister's uby happened after about 4 or 5 years i think. (GT4GTR 12:14, 10 August 2009 (UTC))

Patching

When can you use the patch? Any time, or only if the glitch has happened? R.A. Hunter B. 04:39, 5 March 2009 (UTC)

The glitch has to occur...otherwise it doesn't work... ^ht14 04:39, 5 March 2009 (UTC)

Just making sure my game isn't already patched, as it didn't work. R.A. Hunter B. 04:45, 5 March 2009 (UTC)

Feebas

Someone removed the Feebas tidbit. Does it still change everyday? If so, how? ^ht14 02:07, 7 March 2009 (UTC)

Feebas changes every day in DP, not RS. In RS it changes with the trendy phrase in Dewford. — THE TROM — 03:39, 7 March 2009 (UTC)

Emerald

This glitch seems to have happened in my pokemon emerald game? Is that possible? or is it something else that may be fixed? -- D558 08:41, 8 August 2009 (UTC)

Helloooo? anyone? --D558 18:26, 13 August 2009 (UTC)

I'm not sure. When did you get it? - unsigned comment from Owlwinds (talk • contribs)

I don't think it's possible. It's Emerald itself that can fix this issue. Are you SURE it's the glitch? ^ht14 21:45, 4 October 2009 (UTC)

You may not have the berry glitch, it's possible that your internal clock battery has just run dry. ZestyCactus 20:13, 11 October 2009 (UTC)

It must be the battery or it's a small possibility that my game is some sort of great fake redesigned from a Ruby/Sapphire engine or something. I did get the game off eBay. I have linked it with my legit FireRed and LeafGreen, they have done nothing to fix this. Thanks for the responses. -- D558 09:49, 17 December 2009 (UTC)

I have had this same glitch in Pokemon Sapphire. I don't understand the things that don't happen, but I get the error message: The internal battery has run dry. The game can be played. However, clock based events will not occur. I do not know how long it's been owned, because my uncle got it from his friend, but my brother restarted the game immediately. I haven't played for 100 hours. I played more than 100 hours of Emerald, and nothing happened. August - unsigned comment from Augustjune380 (talk • contribs)

Please sign your posts with four tildes, like this: ~~~~. It's not a matter of how many hours you have played the game, but how many hours the game has been played overall--as in how long it's been since the game was first taken out of the box and played. If you have access to a copy of Pokémon Emerald, you can try to do the Berry Glitch fix that is included on that. If that doesn't help, then the battery really has run dry, and you'll likely have to get a new copy. --Phantom♫Junkie 20:32, 14 August 2010 (UTC)

Thanks, Phantomjunkie. I've been remembering to do that. And I have no idea how many hours it was before, and my file saved over the previous one was something like 72 hours. Augustjune380 20:42, 14 August 2010 (UTC)

I don't know what exactly --D558’s problem was/is, but I have a berry glitch on my Emerald game. I've planted a Cheri berry next to the Berry Master's house, on the left side of the middle bottom patch, and it just won't grow. I've planted it there years ago and it's still in stage one, it just never grows. Other berries grow fine, and all other time based events occur as well. I've done some googling and found one person with the same problem with the same berry in the exact same spot. I don't know if anything can be done about it, but I thought it should be at least mentioned somewhere here, as there is no article about such a thing in Emerald at all. Peterpansexuell (talk) 11:46, 14 September 2012 (UTC)

The internal battery on my Emerald game just ran dry. It displayed the message when I turned it on. What do I do? Can i restore time-based events by replacing the battery? Do I need to do something else, too? Or are the time-based events in my game gone forever?FireIceLucarioNinja (talk) 21:22, 5 June 2013 (UTC)

Yes you can replace the battery and time-base events will occur again. --SnorlaxMonster 03:48, 6 June 2013 (UTC)

I can confirm this glitch happens on Emerald too, albeit randomly. In my copy of Emerald, it triggered suddenly, and even though the battery wasn't dry, the time won't pass, berries won't grow, Shoal Cave's tide won't change and all that. It fixed itself when I started a new game. And for the record, changing the battery has no effect whatsoever. In my brother's copy, the battery had run dry a couple years now and naturally, the clock stopped working. The message that the battery was dead always appeared before continuing with the game. I replaced his game's battery the other day and the message disappeared, but the game is still stuck in time. You can google as much as you like, but nobody seems to acknowledge this problem. Everyone seems to think that the battery needs to be replaced, but that's not the problem. Emerald is INDEED prone to the Berry Glitch, and there seems to be no fix for it, other than starting a new game. I suggest we research this, because lots of people seem to be affected by it, and there's absolutely no info on the matter. hfc2X 10:42, 19 August 2013 (UTC)

This is important. As I had confirmed, this happens on Emerald too, and the cause has been found [3]. It seems to be related to the battery change once the old one dies. The linked website also lists a solution, but requires external devices to fix, and is not easy to "just patch it". I will try it later with my brother's copy of Emerald. hfc2X 09:01, 26 November 2013 (UTC)

Outdated?

This page affirms that Generation III games can still be sent to Nintendo to get the Berry Glitch fixed, eventhough, the company does not accept them anymore. :X SaitoFX 16:30, 4 October 2010 (UTC)

Is this from experience or something that you have read? If it's experience, change it. If it's on their website, we should link to them. --SnorlaxMonster 06:22, 5 October 2010 (UTC)

Sorry, I must have mistaken the information from the GameBoy games with the one of the GBA games. Just to correct myself: the game can still be sent to Nintendo's USA & Canada Factory Services to have the problem fixed for $10, which is usually the case since only new games with warranty can be replaced for free, after one calls (800) 255-3700. SaitoFX 02:31, 12 November 2010 (UTC)

This really is outdated now; I phoned Nintendo and asked them about repairing Ruby & Sapphire games today; they no longer do so as the possibility no longer exists of replacing the carts. FallsDownStairs (talk) 01:34, 7 August 2012 (UTC)

A variation of the Glitch?

Someone can help me?, in my game (Emerald Version), ocurred something similar to the berry glitch, the berries don't grow anymore, the events like energy guru selling cheaper stopped occuring, but i know the time is passing by, because when i talk with the Pokémon Fan Club Chairman's younger brother in Pacifidlog Town, the days for the TM are lowering, but instead of one weak, he is saying 500 days. I tried to fix the glitch with the patch but the game says something like "the berry program don't need to be transferred". If someone could help please... Pkmn Trainer Jinx 20:47, 7 February 2011 (UTC)

Perhaps your internal battery has actually run dry. --SnorlaxMonster 13:02, 24 February 2011 (UTC)

Temporary fixes

It started with my Ruby game lately, but I've noticed that after a few saves and soft resets I am able to get past the glitch and getting it to work again, though I've had to do it once every few days. I don't have all the details, but this seems to be working for now. -Tyler53841 21:27, 26 March 2011 (UTC)

Battery run dry

I had this happen to me, and I didn't get any "battery has run dry" message, or anything else unusual other than the berries not growing. HyperHacker 18:06, 26 September 2011 (UTC)

Mine is a emulator and the message for the battery has run dry is always there so can this glitch stil happen in an emulatorkingsisle

Emulators don't have any internal battery, so the game just assumes it is dry. It's not the Berry glitch. --SnorlaxMonster 06:10, 8 March 2013 (UTC)

Thanks [user:kingsisle|kingsisle]

Mirage Island Liechi Berry

Can the Liechi Berry on Mirage Island also trigger this glitch? To this day (before I started getting the "The internal battery has run dry. The game can be played. However, clock-based events will no longer occur." message) I have not been able to access Mirage Island. --Wildgoosespeeder 07:44, 28 October 2011 (UTC)

I don't see how it could trigger it, but you will have difficulty accessing Mirage Island as the random number won't change. --SnorlaxMonster 06:33, 28 October 2011 (UTC)

The keyword is before. ;) --Wildgoosespeeder 07:44, 28 October 2011 (UTC)

I've never been able to access it either. It isn't a very likely event. About the same chance as encountering a Shiny wild Pokémon. It shouldn't be related. --SnorlaxMonster 07:55, 28 October 2011 (UTC)

I don't think you get what I am saying. I was unable to get to the island because I was never lucky enough to get the randomly generated number that would grant me access. With that being said, I was never able to get the Liechi Berry that was on the island. Since this glitch involves berries in Loamy soil and being forgotten triggering the false dead battery message, could this contribute to the glitch? --Wildgoosespeeder 08:21, 28 October 2011 (UTC)

Berries being forgotten does not cause this glitch. It is caused because the internal batteries in old Ruby and Sapphire games were not made correctly. If you have a game with a dodgy battery, you could never touch a Berry or collect all of them in the first 24 hours, and neither would prevent the glitch. Berries stop growing because of the glitch, not the other way around. --SnorlaxMonster 00:28, 29 October 2011 (UTC)

According to your explanation, that's no glitch at all but rather just something to expect with batteries. They will die eventually even when not in use. No Berry Program Update can fix a dead battery.

The Berry glitch is the nickname for a glitch in the coding of Pokémon Ruby and Sapphire which seems to stop the game's day counter and freezes the growth of any berries which have been planted but not harvested. That current description tells me that the code that deals with various berry functions somehow affects the in-game clock over time but it shouldn't (fixed in Pokémon Emerald Version). --Wildgoosespeeder 01:30, 29 October 2011 (UTC)

The issue is that it thinks that the batteries are dead when they aren't. All time-based events stop, not just Berry growth. --SnorlaxMonster 01:56, 29 October 2011 (UTC)

I know that. Berry growth is normally dependent on the in-game clock. The description, however, says the unpicked berries affected the in-game clock over time, which it shouldn't, thus falsely giving the error message. I remember picking every berry in the game except the ones found on Mirage Island due to being unlucky to go to that place before I started getting the error message. Since they have remained unpicked to this day, I think those berries may have caused the glitch to occur in my two games. Is that possible?

As a side note, I tried to use the Berry Program Update found in Emerald. It didn't work. I did open my games up with a triwing screwdriver and tested the battery with a meter. The Ruby cartridge had no reading while the Sapphire cartridge had a pretty strong reading. If that one battery has a good reading, I get the error message anyway, and the Berry Program Update fails, what in the world is going on here? More importantly, what does the Berry Program Update fix exactly? --Wildgoosespeeder 02:20, 29 October 2011 (UTC)

The description, however, says the unpicked berries affected the in-game clock over time, which it shouldn't, thus falsely giving the error message. Where does it say that? Because they don't, so it shouldn't say that. No idea what the patch fixes, but I guess you could try the other methods. Otherwise you could always try "Sending cartridge to Nintendo". --SnorlaxMonster 02:29, 29 October 2011 (UTC)

I just summarized that section to what I thought it meant. Do I have it wrong? If so, that section needs to be reworded because I'm thinking that unharvested berries affect the in-game clock! I'm all confused. I read the rest of the talk page and everyone seems to be confused too. --Wildgoosespeeder 02:43, 29 October 2011 (UTC)

What it means is that Berries that you haven't harvested won't grow anymore. It is not caused by that fact. You can have no unharvested Berries and still get the glitch. --SnorlaxMonster 02:49, 29 October 2011 (UTC)

Alright then. So the reason it is called the "Berry glitch" is because the first thing that people noticed was berries stopped growing? If that is true, all that remains is what causes the in-game clock to stop and give the false error message even though the battery is not dead. --Wildgoosespeeder 02:59, 29 October 2011 (UTC)

That, and probably in part due to the message "The Berry Program was updated" given when patched from Pokémon Box. --SnorlaxMonster 03:05, 29 October 2011 (UTC)

Wow, and all this time I thought the term "Berry glitch" meant that berries were to blame for the in-game clock messing up. Thanks for clarifying. Should I flag this article for the reasons noted below? The introduction could be reworded to avoid confusion like I just had and I don't see a section for what causes this glitch, just things affected by it. --Wildgoosespeeder 03:47, 29 October 2011 (UTC)

{{Rewording|introduction}} {{GlitchResearch|Causes through analyzing game code.}}

I don't really see how it is misleading, but if you can rewrite it so that it is not, please do so. I don't really like Template:Rewording—if something needs rewording, you should just do so, not tag it as needing it. I don't think GlitchResearch is really necessary either, but you could still add it. --SnorlaxMonster 03:54, 29 October 2011 (UTC)

I figure since other glitches in this wiki I have read have explanations to what causes them, I figure that this article can use it too. --Wildgoosespeeder 04:02, 29 October 2011 (UTC)

Research Needed Re: Cause

Does anyone have a confirmed unpatched save file and a confirmed patched saved save file for comparison? I'm pretty interested to know what the patch does.

I've read that people managed to load various bits of code via the patch system. Anyone know anything about this? PuppyBoy 22:58, 3 November 2011 (UTC)

Patch not Permanent?

I've had my game patched through the Bonus Disk method. However, I recently got the message that my battery has run dry. Does this mean that the patches to fix the game only work for a limited amount of time? If so, I think it's something we should note in the article. Crystal Talian 08:51, 23 December 2011 (UTC)

It means your battery actually has run dry. --SnorlaxMonster 09:14, 23 December 2011 (UTC)

But I thought the patch was meant to prevent that? Or does the glitch cause time-based events to stop before the battery runs dry? Crystal Talian 09:24, 23 December 2011 (UTC)

The GB, GBC and GBA games have an inner battery. Once this runs dry, you can not play the game any more I'm afraid. It's nothing to do with the patch or the glitch. ☆The Solar Dragon☆ 09:38, 23 December 2011 (UTC)

The game plays just fine, actually. It just doesn't run any time based events (berries, dailies, et cetera). That's why I was asking, it's exactly like the Berry Glitch, which I'm sure I have the patch for. I checked and everything. Crystal Talian 09:45, 23 December 2011 (UTC)

What Solar Dragon is half-correct. GB, GBC, GBA, and even DS games have internal batteries. However, only GB and GBC games will be rendered unplayable by this battery running dry. GBA and DS games (with DS games having such a good quality battery that they won't be running dry in the forseeable future) will only stop time-based events from occurring. GB and GBC games will just be unable to be saved. The glitch means that the GBA game thinks the battery thinks the battery is dead when it isn't. However, due to the age of the games, batteries are actually dying now. --SnorlaxMonster 11:37, 23 December 2011 (UTC)

To clarify, most GB/C cartridges which can save use internal batteries to power up both the internal clock and the save data, but many GBA cartridges (including Ruby and Sapphire) use a separate flash memory chip to store the internal clock battery instead, meaning if the battery runs out in the GBA games it will only affect the clock data. --Chickasaurus 13:57, 23 December 2011 (UTC)

Not the same as battery run dry message?

This edit seems dubious to me - it seems like the berry glitch and the internal battery literally running out are two different problems. Does the glitch actually make the message appear, or not? AySz88 05:53, 3 February 2012 (UTC)

Okay, took the liberty of fixing this, on the presumption that there is just some confusion because these have similar symptoms. AySz88 23:02, 5 February 2012 (UTC)

After replacing my battery, I definitely have the glitch and a live battery, and I can confirm that the message does not appear if there's just the berry glitch. AySz88 03:00, 2 March 2012 (UTC)

Regarding Trainers not wanting to rebattle

This glitch causing the game to think its battery is dead, correct? My battery actually is dead (I have the patch for the glitch), but I still get rebattle requests through my PokéNav. Basically, I'm wondering if Trainers not wanting to rematch is part of the glitch, and only the glitch. Because the internal clock doesn't seem to affect them. I hope I'm making sense, I'm having a little trouble wording this. Crystal Talian 05:55, 7 February 2012 (UTC)

Maybe these Trainers already wanted to battle you before? I think it might not matter, since the battery-related effects will only affect events that need to keep being counted while the game is off, whereas Trainer rematches are based on playing the game, not a general time-based thing, I think. --SnorlaxMonster 07:02, 7 February 2012 (UTC)

I'm fairly certain that the Trainers have nothing to do with the internal clock. I've fought the same Trainers five times since my battery has been dead. The little Poké Ball symbol disappears and comes back later and everything. So, I think you're right about it being based on gameplay time, not real time. But in that case, doesn't that mean it should also be unaffected by the glitch? Crystal Talian 07:08, 7 February 2012 (UTC)

If so, then yes. --SnorlaxMonster 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. 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. - unsigned comment from FallsDownStairs (talk • contribs)

I have observed that furthermore the tides in Shoal Cave still work, but the Berry Master and the Lotto Centre don't seem to reset after midnight. I'd honestly think it's just a straightforward Berry Glitch if I hadn't already patched it, and if the battery hadn't previously run out. FallsDownStairs (talk) 08:10, 6 August 2012 (UTC)

The same thing happened to me... The internal battery ran down in Sapphire and it was replaced (admittedly with a different size battery but that shouldn't make any difference, I'm told), but the time still wasn't running. I patched the berry glitch and now Shoal Cave is changing tides and the clock is moving but nothing else is happening. There are several berries stubbornly refusing to grow. Aggron989 (talk) 23:36, 12 December 2012 (UTC)

I had a dead internal battery, so I replaced it with the proper "CR1616" battery. The clock in the game moves, but clock-based stuff doesn't happen. I have tried to get the berry patch using the Leafgreen method, but Ruby said it was "unable" to get the patch (I left a party space open on Ruby like you're supposed to). I tried connecting to Colosseum by trading and by battling, but neither of those installed the patch. Maybe nothing is working because I already have the patch? If so, then why is it acting like I don't? Crater55 (talk) 22:54, 30 December 2012 (UTC)

I didn't know you were supposed to leave a party space open. The Sapphire version I was trying to fix received the patch from a Leafgreen version just fine, and it had a full party. It was after I patched it when the clock started moving but nothing else happened except that the tides in Shoal Cave began changing again. It could be that your game has already been patched, because I don't think it will patch a second time. Aggron989 (talk) 21:06, 28 January 2013 (UTC)

I think it has to do with the way time is counted and the fact games weren't programmed with battery replacement in mind. There may be a very high counter intended to count upward for as long as the battery lasts. When the battery runs out it goes back to zero if this counter is the basis of the clock, it may stop time based events from working correctly based on how it works with the counter.

For berries, it may compare the current counter value with the previous counter value and add the amount of time that passed. If the battery is replaced, it's comparing a high previous value to a much lower value after battery replacement, and assuming no time has passed. ~Kendai (talk) 19:21, 31 March 2014 (UTC)

This is probably all the detail anyone could want, including potential solutions: http://furlocks-forest.net/wiki/?page=Pokemon_Ruby/Sapphire_New_Battery_Glitch . Tiddlywinks (talk) 21:45, 31 March 2014 (UTC)

As many people confuse the "dead battery"-effects and "after replacing battery"-effects with the berry glitch, I decided to add two sections for "when it looks like the glitch but is not". However, this is starting to get very technical and I wonder whether a page with more information about the RTC and battery (and "timeouts" vs "real time") may be useful. This also seems to be slightly out of scope for the "time"-page.TCCPhreak (talk) 14:47, 5 August 2014 (UTC)

If you have the information, please share it. I am one of the people trying to find out just what exactly needs to be done to make real time events work again after the battery has been replaced. Simply resetting the RTC does not work, unfortunately. There is also a discussion about this going on in a thread about KazoWAR’s A-Save save file editor (spread among other posts referring to the editor). So, if you have any information, especially on the distinction between 'timeouts' and 'real time', please let people know. Personally, I'm curious about the 'last saved' value somebody else mentioned here. Maybe that is the key to everything? Peterpansexuell (talk) 11:13, 11 September 2014 (UTC)

I think, I added most (all?) of this info already on the page. I was merely thinking that moving it out of this page may be sensible. To be honest, I do not know really much about the RTC-stuff. I read furlocks-forest and the A-Save-thread and experimented a bit from there. After some failures, I was pretty happy when berries grew again and I could farm shell bells from shoal cave. It seems like talking to the old man can re-start timeouts; maybe there are other restart-events as well. I've tried to understand the 'last save'-value and the relation to the 'game started'-info with several starts of the game but failed to do so (exact values are documented on furlocks forest) so I cannot really add much to the discussion. I could try whether the other time-based-events work on my cartridge (on which I changed the battery without starting a new game). If they do, the old man could be the key. TCCPhreak (talk) 12:33, 11 September 2014 (UTC)

Thanks for replying! I see. The 'last save' value seems to be 'time started' + 'time passed'. I am currently trying a few things based on new info I found on the furlock's forest site in the comments. (I restarted my game and uploaded it to | their timestamp check to find out what the 'cart's time' that some talk about is. Will now manipulate my game with the cart's time in mind. Maybe I can simply take the values from a newly started game and copy them into an old save file …?) Will report back in case I am successful. Thanks a lot for mentioning the old man, will check that, too. In case we ever get it to work, maybe we could write a tutorial or something like that together? Peterpansexuell (talk) 12:45, 11 September 2014 (UTC)

Update: I got it to work with the RTC editor from furlock's forest. Turns out that if you have ever saved on your game with VBA’s RTC enabled, the game is messed up. I couldn't get such games to run again, but it works fine on all other games (untouched by VBA). As I was doing most of my testing etc. with a cartridge that had been messed up by VBA, most of my test results were simply off and made no sense. It seems like at the moment, the RTC edit tool is the only thing that can really help you as simply changing the 'last save' date etc. with save file editors doesn't work. At the moment there is only the GBA flash cart version around, maybe one day someone will make a version that runs on DS flash carts, too. Anyways. If you think it's a good idea, maybe update that last sentence about the 'last save' date and/or add a note that save files that have been saved on with VBA's real-time clock enabled won't work in any case? Peterpansexuell (talk) 11:26, 14 September 2014 (UTC)

I think I commented on the "Emulator that supplies PC Clock as RTC value"-problem on furlock's forest. As this strongly refers to using emulators for playing the games, I'm not sure whether it should be included on the glitch page (there are other pages containing the word "emulator" or "VBA"). I don't think that VBA manipulates the savegame in other ways than an original GBA (as in "should not alter the game-started-flags") but simply causes high numbers to be written to the "last time saved". So I would expect that changing the "last time saved"-field in the savegame should fix this - but I have not looked into this. To be honest: I agree with furlock that writing to the RTC seems cleaner than patching the savegame. TCCPhreak (talk) 15:23, 15 September 2014 (UTC)

I have not managed to make *any* game work again with just editing the 'last save' value (and other time values) in the save file, not even the untouched ones, sadly. My game with a VBA-influenced save file, however, does not work even when I change the actual RTC of the cartridge, it’s just messed up. Also, when I edit time values in the save file of that game, e.g. the in-game time (that you set on your clock in your room), what I enter and what is actually displayed by the game are two completely different times. So while I am not willing yet to rule out the possibility that doing things with the save file alone (without touching the RTC) might make a game work again (although I haven't been able to do so so far; and I've tried quite a lot), I can say that a VBA-saved game doesn't even work again after an RTC-fix. I just thought mentioning that might be useful for people in similar situations, lest they try everything and get disappointed because they at one point saved via VBA with its RTC on. But I'm also just glad that it got mentioned at least here now, that's sometimes enough already for people who look for every bit of info in these situations … ^^ Peterpansexuell (talk) 17:14, 15 September 2014 (UTC)

Stumbled across this talk page while trying to fix this very issue. There's now a new tool that can fix this issue. Here's a post explaining the process. I'll also add this as a citation for that portion of the main page. Feketelo (talk) 05:19, 30 December 2020 (UTC)

New info

GCLF member Háčky researched the cause of the glitch and explained how Game Freak fixed it (link). The Berry Program Update does not fix the glitch in all circumstances and it definitely does not affect games with dead batteries. Speaking of which, I think the information about the quirks caused by dead batteries should be placed in a different article since the two issues are not related. SatoMew 17:40, 18 February 2015 (UTC)

I noticed that there are two recent edits (1, 2) that changed the text from "seems to stop the game's day counter" to "stopping the internal clock", which would actually be less accurate given the information in that new thread. Those two edits also change a bunch of other things in the article, along the same lines. Should those changes be undone wholesale? AySz88 (talk) 08:29, 19 February 2015 (UTC)

Yes, but I think we should hear Blueapple128 first. SatoMew 19:59, 19 February 2015 (UTC)

Starting a New Game?

Does the patch need to be reapplied if you clear saved data and start a new game? ~ By Caroline under Bulbagarden ~ (talk) 04:24, 6 April 2016 (UTC)