Skip to content

Reminders

Reminders keep your kingdom on schedule. The bot has built-in reminders for two recurring events, Ancient Ruins and the Altar of Darkness, and it can also send any custom recurring reminder you define. Once a reminder is set up, it runs on its own: the bot posts a message in your chosen channel ahead of each occurrence and pings the role you set, so members who opted in never miss the event.

For Ancient Ruins and the Altar, the bot posts a role menu in the channel. Members use it to subscribe to the pings they want.

TierPatron
Command/reminder setup, deactivate, custom, delete, list
Who can useAdmins (Administrator or Manage Server), or the server’s Bot Admin role
Also on dashboardNo

You tell the bot the date and time of the first occurrence, how far ahead to remind, and which channel to use. From then on the bot checks for due reminders every minute and posts them at the right times.

  • Lead-time pings. Choose any combination of 1 hour, 4 hours, and 8 hours before the event, or set your own list of intervals (for example 1d, 4h, now). now sends a ping right at the event’s start time.
  • Built-in events. Ancient Ruins and the Altar of Darkness each get their own subscribable role and a shared role menu in the channel.
  • Custom reminders. Define your own event with a title, a start time, and a repeat interval. Custom reminders can ping a role you pick, or no role at all.
  • Optional Discord events. Any reminder can also create a Discord Scheduled Event for each occurrence.

All dates and times you enter are in UTC, in the format HH:MM DD/MM/YYYY (for example 20:00 25/12/2026).

When a command asks for an interval or a repeat, use a number followed by a unit:

  • d for days, h for hours, m for minutes (and s for seconds in custom_intervals).
  • Examples: 2d (2 days), 40h (40 hours), 30m (30 minutes).
  • In custom_intervals, now means “ping at the start time.”
  • For repeat_interval on a custom reminder, use 0 to make it a one-time reminder.

Set up reminders for Ruins or Altar in a channel.

OptionTypeRequiredDescription
channelText channelYesThe channel where reminders will be sent.
reminder_typeAncient Ruins / Altar of DarknessYesThe type of event to set up reminders for.
first_instanceTextYesThe date/time of the very first event instance. Format: HH:MM DD/MM/YYYY. Must be UTC.
last_instanceTextYesThe final date/time for which reminders should be active. Format: HH:MM DD/MM/YYYY. Must be UTC.
reminder_1_hourTrue / FalseNoSend a reminder 1 hour before. Defaults to off.
reminder_4_hourTrue / FalseNoSend a reminder 4 hours before. Used as the fallback if you pick no other interval.
reminder_8_hourTrue / FalseNoSend a reminder 8 hours before. Defaults to off.
custom_intervalsTextNoComma-separated list, for example 1d, 4h, now. now sends a ping at start time. Overrides the 1/4/8-hour toggles.
discord_eventsTrue / FalseNoCreate a Discord Scheduled Event for each instance. Defaults to off.

Behavior:

  • If you do not pick any interval (no toggles and no custom_intervals), the bot defaults to a single 4-hour-before reminder.
  • If a reminder of the same type is already active, the bot tells you and stops. Use /reminder deactivate first.
  • If you turn on discord_events, the bot needs the Manage Events permission.
  • The bot creates the Ruins and Altar roles if they do not exist, and posts (or reuses) a role menu in the channel so members can subscribe.

Example

/reminder setup channel:#reminders reminder_type:Ancient Ruins first_instance:12:00 01/07/2026 last_instance:12:00 01/07/2027 reminder_4_hour:True reminder_1_hour:True

Deactivate Ruins or Altar reminders for this server.

OptionTypeRequiredDescription
reminder_typeAncient Ruins / Altar of DarknessYesType to deactivate.
keep_rolesTrue / FalseYesKeep roles for future use.

Behavior:

  • Turns off the chosen reminder type and removes the reminder messages it sent. If it created Discord events, those are removed too.
  • The shared role menu is removed once both Ruins and Altar are inactive.
  • If keep_roles is False, the Ruins and Altar roles are deleted once neither type is active. Set it to True to keep the roles for later.

Example

/reminder deactivate reminder_type:Altar of Darkness keep_roles:True

Set up a custom recurring reminder.

