Skip to main content

Time zones (server and member)

Two clocks matter in Last Command: the game server's fixed UTC offset (set once by an officer) and each member's own local time zone (self-set). Line them up and the platform can judge attendance fairly and work out Blood Night coverage across the roster.

// ON THIS PAGE

Two clocks

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

  • The server offset — the fixed UTC offset your in-game server runs at. One value for the whole alliance, set once by an officer.
  • Your member time zone — where you actually are, set on your own profile. Every member sets their own.

Neither is guessed. The server offset lives in alliance settings and member time zones live on each profile.

The server offset (officers)

Last War servers run at a fixed UTC offset and never observe daylight saving, so the offset is set once and left alone. An officer sets it under Settings → Server timezone, and the whole alliance then shares one source of truth.

  1. 1

    Open Settings → Server timezone

    The panel shows the current offset (for example UTC+2) and the server's live wall-clock time so you can sanity-check it at a glance.
  2. 2

    Not sure of the offset? Use the helper

    Open the game, read the time it labels as Server Time, and type that into the helper. The platform compares it to UTC right now and derives the offset for you, rounded to the nearest half hour. Hit "Use this" to save it.
  3. 3

    Or pick the offset directly

    If you already know it, choose from the dropdown — every real offset from UTC−12 to UTC+14 in half-hour steps. Saving revalidates the pages that depend on it immediately.

// NOTE

The server offset is an officer setting (R5/R4). Members don't need to touch it — once it's set, everything downstream just works.

Your own time zone (members)

Every member sets their own time zone on their profile, next to availability. Pick it from the list, or tap the shortcut to use the one your browser already detected. The panel confirms the current local time in your chosen zone so you know you've picked the right one.

// TIP

This is the single most useful thing an ordinary member can do for fair scoring. Set it once and officers can tell a 2am-local match from an 8pm-local one — see attendance.

What they power together

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.

// HEADS UP

If the server offset is wrong, every derived local time is wrong with it — attendance and coverage both skew. If the numbers look off, re-check the offset with the helper first.
// PREVAlliance settings// NEXTNotification preferences