Time zones (server and member)

Coordinating an alliance across a global roster means two different clocks have to agree. The platform tracks both separately:

• The server clock — derived automatically from the alliance's reset time. An optional fixed-offset override is available if the game clock and reset do not line up.
• Your local clock — detected from your device for displayed times and time-entry controls. Your saved profile time zone remains the source for availability and attendance analysis.

Officers set the reset using their own local clock in alliance settings and member time zones live on each profile.

Start in Settings → General and enter server reset using the local time shown on your own device. Last Command converts it to UTC internally and derives the fixed game-server clock. The separate Server timezone panel is an override for unusual server clocks, not a normal setup requirement.

1. 1

   Open Settings → General

   Set Server reset time using the local time displayed beside the control. You do not need to convert it to UTC.
2. 2

   Use Local by default

   Event times are shown in the viewer's device timezone. Use the Local / Server switch in the dashboard header or iOS command drawer when you want to compare with the game clock.
3. 3

   Override only when needed

   If Server mode does not match the game, open Server timezone and enter the game's current Server Time or choose its fixed offset directly.

For example, if an officer in Los Angeles selects 18:00 for reset, Last Command saves the corresponding instant. A member in Berlin might see 03:00 while a member in India sees 07:30. They are all looking at the same reset, converted for their own location.

Local display uses the current browser or device timezone, so members do not need to configure anything before event times are correct. It also follows daylight-saving changes and travel automatically. The timezone saved beside profile availability is used for background attendance and availability analysis when that member is not actively viewing the screen.

With the server offset and member time zones both set, the platform can convert any alliance event into each member's local wall-clock time. That drives two things:

• Opportunity-adjusted attendance — an event landing at 2am your time isn't counted against you like one in your evening. The clocks are what make that judgement possible.
• Blood Night and season coverage — knowing when each member is awake lets officers see who can realistically cover a given window rather than guessing.