/recurrence
Set a recurring schedule on an event. The bot automatically generates the next occurrence within a rolling 28-day window.
Premium feature. Requires an active premium subscription or trial.
Usage
/recurrence <event_name> <type>
Parameters
| Parameter | Required | Options | Description |
|---|---|---|---|
event_name | Yes | — | Name of the event to configure |
type | Yes | weekly, biweekly, monthly, none | Recurrence schedule |
Permission
Organizer of the event, or Admin
Requirements
- The event must have a
confirmed_dateset — run/eventsand confirm a slot first - The server must have an active premium subscription
How It Works
A background task runs every 15 minutes and checks for events with recurrence enabled. When the most recent occurrence is within 28 days of expiry, it generates the next child event.
Child event naming:
{Parent Name} - {Date Label}
Example: Weekly Raid - Mon Jan 13
Each generated child event:
- Inherits the same time slot duration as the confirmed parent
- Posts its own bulletin embed in the configured channel
- Is independent — members RSVP and confirm it separately
- Can have recurrence disabled individually
Disabling Recurrence
Set type to none to stop generating future occurrences. Existing child events are unaffected.