Ok. I'm not a fan of getTimer because CPU cycles can actually vary
based on power draw in modern CPUs. So I used a gettime approach,
it's a little less percise but good enough for determining this stuff. I
also use a leading and trailing bit of text so I can time just the macro,
factoring out my ping.
Code:
# ---------------------------------------------------------
setVar $macro "m20210*<"
# ---------------------------------------------------------
killTrigger macro_start
killTrigger macro_end
setTextLineTrigger macro_start :macro_start "Average Interval Lag:"
setTextLineTrigger macro_end :macro_end #179 & "Turns "
setVar $macro "@" & $macro & "/"
send $macro
pause
# ---------------------------------------------------------
:macro_start
getTime $start "hh mm ss zz"
pause
:macro_end
getTime $end "hh mm ss zz"
getWord $start $hh 1
getWord $start $mm 2
getWord $start $ss 3
getWord $start $zz 4
setVar $start_mm (($hh * 60) + $mm)
setVar $start_ss (($start_mm * 60) + $ss)
setVar $start_ms (($start_ss * 1000) + $zz)
getWord $end $hh 1
getWord $end $mm 2
getWord $end $ss 3
getWord $end $zz 4
setVar $end_mm (($hh * 60) + $mm)
setVar $end_ss (($end_mm * 60) + $ss)
setVar $end_ms (($end_ss * 1000) + $zz)
setVar $elapsed ($end_ms - $start_ms)
echo ANSI_14 & "**Elapsed: " & $elapsed & "ms**"
halt
# ---------------------------------------------------------
$macro: "m20210*<"
Elapsed: 361ms
$macro: " m20210* < "
Elapsed: 149ms
$macro: " m20210*< "
Elapsed: 186ms
$macro: "ddddd"
Elapsed: 77ms
In a 6 way
setVar $macro "ddddd"
Elapsed: 121ms
Interesting how display sector takes so much time.
So let's try move w/o displays.
$macro: " m 3789* < "
Elapsed: 165ms
Obviously no move delay there
What about a longer run?
$macro: " m2855* m19838* m21118* m8965* m2862* m29533* m20526* m25307* "
Elapsed: 207ms
What about a twarp?
$macro: " m5* y y p t * * * m 206 * y y "
Elapsed: 403ms
What about without getting ore?
$macro: " m5* y y m 206 * y y "
Elapsed: 0ms !!!
So I do believe this confirms that there is no move delay in the beta.