Every live-service game runs on a clock - daily quests, weekly raids, shop rotations, and battle-pass deadlines all hinge on a server reset time. The problem is that resets are defined in the server's time zone, not yours. Miss the conversion and you blow a daily streak, log in after a weekly raid has already locked, or buy a rotating shop item one day too late.
How game server resets work
Most resets fall into one of three patterns:
Fixed to a real time zone.
The reset is tied to a city - often US Pacific, US Eastern, or a publisher's home region (Tokyo, Seoul). These resets move with daylight saving time in that region.
Fixed to UTC.
The reset happens at a set UTC hour (e.g. 00:00 UTC). UTC never observes daylight saving, so these resets stay put year-round - but your local conversion shifts when your region changes clocks.
Regional servers.
Many games run separate NA, EU, and Asia servers, each resetting on its own regional clock. Make sure you're converting from the server you actually play on.
Common reset times by game type
| Pattern | Typical reset time | Notes |
|---|---|---|
| US Pacific daily reset | Early morning Pacific | Shifts ±1 hr with US DST |
| US Eastern daily reset | Midnight or early AM Eastern | Shifts ±1 hr with US DST |
| UTC-based reset | Commonly 00:00 UTC | Fixed in UTC; your local time shifts |
| Asia (KST/JST) reset | Early morning local | Korea & Japan don't use DST |
Worth knowing: Korea (KST) and Japan (JST) do not observe daylight saving time. Games run out of Seoul or Tokyo have rock-steady resets all year - the only thing that moves your local conversion is your own region's clock change.
How to convert a reset to your time zone
1. Find the source. Check the game's official site, patch notes, or community wiki for the reset time and its time zone (e.g. "daily reset at 4:00 AM PT" or "weekly reset 00:00 UTC"). 2. Convert once. Put the source city/zone and your own city into a time zone converter to get your local reset time. 3. Save it. Note your local reset for daily and weekly resets separately - they're often at the same clock time but on different days. 4. Re-check at DST. If the reset is tied to a DST-observing region (US, EU, Australia), or if you live in one, the converted time will shift by an hour twice a year.
The daylight saving trap
This is what catches dedicated players. If a game resets at 4:00 AM US Pacific, that's a fixed Pacific time - but Pacific time itself jumps an hour during US DST. So your local reset can suddenly land an hour earlier or later, even if you didn't touch your own clock.
The 2026 US daylight saving dates: clocks spring forward March 8 and fall back November 1. Europe shifts on March 29 and October 25, and Australia on April 5 and October 4. During the gaps between these dates, the offset between a US server and a European player is temporarily off by an hour - a classic source of "wait, why did the raid lock early?" confusion.
Pro tips for streaks and raid locks
- - Build a buffer. If a daily reset is the cutoff for a streak, do your dailies at least an hour before reset to absorb any DST drift or miscalculation.
- - Convert weekly resets separately. A weekly reset might be the same time as the daily but on a specific day - and a time-zone conversion can push it onto a different calendar day than the server's.
- - Double-check after server-region transfers. If you migrate from an NA to an EU server (or play with friends across regions), the reset zone changes with it.