"Remind me to post the event at 8." In most servers that means someone sets a phone alarm and hopes they're at their desk. CloudMod keeps the reminder where the event actually happens — in Discord — so it pings the right person in the right place at the right time.
One command, natural timing
A member runs /reminder set with a when and a message. When it's due, CloudMod pings them — in the channel, or by DM if they'd rather keep it private. No calendar, no external app, no leaving Discord.
when takes either a delay or a clock time:
/reminder set when:2h message:Raid starts
/reminder set when:20:00 message:Daily standup
/reminder set when:friday 20:00 message:Scrim
Clock times are read in your network's timezone — the one you set once under Settings › General, the same one events and birthdays use. So 20:00 means 20:00 to everyone on your server, not 20:00 UTC.
Anything CloudMod can't read is turned down with a hint that names the problem. It never guesses at a time and quietly picks the wrong one.
One-off or repeating
Switch repeat on and the reminder keeps coming — on the rhythm of what you wrote, not the gap until the first one. 2h repeats every two hours, 20:00 repeats daily, and friday 20:00 repeats weekly. That last one is the "start the weekly voice night" case, and it keeps its 20:00 for good: a repeating reminder stays on its original time instead of drifting a little later every week.
/reminder list shows what's queued and /reminder cancel clears anything you no longer need, so it never turns into a pile of forgotten pings.
Personal, not admin overhead
Because members set their own reminders, there's nothing for staff to manage day to day. It's a quality-of-life tool that lives quietly in the background and only speaks up when someone asked it to.
Admins do get one view: Plugins › Reminders in the dashboard lists everything scheduled across the network — who set it, when it fires, whether it repeats — with a delete button on each row. That's there for the moment someone asks you to remove what the bot stores about them, and for the two settings that live alongside it: whether DM delivery is allowed at all, and how many reminders one member can queue per server.
A note on Alpha
Reminders is currently an Alpha plugin — it's fully usable and safe to switch on, just newer than our stable features, so it's had less mileage. If anything feels off, that feedback is exactly what moves it to stable, so tell us. Nothing about it will surprise a member: it's a slash command that pings you when you asked.
Getting started
Enable the Reminders plugin, then try /reminder set when:10m message:test to see the flow end to end. Once you've watched one land, /reminder list and /reminder cancel are all you need to manage the rest.