The rule states "Timer starts as soon as inputs are possible." I did some testing, and inputs don't register until about .75 seconds after the walk cursor shows up, slightly after the first screen loads in. (There seems to be some variability to within a tenth of a second.)

Was the intent of the rule to be when the walk cursor appears? If so, then I think that ought to be clarified. If the rule was meant as written, then SantaClaus may want to retime his run, as I think it would be faster than what's currently noted.

Good point. I actually retimed the recent runs in milliseconds to when the walk symbol shows up, as this is the only strict visual cue we have. Will clarify the rule, as long as there's no objection against it. (but timing the runs 0.75 after the cursor shows up seems unnecessary complicated imho)