Reminders
Let members set their own reminders with /reminder — one-off or repeating.
Personal reminders your members set themselves — with a dashboard page that shows everything scheduled across your network.
Commands
/reminder set when:2h message:Raid starts
/reminder set when:20:00 message:Daily standup repeat:True
/reminder set when:friday 20:00 message:Scrim repeat:True
/reminder cancel number:3
/reminder list
repeat and dm are optional on/off switches. dm:True sends the reminder to the member's DMs instead of the channel.
When
when takes either a relative span or a clock time.
Relative
| You type | You get |
|---|---|
30m | in 30 minutes |
2h | in 2 hours |
1d | tomorrow, same time |
1w | in a week |
1h30m | in 90 minutes |
Units are seconds, minutes, hours, days and weeks (s m h d w), and you can combine them.
Clock times
| You type | You get |
|---|---|
20:00 | today at 20, or tomorrow if it's already past |
friday 20:00 | the next Friday at 20 |
2026-09-01 20:00 | that exact date and time |
Weekday names work long or short (friday, fri). Times are read in your network's timezone, which you set under Settings › General — so 20:00 means the same thing here as it does for events and birthdays. Networks without a timezone are treated as UTC.
With repeat
repeat:True uses the rhythm of what you wrote, not the gap until the first firing:
| You wrote | It repeats |
|---|---|
2h | every 2 hours |
20:00 | daily |
friday 20:00 | weekly |
2026-09-01 20:00 | not at all — a fixed date is refused with a hint |
Limits
The shortest reminder is 1 minute from now, the longest 1 year.
Months and years aren't units, because they aren't a fixed length. Use 4w for about a month and 52w for about a year. Fractions don't work either — write 30m, not 0.5h.
Anything CloudMod can't read is refused with a hint that names the problem. It never guesses at a time.
Delivery
A reminder fires in the channel where it was set, or in the member's DMs if they chose dm:True. If those DMs are closed, it lands in the channel instead rather than being dropped. repeat:True keeps it firing on the same interval until the member cancels it.
A repeating reminder keeps its original time. If the bot is briefly offline it catches up on the next run without drifting later and without firing every interval it missed.
Each member can have 25 reminders per server at a time. You can change that on the Reminders page (1–100).
The dashboard page
Plugins › Reminders lists everything queued across your network — next one first, with who set it, when it fires and whether it repeats. Each row has a delete button.
Switching the plugin off deletes every scheduled reminder immediately. There's no grace period and no undo — turning it back on starts from empty.
That list is the only way to remove someone else's reminder. Members can cancel their own with /reminder cancel, but if someone leaves or asks you to delete what CloudMod stores about them, this is where you do it. Deleting is immediate and the member isn't notified.
Two settings live on the same page:
- Allow delivery by DM — on by default. Turn it off and every reminder lands in the channel, including ones members set with
dm:True. - Reminders per member — the per-server quota, 1 to 100.
Good to know
- Reminders survive bot restarts — they live in the database, not in memory.
/reminder listand/reminder cancelonly ever show a member their own reminders.- Replies are ephemeral: nobody else in the channel sees what someone set.
Requirements: Send Messages and Embed Links in the channel where reminders should land.