-
Check out the relaunch of our general collection, with classic designs and new ones by our very own Pissog!
-
Welcome to Smogon! Take a moment to read the Introduction to Smogon for a run-down on everything Smogon, and make sure you take some time to read the global rules.
Most Generation PRNG Help / Information
- Thread starter mingot
- Start date
Yes, I'm using PikaTimer.
And no, I haven't been adjusting the seconds. Bearsfan092's videos had these set to 0 so I just mimicked that.
However, I just set that and the call came up as...
16:56:48 with the delay 2341.
So do I update PikaTimer with the delay 2341, or is there something different that I need to edit? How will PikaTimer I know I meant the 16:56:48 delay and not the the 16:56:49 delay?
And no, I haven't been adjusting the seconds. Bearsfan092's videos had these set to 0 so I just mimicked that.
However, I just set that and the call came up as...
16:56:48 with the delay 2341.
So do I update PikaTimer with the delay 2341, or is there something different that I need to edit? How will PikaTimer I know I meant the 16:56:48 delay and not the the 16:56:49 delay?
Well, now try to see if you can hit anything near your right delay, if you search for +/- 9 seconds as well.
My problem was back then, when I didn't update my timer, I got a delay of +14. So I thought, I'll just update my timer. When doing that, I got the right delay, but 1 second too early. Then someone told me, I had to add 0,5 second to the first timer to make it work. And here I am, did over 80 abuses already on 4th with PikaTimer xD So you might want to try that. :)
Alright, I started over the search from the default timer. My first call hit 16:56:50 at 2429.
Which is pretty close so now I'm like, where was this last time? xD
Anyways, so I enter 2429 into the "Other Delay" section on PikaTimer and just click Update, reset the time and start again. My question was if the delay I hit is a different second, is there anything I need to change? Or do I just enter that into "Other Delay" as usual?
To me, there's a difference between a 16:56:50 2429 delay and a 16:56:49 2429 delay. Does this 1 second difference matter to PikaTimer at all?
Thanks for your help btw. (:
I would've just kept increasing the spread to like, +/- 1000. xD
edit; The next call is a perfect example. I got 16:56:49 at 2377.
Do I just input 2377 into the "Other Delay" spot on PikaTimer and update, or is there something additional I have to do because the second changed?
Which is pretty close so now I'm like, where was this last time? xD
Anyways, so I enter 2429 into the "Other Delay" section on PikaTimer and just click Update, reset the time and start again. My question was if the delay I hit is a different second, is there anything I need to change? Or do I just enter that into "Other Delay" as usual?
To me, there's a difference between a 16:56:50 2429 delay and a 16:56:49 2429 delay. Does this 1 second difference matter to PikaTimer at all?
Thanks for your help btw. (:
I would've just kept increasing the spread to like, +/- 1000. xD
edit; The next call is a perfect example. I got 16:56:49 at 2377.
Do I just input 2377 into the "Other Delay" spot on PikaTimer and update, or is there something additional I have to do because the second changed?
When using Pikatimer, I never found that update delay to truly work.
What I do is, change the wanted delay to plus or minus delays, depending what I hit with the previous value.
So for my case, rather then updating the timer, you'd just change your wanted delay from 2381 to 2333 to just manually adjust it?
I'll give that a shot if the Update Timer turns out to be a bit wonky, but does this change in second matter for the purposes of PikaTimer, or should I just strictly be looking at the delays?
I'll give that a shot if the Update Timer turns out to be a bit wonky, but does this change in second matter for the purposes of PikaTimer, or should I just strictly be looking at the delays?
No, I wouldn't up date it that way. So say your target Delay is 1000. You just hit 1021. I'd drop the wanted delay by 21. So I'd put it at 979. See how close to 1,000 I get and continue that way. Sort of. Sometimes your wanted delay in Pikatimer won't even be near your wanted delay in game.
Yeah, my target delay is 2381 and I hit 2429, so I'd want to drop my delay by 48, to 2333.
Or am I missing something?
I'm still going at the update timer (about to abandon it to try your method).
My first call hit within the 16:56:50 range, after that I got a call in the 49 seconds.
I just updated the delay in the timer and I'm (ever-so-slowly) creeping up to 2381... in the 49 second bracket. Is this correct or am I now trying to hit the wrong seed?
Or am I missing something?
I'm still going at the update timer (about to abandon it to try your method).
My first call hit within the 16:56:50 range, after that I got a call in the 49 seconds.
I just updated the delay in the timer and I'm (ever-so-slowly) creeping up to 2381... in the 49 second bracket. Is this correct or am I now trying to hit the wrong seed?
Nah, that seems right. Give it a go and see what you get. You'll probably end up reducing it some more, but give it a go any ways.
Lower delays are easier for Pikatimer it seems.
I don't understand the question?
Well the delay I'm searching for is...
Date..........Time......Delay
2011/29/05 16:56:50 2381
The first call I got hit at
2011/29/05 16:56:50 2429
I updated PikaTimer and repeated the process. The next call hit at...
2011/29/05 16:56:49 2377
What do I have to do to PikaTimer in order to reflect this change in the seconds place occurring?
Because now all of my calls are occurring in the :49 second range. , which is an entirely different seed.
Date..........Time......Delay
2011/29/05 16:56:50 2381
The first call I got hit at
2011/29/05 16:56:50 2429
I updated PikaTimer and repeated the process. The next call hit at...
2011/29/05 16:56:49 2377
What do I have to do to PikaTimer in order to reflect this change in the seconds place occurring?
Because now all of my calls are occurring in the :49 second range. , which is an entirely different seed.
I've never encountered that problem, as whenever I used Pikatimer, I always hit the correct second. Possibly it's something you're doing incorrectly?
Well, that's my fear. D:
I'm going to start and try your method since PikaTimer just sent me through a 6-call long loop. >_>
If you have the time/boredom, towards the top of this page I listed pretty much my entire process to get me to where I am, except I've taken Zoap's suggestion and changed my calibration data to 14 seconds and 480 delay.
I'm going to start and try your method since PikaTimer just sent me through a 6-call long loop. >_>
If you have the time/boredom, towards the top of this page I listed pretty much my entire process to get me to where I am, except I've taken Zoap's suggestion and changed my calibration data to 14 seconds and 480 delay.
I always left calibration at 15 and 488 for calibrated. You might want to give that a try and see if it helps you.
It can't hurt. I adjusted PikaTimer the way you suggested and I actually hit 2383 delay, which is the closest yet.
However, it's in the :48 seconds time frame... >_>
However, it's in the :48 seconds time frame... >_>
I suggest trying to hit a second that your calibrated delay is set to. So in this case, 15. When abusing, even still to today. I've always hit seeds at 15 seconds xD!
Tried changing my wanted seconds (as well as everything in RNG Reporter to adjust for the date/time) and still hit a second below what I wanted, but was only 6 delays off.
So close, yet so far...
Perhaps if I increased my wanted seconds by one... would that compensate in the same way changing the wanted delay does in your process?
So close, yet so far...
Perhaps if I increased my wanted seconds by one... would that compensate in the same way changing the wanted delay does in your process?
Tried changing my wanted seconds (as well as everything in RNG Reporter to adjust for the date/time) and still hit a second below what I wanted, but was only 6 delays off.
So close, yet so far...
Perhaps if I increased my wanted seconds by one... would that compensate in the same way changing the wanted delay does in your process?
I haven't tried it before, but it seems more than logical to give it a go. Give it a try and tell me how it goes :D!
Just keep calm, be patient. It nearly took me 4 months to RNG my first 4th gen Poke :P
Tried changing my wanted seconds (as well as everything in RNG Reporter to adjust for the date/time) and still hit a second below what I wanted, but was only 6 delays off.
So close, yet so far...
Perhaps if I increased my wanted seconds by one... would that compensate in the same way changing the wanted delay does in your process?
Try starting the clock one minute later, when I hit a second above my target second I had to start the clock a minute earlier.
@Winters
4 months!? Clearly, you have far more patience then I do. :P
@Kiebin
So you're saying one second on RNG Reporter means a minute change on the DS clock?
Couldn't hurt to try.
So far, all my calls are landing in the right second. Using Winter's suggestion to manually adjust PikaTimer, right now I hit 2389, so I'm close. (:
I asked Zoap earlier but after I successfully hit my delay (2381), I obviously will have something other then 2381 in the "Desired Delay" field on PikaTimer. Is there a way or a formula to use that will allow me to adjust more current calibrated delay (480) so that I can find my seed more quickly/accurately?
Thanks again everyone for all your help.
Saving me such a headache... xD
4 months!? Clearly, you have far more patience then I do. :P
@Kiebin
So you're saying one second on RNG Reporter means a minute change on the DS clock?
Couldn't hurt to try.
So far, all my calls are landing in the right second. Using Winter's suggestion to manually adjust PikaTimer, right now I hit 2389, so I'm close. (:
I asked Zoap earlier but after I successfully hit my delay (2381), I obviously will have something other then 2381 in the "Desired Delay" field on PikaTimer. Is there a way or a formula to use that will allow me to adjust more current calibrated delay (480) so that I can find my seed more quickly/accurately?
Thanks again everyone for all your help.
Saving me such a headache... xD
Yeah, that's what I had to do when I used PikaTimer. When I switched to ZomgTimer though, I never hit a wrong second again.
Well, it was on and off. I just couldn't understand most of it. I didn't get a lot of help either. I got a shiny arbok, but couldn't RNG the IV's. Also did a shiny staryu in Plat but never did IV's either.
My first RNG was a Shiny hexflawless 0 Spe TR Ralts! :D!
Congrats! Almost there! No, you just have to test a bunch. Now, if you want to hit that delay again, you can use the same parameters you are using in Pikatimer now and abuse that delay later and you should get it relatively fast. Works very well with breeding too.
Woo!
I hit my seed!! :D
PikaTimer has my desired delay at 2335, but I was trying to hit 2381.
So from now on, should I subtract 46 from my desired delay in an attempt to hit it faster next time?
Alright. Now back to the tutorial to figure out exactly what to do next.
My goal here was just to catch any Pokemon to make sure I'm doing it right. My seed should give me a Flawless Docile Pokemon. If that's correct, then I can move to my goal of capturing a Flawless Ditto so I can breed flawless Pokemon (did I miss anything? :P ).
Honestly, I could care less about breeding shiny Pokemon. In my opinion, most of them just look awful. Except Beldum. Shiny Beldum should've been the regular color... js.
I hit my seed!! :D
PikaTimer has my desired delay at 2335, but I was trying to hit 2381.
So from now on, should I subtract 46 from my desired delay in an attempt to hit it faster next time?
Alright. Now back to the tutorial to figure out exactly what to do next.
My goal here was just to catch any Pokemon to make sure I'm doing it right. My seed should give me a Flawless Docile Pokemon. If that's correct, then I can move to my goal of capturing a Flawless Ditto so I can breed flawless Pokemon (did I miss anything? :P ).
Honestly, I could care less about breeding shiny Pokemon. In my opinion, most of them just look awful. Except Beldum. Shiny Beldum should've been the regular color... js.
It doesn't always work like that. It's weird, you have to test Pikatimer for each different delay. It's super weird, but after a while you ge tused to it.
What frame is your spread on? You have a sweet scent with you, correct? Saved in grass already?
I've made the first 12 Elm calls in order to make entirely sure I'm on the right seed, and they all match.
And no, I'm playing HeartGold so I don't have a sweet scenter but I am in the grass.
This is the line that JavaRNG gave me:
(DOCILE, ability 1) 31/31/31/31/31/31 (Seed: fb100958 Frame: 27) HP DARK 70
In the main RNG Reporter screen, I've entered my seed as fb100958 (the one I've been trying to hit), the max results to 27, and set to Method K.
Frame 24, however, is what RNG Reporter says that I'll get this Docile Flawless Pokemon. Does this mean I just need to advance the frame to 24 and then capture the Pokemon?
So since I made 12 calls, I'm at Frame 13. So I need to make 11 more calls to get to Frame 24, then capture?
I made an error.
And no, I'm playing HeartGold so I don't have a sweet scenter but I am in the grass.
This is the line that JavaRNG gave me:
(DOCILE, ability 1) 31/31/31/31/31/31 (Seed: fb100958 Frame: 27) HP DARK 70
Frame 24, however, is what RNG Reporter says that I'll get this Docile Flawless Pokemon. Does this mean I just need to advance the frame to 24 and then capture the Pokemon?
So since I made 12 calls, I'm at Frame 13. So I need to make 11 more calls to get to Frame 24, then capture?
I made an error.
Heartgold gets sweet scenters too, so I don't get the relevance of posting the game.
You are going to need one otherwise you could skip over your frame completely. Walking/turning in wild Pokemon areas causes 1 frame advancement. (Meaning grass, and places that randoms could pop up)
So without Sweet Scent you could walk around for ever skipping frames left and right and not hit anything you want.