No problem. I know that you can use save states to abuse the FR/LG RNG, but I was referring to pure cartridge abuse, where save states are obviously impossible.
As for PikaTimer, I'd like to see something that would make it a bit easier to nail the soft reset more accurately. Although there is the pinging, at least on my computer, it appears to start somewhere in the middle of any given second, rather than at 2.00, 1.00, 0.00, etc., and the pings are sometimes out of sync (the time between pings sometimes seems slightly different). The length of the ping is, in my opinion, a bit too long for it to be used accurately for what it's intended for. I personally like the length of the Emloop ping. It's short enough so that, if you follow along with the rhythm, you can more accurately predict the timer hitting 0:00 than you could with a ping who takes half a second. Pings in Java are one thing I do NOT have any experience with; are there more pings available for the program to cause besides Windows' Default Beep? I also think that the timer could be a bit easier to nail if either the text or a small area surrounding the text flashed a different color for a slight bit (maybe for 0.25 seconds or so?) at the start of every second (at every X.00) within the last 5/10/whatever. That might make a nice rhythm for the user to follow, since the actual numbers are going by so quickly. This would apply to both the first and second timers. It might also be useful to have a checkbox where the user could toggle the pinging (or possibly the flashing) on or off, and maybe even an extra text field where the user can input the time at which they'd like the pinging (or possibly the flashing) to start, like Emloop has.
I hope that makes sense; I'm finding it a bit difficult to put some of these thoughts, particularly about the pinging, into words.