Humanoid

The script on the page has been updated to take into account the timezone. So I think whatever timezone you are in it will count down to zero at the previously mentioned Jul 20, 2017 16:02:03.478 BST (and not Jul 20, 2017 16:02:03.478 local time). That is 15:02 GMT/UTC, which, with current daylight saving, is: 17:02 Europe daylight saving time, 11:02 am US Eastern time daylight saving, Jul21 00:02 in Tokyo, Ju;21 03:02 in New Zealand etc

On my machine, which is in BST, I think the counter will zero at Jul 20, 2017 16:02:03.478 BST which is 3:02pm GMT. But then again, i'm not sure how timezones work in website scripts, the timezone isn't specified in the code, which could mean that the counter looks the same in every timezone - i.e. it might zero 11 hours earlier than that in New Zealand.

To mess with our heads is probably the real reason. The code on the page works out a duration in days, say like 2.222199999999999 Where 2 is the days and the .222... is a fraction of a day. Then is works out the hours, minutes, seconds and thousands of a second of that fraction of a day to display. When the seconds bit is worked out you should have 0-59 seconds, There are 3600 seconds in a hour but the code uses 360 instead. So the 'seconds' are a factor of ten out, 59 = 5.9, 58 = 5.8 etc down to 1 second = 0.1 the 'seconds' are then rounded down for the counter display, 5.9 rounds down to 5 etc, so it displays 5, 4, 3, 2, 1, 0.

I got it to be a few minutes earlier: Jul 20, 2017 16:02:03.478 a: -13.959762476851852 f: 16.965798105324073 x: -3.006035519776493 in the code change: var now = new Date().getTime(); to var now = new Date("Jul 20, 2017 16:02:03.478").getTime(); and the counter is: 00:00:00:00.000

Bradley's Robot 3/B1 - yeah!