Scheduled announcements
Write it now, post it later - once, or every week.
Write an announcement and give it a time. Arklynn posts it then, whether or not you are awake. It uses the same embed script as everything else, so anything you can announce you can schedule.
First, the timezone
Do this once, before anything else. Times are read in the server's timezone, and if nobody has set one the bot assumes Europe/Berlin. Typing 18:00 and getting a post at 14:00 is the kind of thing you discover afterwards.
/schedule timezone name: Europe/BerlinAny IANA name works: America/Sao_Paulo, America/New_York, Asia/Tokyo. Run it without a name to see what is currently set and what the time is there right now.
Scheduling one
- 1Run /schedule add. It wants a time and a message; the channel defaults to the one you are in.
- 2Write the time in whatever way is natural - see the table below.
- 3Write the message as plain text, or as an embed script for something that looks made.
- 4It answers with a number. That number is how you cancel or pause it.
- 5Check /schedule list. Every entry shows its channel and a countdown.
| You type | It means |
|---|---|
2h | Two hours from now. |
30m | Thirty minutes. |
1d 6h | A day and six hours. |
3d | Three days. 1w for a week. |
18:00 | Six in the evening today - or tomorrow, if it is already past. |
05.10. 18:00 | The fifth of October at six. |
2026-10-05 18:00 | The same, written the other way. |
2026-10-05 | That date at nine in the morning. |
/schedule add when: 18:00 message: Server event starts now, see you in voiceRepeating
The repeat option takes once, daily, weekly or monthly. A weekly post keeps its weekday, and a monthly one keeps its day of the month - the 31st becomes the 28th in February and then goes back to the 31st in March, rather than sliding to the 28th forever.
Managing them
| Command | What it does |
|---|---|
/schedule list | What is waiting, when, and which of them are paused and why. |
/schedule cancel | Delete one, by its number. |
/schedule pause | Stop one without deleting it. Add resume to start it again. |
/schedule timezone | What 18:00 means here. |
Up to 50 announcements can wait at once, and every one of them can repeat.
Things worth knowing
- A broken script is refused when you schedule it, not at three in the morning. The message is checked immediately.
- Nothing pings unless you could ping. An announcement with @everyone in it only pings if you are allowed to - checked at the moment it posts, not when you wrote it.
- If you lose Manage Server, or leave the server, your scheduled posts stop and say so. They are paused rather than deleted, so somebody who does have the permission can resume them. Nobody should be able to leave a year of weekly posts behind on their way out.
- If the bot was down when something was due, it posts once on the next check - not once per missed window.
- If the channel is deleted, that announcement pauses and tells you why rather than failing quietly every week.
Commands
Loading commands…