Durations & time
How to write durations, and how Ledra handles time zones.
Writing a duration#
Anywhere Ledra asks for a duration — /timeout, /tempban, /remind,
/announce — the same format applies.
| Unit | Accepted spellings |
|---|---|
| Seconds | s, sec, secs, second, seconds |
| Minutes | m, min, mins, minute, minutes |
| Hours | h, hour, hours |
| Days | d, day, days |
| Weeks | w, week, weeks |
Valid:
30s 30 seconds
10m 10 minutes
2h 2 hours
7d 7 days
1w 1 week
1d12h 1 day and 12 hours
2h30m 2 hours and 30 minutes
1w2d3h 1 week, 2 days and 3 hours
30 minutes spaces are fine
Combine as many units as you like; they add up.
No months or years. Their length is ambiguous, so Ledra does not guess.
Use 30d or 365d.
Anything unparsable is refused, not ignored. 10m please gives an error
rather than silently becoming 10 minutes. Nothing scheduled is ever a guess
about what you meant.
Duration limits#
| Where | Minimum | Maximum |
|---|---|---|
/timeout |
— | 28 days (Discord's own cap) |
/tempban |
— | 365 days |
/remind |
30 seconds | 365 days |
/announce interval |
15 minutes | 365 days |
Times of day#
/announce create accepts an optional time in 24-hour format:
time:09:00
time:18:30
time:23:45
With a time set, the interval must be whole days — 1d, 3d, 1w.
Time zones#
/settings timezone name:Europe/Berlin
Uses standard IANA names (Europe/Berlin, America/New_York, Asia/Tokyo,
Australia/Sydney). The option autocompletes as you type, and the reply shows
the current local time there so a typo is obvious.
Default is UTC.
What the time zone affects#
Only announcements with a fixed posting time.
Everything else — case timestamps, reminder times, log entries — uses Discord's own timestamp format. Each member sees those in their own local time automatically, so no server setting is involved.
Daylight saving#
Handled. An announcement set for 09:00 posts at 09:00 all year, on both sides of the switch, even though its distance from UTC changes.
How precise is scheduling?#
Ledra checks for due work every 30 seconds. A reminder set for 14:00 arrives between 14:00 and 14:00:30.
That is why the minimum reminder is 30 seconds — anything shorter could not be delivered honestly.
After downtime#
The two features behave differently, on purpose:
| Feature | Behaviour |
|---|---|
| Temp-bans | Expired bans are lifted at the next start |
| Reminders | Delivered late, marked "Delivered late" |
| Announcements | Missed slots are skipped, never replayed |
A missed personal reminder is still useful. Forty-eight copies of "read the rules" are not.