Write one time and let every member see their local time.

Personal command

Configure once

Choose a standard worldwide timezone name such as America/New_York, Europe/Warsaw or Asia/Tokyo. These are sometimes called IANA timezones. The setting belongs to the Discord account, not to one character, and remains available when the main character changes.

The timezone selector is also available from the Registration panel. Both entry points update the same account setting.

Registration

The first character guides missing timezone setup

If no timezone exists, the registration panel asks for it inside the same guided flow before verification continues. Once stored, failed or repeated registrations do not ask again.

Event scheduling

Creator input, viewer output

1. The creator enters a date in their configured timezone.
2. Luminox converts it to one absolute instant.
3. The event panel stores and displays a Discord timestamp.
4. Each viewer sees the same instant rendered in their local Discord client.
5. Opening Edit event preserves that stored instant instead of silently rebuilding it from the bot host timezone.

Event creation requires a configured timezone to prevent silent server-time assumptions. Changing the account timezone later does not rewrite already scheduled absolute event times.

Natural input

Multiple friendly expressions

Message conversion

Apps → Convert time or react with 🕒

Use the message context command or the clock reaction on a message containing a time. Luminox compares the author's timezone with yours. The context-menu result is a private temporary response; a reaction uses a short public message because Discord reactions cannot open a private response.

Reaction results are removed automatically after a short reading window. If you have not configured a timezone, Luminox stops the conversion and shows a temporary clickable link to /timezone set; after saving it, react again.

Friend Time limits

Clock conversion stays intentionally predictable

• Friend Time recognizes explicit 24-hour values such as 9:00, 17:30 and 23:45.
• One message can expose up to five distinct times.
• Commands and common command-prefix messages are ignored.
• It converts times using the message date; it does not interpret phrases such as “next Monday”, “in three days” or date ranges.
• Natural dates belong to the Event creation parser, where the creator explicitly confirms the final scheduled instant.

Examples

Choose the correct tool