Here’s what happened. The cron job that does the nightly rollver runs at a fixed time every day (7am.) Since the server updates for DST, this automatically changed to an hour earlier as it should have.

The code that I use to tell us when there’s a new rollover looks like this:

  def self.next_reset
    if (Time.now > (Time.now.midnight + HOUR_RESET.hours))
      Time.now.midnight + 24.hours + HOUR_RESET.hours
    else
      Time.now.midnight + HOUR_RESET.hours
    end
  end

In other words, depending on whether the reset has already occured today, it’s either HOUR_RESET after midnight today or HOUR_RESET after midnight tommorow.

This code works great, except on DST. HOUR_RESET, which is set to 7, will happen at the wrong time, since it’s actually 8 hours after midnight on the rollover date only.

So there’s a bug in that function that has to be fixed. It was a cosmetic bug only, and is already back on track.

As for losing visits, I imagine it only affected a very small percentage of people who were saving up their visits for Domination. In fact, until I saw this thread I didn’t know anyone had been affected by it at all: neither of the two people posting here reported it.

Sure, it’s more fun to **** about your lost visits in Flamebate, but if you care about getting your visits back, why not you know, actually report it to me? There’s no way for me in code to determine whether you were saving up visits and lost your chance due to the timer messing you up, so I couldn’t do it automatically.

Especially if you are playing compeitively, you have a responsibility to report things that have affected you. You know it’s not uncommon for us to grant extra visits in the event in cases like these, and I’ll certainly work with whomever was affected!