Talk:Berry glitch: Difference between revisions

 
(29 intermediate revisions by 14 users not shown)
Line 524: Line 524:


:I don't know what exactly --[[User:D558|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.  [[User:Peterpansexuell|Peterpansexuell]] ([[User talk:Peterpansexuell|talk]]) 11:46, 14 September 2012 (UTC)
:I don't know what exactly --[[User:D558|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.  [[User:Peterpansexuell|Peterpansexuell]] ([[User talk: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?[[User:FireIceLucarioNinja|FireIceLucarioNinja]] ([[User talk:FireIceLucarioNinja|talk]]) 21:22, 5 June 2013 (UTC)
:Yes [http://www.overclock.net/t/465536/tutorial-replace-internal-battery-for-pokemon-ruby-sapphire-emerald you can replace the battery] and time-base events will occur again. --[[User:SnorlaxMonster|<span style="color:#A70000">'''Snorlax'''</span>]][[User talk:SnorlaxMonster|<span style="color:#0000A7">'''Monster'''</span>]] 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. '''[[User:Hfc2x|<span style="color:#008800">h</span><span style="color:#000000">fc</span>]][[User talk:Hfc2x|<span style="color:#000000">2</span><span style="color:#008800">X</span>]]''' 10:42, 19 August 2013 (UTC)
:::This is important. As I had confirmed, this happens on Emerald too, and the cause has been found [http://furlocks-forest.net/wiki/?page=Pokemon_Ruby/Sapphire_New_Battery_Glitch]. 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. '''[[User:Hfc2x|<span style="color:#008800">h</span><span style="color:#000000">fc</span>]][[User talk:Hfc2x|<span style="color:#000000">2</span><span style="color:#008800">X</span>]]''' 09:01, 26 November 2013 (UTC)


== Outdated? ==
== Outdated? ==
Line 543: Line 548:


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. [[User:HyperHacker|HyperHacker]] 18:06, 26 September 2011 (UTC)
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. [[User:HyperHacker|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 emulator[[User:kingsisle|kingsisle]]
:Emulators don't have any internal battery, so the game just assumes it is dry. It's not the Berry glitch. --[[User:SnorlaxMonster|<span style="color:#A70000">'''Snorlax'''</span>]][[User talk:SnorlaxMonster|<span style="color:#0000A7">'''Monster'''</span>]] 06:10, 8 March 2013 (UTC)
Thanks [user:kingsisle|kingsisle]


== Mirage Island Liechi Berry ==
== Mirage Island Liechi Berry ==
Line 606: Line 615:
: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. [[User:FallsDownStairs|FallsDownStairs]] ([[User talk:FallsDownStairs|talk]]) 08:10, 6 August 2012 (UTC)
: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. [[User:FallsDownStairs|FallsDownStairs]] ([[User talk: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. [[User:Aggron989|Aggron989]] ([[User talk:Aggron989|talk]]) 23:36, 12 December 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. [[User:Aggron989|Aggron989]] ([[User talk: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? [[User:Crater55|Crater55]] ([[User talk: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. [[User:Aggron989|Aggron989]] ([[User talk: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. [[User:Kendai|~Kendai]] ([[User talk: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 . [[User:Tiddlywinks|Tiddlywinks]] ([[User talk: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.[[User:TCCPhreak|TCCPhreak]] ([[User talk: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 [http://projectpokemon.org/forums/showthread.php?31254-A-Save-(3rd-Generation-Save-Editor)/|here, 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? [[User:Peterpansexuell|Peterpansexuell]] ([[User talk: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. [[User:TCCPhreak|TCCPhreak]] ([[User talk: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 [http://furlocks-forest.net/tools/pkmntimestamp.php | 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? [[User:Peterpansexuell|Peterpansexuell]] ([[User talk: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? [[User:Peterpansexuell|Peterpansexuell]] ([[User talk: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. [[User:TCCPhreak|TCCPhreak]] ([[User talk: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 … ^^ [[User:Peterpansexuell|Peterpansexuell]] ([[User talk: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. [https://gbatemp.net/threads/how-to-reset-the-rtc-in-gba-pokemon-games-after-replacing-the-battery.558620/| Here's a post explaining the process.] I'll also add this as a citation for that portion of the main page.
[[User:Feketelo|Feketelo]] ([[User talk: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 ([http://forums.glitchcity.info/index.php/topic,7192.0.html 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. [[User:SatoMew2|<b><span style="color:blue">Sato</span></b>]][[User talk:SatoMew2|<b><span style="color:pink">Mew</span></b>]] 17:40, 18 February 2015 (UTC)
 
: I noticed that there are two recent edits ([http://bulbapedia.bulbagarden.net/w/index.php?title=Berry_glitch&diff=2222984&oldid=2222285 1], [http://bulbapedia.bulbagarden.net/w/index.php?title=Berry_glitch&diff=2246003&oldid=2222984 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?  [[User:AySz88|AySz88]] ([[User talk:AySz88|talk]]) 08:29, 19 February 2015 (UTC)
::Yes, but I think we should hear [[User:Blueapple128|Blueapple128]] first. [[User:SatoMew2|<b><span style="color:blue">Sato</span></b>]][[User talk:SatoMew2|<b><span style="color:pink">Mew</span></b>]] 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? [[User:Ais5174|~ By Caroline under Bulbagarden ~]] ([[User talk:Ais5174|talk]]) 04:24, 6 April 2016 (UTC)
4

edits