Daylight savings start time errors

[stugots]

Just my annual reminder to those BF users out there that may not be aware that every year on this special day they manage to stuff up the start times of many Aussie meetings.

Some are showing an hour before jump time, some an hour after, have fun linking up your bots etc, I know I always do...

[The Ocho]

Thanks stugots. Yes always fun and games.

[Michal]

Ahh a bit of nostalgia.

My bot deals with this by using external references for start times. So I have no issues. This is due to the fact that I was 'revolutionary' in my approach when I built it. By that I mean that BF couldn't even work out that start times change for the first 5 years of their AU operation. So once a race was put back all the best laid plans went to s... So I must have been doing something 'revolutionary' that they couldn't?? :). Its funny looking back.

On that front nothing changes we still deal with errors every day so that our clients don't have to.

[UselessBettor]

If a bot is written correctly then it should use the markettime field. This is a long (which is a very large number in programming) with the number of seconds since a certain date. So regardless of display time the timing of your bot should be spot on.


I have noticed numerous display time errors today but the actual markettime field has been perfect. There has been no issues at all if using this field.

[stugots]

Yes, it's not really an issue of 'things not working', rather just a PITA linking up to excel.

There really is no excuse for this to be a continuing issue year after year.