So, I'm trying to figure out how to use emloop to hit higher delays today, and I've come across a problem. When I get to this step (in Syberia's guide):
----------------------------------------------------------------------------------------------------
Step 3:
Press the blue button on emloop, and note the value that appears in the yellow box. This is your delay converted to seconds, and is necessary for finding a proper date/time combination in RNGReporter.
Ignore anything after the decimal place, it's only the first two numbers that matter. Don't round, just cut them off. In this case, I would simply be using "12."
Step 3.5:
Not a requirement, but this can make things a lot less difficult in certain situations.
If the value you get for seconds is dangerously close to the next whole number (to be safe, anything that's .8 or higher), I would add 0.2 to the green box (so, enter 60.2 instead of 60) and use (seconds +1) as the value to look for in RNGReporter. This minimizes the effects of not resetting your game and starting Emloop at the exact same time, as it gives you closer to a whole second's margin of error, as opposed to at most 0.2 seconds.
For example, if my delay converted to 12.87 seconds, I'd enter 60.2 in the green box and search for things with a seconds value of 13 in RNGReporter.
----------------------------------------------------------------------------------------------------
I get a seconds value of 12.95. I adjust my pre-delay time to 60.2 to account for the adjacency of my seconds result to 13. My problem, however, is that I can't hit a target time of 13 seconds. My typical seconds range is 14-15. What do I need to adjust in order to make this work?