Thanks... is there a reason why though?
Btw, I seem to be having some issues with RNGing...
every time I check my Elm Responses in seed to time, I always get no results. So I change my Delay and seconds parameters naturally, and turns out I'm hitting a frame 20+ above my target (I'm trying to hit 632), and I'm hitting 47 seconds instead of 50. I feel like I'm starting my EonTimer and DS Clock at the same time, but I'm ending up with VERY crazy results. I also feel like I'm booting my game and starting my game at the right time (which should be right at the last tick on the EonTimer if I'm correct)
It should be my error, correct? I've gotten these types of results 5 times in the past 7 attempts, the other 2 attempts I've hit +/-10 near my target delay.
This is a little older but I didn't see any answers so seems likely that you're getting a wrong result. There shouldn't really be any reason to change the +/-seconds part in the seed to time window.
I changed the calibrated delay to 564 at some point, and I got Kanto, Kanto, Pokerus, Pokerus, which was the farthest I have yet. But I never got anything like that afterward with 564.
Should I change the target delay?
@ ToastPlusOne: I'll try that and come back
Fyi, you shouldn't need to change the calibration manually. The defaults should be close and the rest should be easily taken care of by the update function.