Timezones

Members set their timezone once, and Qreate reuses it wherever people have to find a time together.

Set it up

1. Tell members to run /timezone set in Discord. A city works, and so does the name people actually use: mountain, MST, pacific, eastern, CET, or an offset like GMT-7. The suggestions show the current local time in each one, so they can confirm they picked the right place.
2. Members do not need a Qreate account. Server admins can enable optional band roles on the Timezone Bands page.
3. Anyone travelling can add a number of days, and Qreate forgets the temporary timezone again afterwards.

What to know

• Members save usual weekly hours with /availability set, using their own timezone. Overlap finds shared hours over the next seven days, rather than checking live presence.
• Private availability is shown only as shared hours in the asker's zone. Q reads exact zones, local times and windows only when allowed; offset-only shares a band and hidden shares nothing.
• Timezone Bands shows members per band and available members at each UTC hour over the next 24 hours. Counts below three are suppressed. Band roles need Manage Roles and a bot role above them.
• Automations can use member_local_hour with config.from and config.to from 0 through 23. Both end hours are included, and a range across midnight wraps. An absent or expired member zone does not match.
• Qreate stores the timezone by name, not as a fixed offset, so daylight saving is handled for you. A member who set their timezone in July is still correct in December.
• /timezone compare tells a member how far apart they and somebody else are, and what time it is for the other person right now.
• Members choose how much other people see with /timezone privacy: their timezone, only how far apart you are, or nothing at all. On the last two, no reply anywhere names their local time. The strictest setting still lets Qreate match them with people who share their hours, it just never names where they live or what their clock says.
• Where it shows up today: LFG lobbies list each player's local time and how far they are from the host. Event cards have always shown times in each viewer's own local time, so they need no timezone set.
• A member is never asked for their city as such. Qreate stores a real zone either way, so somebody who says mountain and somebody who picks Denver are stored identically, and a timezone is shown by its name, Mountain Standard Time rather than America/Denver.
• Timezone is never guessed. A member who has not set one simply has no local time shown, and nothing else about the server changes.