OptionTypeRequiredDescription
titleTextYesThe title of the custom event, for example VIP Shop Reset.
channelText channelYesThe channel where reminders will be sent.
first_instanceTextYesThe date/time of the very first event instance. Format: HH:MM DD/MM/YYYY. Must be UTC.
repeat_intervalTextYesHow often the event repeats, for example 2d, 40h, or 0 for one-time.
last_instanceTextYesWhen to stop reminding. Format: HH:MM DD/MM/YYYY, or 0 / never. Must be UTC.
role_to_pingRoleNoA role to ping when the reminder is sent.
reminder_1_hourTrue / FalseNoSend a reminder 1 hour before. Defaults to on.
reminder_4_hourTrue / FalseNoSend a reminder 4 hours before.
reminder_8_hourTrue / FalseNoSend a reminder 8 hours before.
custom_intervalsTextNoComma-separated list, for example 1d, 4h, now. now sends a ping at start time. Overrides the 1/4/8-hour toggles.
discord_eventsTrue / FalseNoCreate a Discord Scheduled Event for each instance. Defaults to off.
event_lengthTextNoRequired if discord_events is True. The event duration, for example 1h or 30m.

Behavior:

  • Unlike Ruins and Altar, a custom reminder does not create a role or a role menu. It pings only the role you pass in role_to_ping, if any.
  • Set repeat_interval to 0 for a one-time reminder. For a repeating reminder, set last_instance to a date, or to 0 / never to repeat indefinitely.
  • If you turn on discord_events, you must provide event_length, and the bot needs the Manage Events permission.
  • Each custom reminder is given a numeric ID. Use /reminder list to find it, and /reminder delete to remove it.

Example

/reminder custom title:VIP Shop Reset channel:#reminders first_instance:00:00 01/07/2026 repeat_interval:1d last_instance:never role_to_ping:@Shoppers reminder_1_hour:True

Delete a custom reminder by its ID.

OptionTypeRequiredDescription
reminder_idNumberYesThe ID of the custom reminder to delete.

Behavior:

  • Removes the custom reminder and any Discord events it created. Find the ID with /reminder list.
  • This command only deletes custom reminders. To turn off Ruins or Altar, use /reminder deactivate.

Example

/reminder delete reminder_id:3

List all active reminders for this server.

This command takes no options. It shows every active Ruins/Altar reminder and every active custom reminder, with each one’s channel, the role it pings, and its intervals. Custom reminders also show their ID and how often they repeat. If there are many reminders, the list is split into pages you can flip through. The response is only visible to you.

Example

/reminder list
  1. Make sure your server is authorized. If /reminder does not appear, run /patreon verify (with Manage Server) and wait a few seconds.
  2. Pick a channel for the pings, for example #reminders, and confirm the bot can send messages there.
  3. Find the next occurrence in UTC. Work out the date and time of the next Ancient Ruins or Altar of Darkness, written as HH:MM DD/MM/YYYY.
  4. Run /reminder setup. Choose the channel, the event type, the first and last instance, and which lead-time reminders you want.
  5. Tell members to use the role menu in the channel to subscribe to the pings they want.
  6. (Optional) Add your own events with /reminder custom, and check everything with /reminder list.
  • Who can run setup, deactivate, custom, and list: members with Administrator or Manage Server, or the server’s configured Bot Admin role.
  • Who can run delete: members with Administrator or Manage Server, or the server’s Bot Admin role.
  • Server authorization: the server must be authorized through Patreon, or the commands do not appear.
  • Bot permissions: the bot needs Send Messages in the reminder channel and Manage Roles (to create the Ruins/Altar roles). For Discord Scheduled Events, it also needs Manage Events.
  • All times are UTC. Enter dates as HH:MM DD/MM/YYYY. Double-check the offset from your local time.
  • One active reminder per built-in type. You cannot have two active Ancient Ruins reminders (or two Altar reminders) at once. Deactivate first to change one.
  • Checks run every minute. The bot looks for due reminders on a one-minute cycle, so pings land close to their scheduled time.
  • custom_intervals overrides the toggles. If you provide a list of intervals, the 1/4/8-hour toggles are ignored for that reminder.
  • Default interval is 4 hours. For /reminder setup, if you choose nothing, you get one reminder 4 hours before each occurrence.
  • Custom reminders need an end or never. A repeating custom reminder runs until its last_instance date, or forever if you set last_instance to 0 / never.
  • “Invalid date format.” Use HH:MM DD/MM/YYYY in UTC, for example 20:00 25/12/2026. The time comes first, then the date.
  • “A reminder is already active.” That event type is already set up. Run /reminder deactivate for it first, then set it up again.
  • “event_length is required.” You turned on discord_events for a custom reminder without giving a duration. Add event_length, for example 1h.
  • “I lack Manage Events permission.” You asked for Discord events but the bot cannot create them. Grant Manage Events and try again.
  • Members are not getting pinged. Make sure they subscribed via the role menu (for Ruins and Altar), or that the custom reminder’s role_to_ping is set. Also confirm the bot can still send messages in the channel.
  • I can’t find a custom reminder’s ID. Run /reminder list. Each custom reminder shows its ID at the start of its entry.