69
edits
Talk:Berry glitch: Difference between revisions
→Similar glitch in a patched game with a newly-replaced battery
| Line 620: | Line 620: | ||
: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 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. | |||