One instant can have different calendar dates.

Clock labels need a reference

A time zone gives local clock time a relationship to a common reference. UTC is the reference used for the 3 SECONDS Daily reset. Daylight saving changes the local offset in places that observe it; it does not move the game’s reset away from 00:00 UTC.

Walk through an example

Imagine one player at UTC+2 and another at UTC−5. At 00:30 UTC, the first player’s clock reads 02:30. The second reads 19:30 on the previous calendar date. They are looking at the same instant with different local labels.

These are hypothetical offsets, not a claim about the current rules in particular countries. Real locations can change offsets seasonally, and their rules are not all identical.

Why “midnight” is incomplete

If a friend says “the challenge changes at midnight,” ask: midnight where? Without that reference, the statement is not enough to schedule a shared event. Including UTC or an explicit local zone turns a vague instruction into one you can use.

Likewise, a date by itself is not a worldwide instant. A calendar page changes at different moments for different local clocks. This matters for game resets, travel plans and remote meetings.

In the game

Daily uses one UTC date so players on compatible settings receive the same daily sequence regardless of their local midnight. Local records and the visible date should make that choice understandable.

When checking a reset, compare the stated UTC day first. Do not assume a new local date means a new Daily has begun. The shared reference is what makes the competition shared.