For people with homebrew, there's an even easier method using the 3DS Alt Settings app.
We don't have Gen 5 tools yet, but the 3DS Alt Settings app works for Gen 5 RNG too.
The Problem
A common issue with NDS RNG on 3DS is inconsistent second values. It's often blamed on TwilightMenu or NDS launch delays, but I was skeptical.If launch timing was truly the cause, soft resetting when your timer beeps (the common RNG approach) should fix it, but it doesn't.That made me suspect the issue occurs earlier in the process.
The Hypothesis
The real issue, if not the only one, seems to be how the 3DS sets the system time.On many modern systems, manually setting the clock doesn't clear milliseconds, so your system time can carry leftover ms from before the change. For example, setting the time to 14:32:00 with 927ms internally results in 14:32:00.927.If the 3DS has the same behavior, the 3DS time would be one second off in just a few milliseconds.
The Tests
I wrote a research plugin to log timing info in System Settings every frame. Here's what to know from the screenshots:
Now = current system time
Changed at = frame right before the time was set
Measured after change = frame right after
Preview
Preview
Findings:
In the first screenshot, the ms portion remains unchanged after setting the time - confirming the hypothesis.
In the second screenshot, after setting the time to 14:32 at 987 ms, the clock displayed 14:32:01 in less than one second - showing the issue is reproducible.
Findings:
We don't have Gen 5 tools yet, but the 3DS Alt Settings app works for Gen 5 RNG too.