• Forum Moderator applications are now open! If you're interested in joining an active team of moderators for one of the biggest Pokémon forums on the internet, click here for info.

Pal Park...what clock does it run on?

Habunake

追放されたバカ
Joined
Jun 11, 2004
Messages
11,088
Reaction score
5
Does it log the 24 hours with the built in DS clock, or the internal clock of the GBA games?

Because I believe my friend's Japanese Ruby version never had the Berry Glitch fixed, so I can't use it for Pal Park anymore...and I don't know how to fix it....-_-
 
Hmm...would time-travelling with the DS throw it off?
 
I retimetravelled, and then went back to normal time, and now I get the standard "wait 24 hours" message again.
 
It did that to me the other day. I restarted the DS, went into Sapphire and saved in front of the computer instead of just in the Poke Center, then when I restarted it let me do it. Uncertain if the movement of my character actually changed anything, but I can guarantee that the berry glitch has not been fixed in my Sapphire. It's been 7:33 for a very long time.

- Trip
 
Ah!

I should of known that would most likely be the case!

Darn, now I have to wait 24 hours....0.0

EDIT: Now it goes back to the message I kept getting earlier...this sucks.

I'm gonna hope it works tommorow...

EDIT2: I found ou,t the Berry Glitch was indeed fixed. Now I'm REALLY worried.
 
Last edited:
I can't get my berry glitch fixed because I don't have a second GBA, and don't have an English FR/LG or Emerald to fix with.
 
What about the Gamecube games? I know downloading Jirachi from Channel fixes it...
 
There is every chance that putting the GBA cart in with D/P at the same time will patch the berry glitch. They certainly put the patching routine into every GBA or GCN release since Ruby & Sapphire.
 
Please note: The thread is from 20 years ago.
Please take the age of this thread into consideration in writing your reply. Depending on what exactly you wanted to say, you may want to consider if it would be better to post a new thread instead.
Back
Top Bottom