Recurring events
A weekly raid, a monthly town hall, a stream every Tuesday and Thursday: you create it once with a repeat rule, and FlaviBot produces the occurrences.
Two things to keep apart, because everything on this page follows from the difference:
- The series is the rule and the shared details: title, description, place, capacity, sign-up slots, reminders, kind, team, and so on. It is never displayed on its own and never has a panel.
- An occurrence is one date produced by the rule. Each one is a normal event: its own panel, its own RSVPs, its own reminders, its own Discord scheduled event when the rule cannot be mirrored as one. Members sign up for the occurrence they want, not for the series.
Writing the rule
In the create form, Repeat offers Daily, Weekly, Monthly, Yearly and Custom. The quick choices repeat every day, every week on the start's weekday, every month on the start's date, every year on the start's date. Custom opens the full editor:
| Repeats | Options |
|---|---|
| Daily | Every N days. Optionally only on some weekdays, for a "weekdays only" schedule |
| Weekly | Every N weeks, on one or more weekdays |
| Monthly | Every N months, either on day N (1 to 31, or last day) or on the Nth weekday (first to fourth, or last) |
| Yearly | Every N years, on a month and a day |
Every N goes up to 99. Ends is Never, On a date (at most two years ahead) or After N occurrences (at most 365); pick both and whichever comes first wins. A summary sentence under the editor reads the rule back to you: "Every 2 weeks on Monday and Wednesday, until 12 Dec 2026".
Three details of how dates are produced:
- The start you type is the first occurrence, provided it fits the rule. A weekly-on-Monday series started on a Wednesday begins the following Monday.
- Occurrences keep the local time of the start in the event's timezone. A 20:00 raid stays at 20:00 through a daylight-saving change; the instant moves, the wall clock does not.
- A monthly rule on day 31 skips the months that do not have one; use last day for "the end of every month".
The same rule is available from Discord, in a shorter form: /event create … repeat:weekly repeat_until:2026-12-31. The choices there are none,
daily, weekdays, weekly, biweekly, monthly and yearly, always on
the start's weekday or date.
How many occurrences exist at a time
FlaviBot does not post a panel for every future date. The setting Occurrences posted ahead (1 to 5, in the module's Settings tab) says how many upcoming occurrences have a panel at any moment. The default is one.
- Those occurrences are real events, taking sign-ups and reminders.
- Every later date is still on the calendar, drawn dashed with a ↻, so the month view shows the whole season. It gets its panel when its turn comes.
- When an occurrence ends, the next one is posted about a minute later, so the channel always has the coming date ready to sign up for.
Raise the number when your members like to book the next few weeks at once; keep it at one when a single "this week" panel is enough. Remember that each posted occurrence counts toward the server's active-event cap.
When the rule runs out (its end date passed, or its count is reached) the series ends on its own after its last occurrence, and no new dates appear.
Editing
Open any occurrence and press Edit. The form asks whether you are editing this occurrence or the whole series.
This occurrence changes that date alone and marks it as detached: it keeps its own title, time or place from now on, and later edits to the series leave it alone. Use it for "the meeting is at 21:00 this week only".
The whole series changes the rule and the shared details:
- Change the title, description, place, capacity, sign-up slots, hosts, kind, colour, team, reminders, start announcement or Discord sync, and every posted occurrence that was not detached is updated in place: its panel is repainted, members keep their RSVPs.
- Change the start time, timezone or repeat rule, and the occurrences that had not started yet are cancelled and posted again on the new dates. That is the honest outcome of moving a series: a panel for "Tuesday 20:00" cannot become "Thursday 19:00" and keep everyone's answer meaningful. Occurrences that are already live finish as they were, and detached ones are untouched.
Where you open the series from decides which of those two you can change:
- From a posted occurrence, move the start time or timezone and the whole series shifts by the same amount. The repeat rule is shown there but not editable.
- From a dashed occurrence, one without a panel yet, change the repeat rule. Its date, time and timezone are locked, since that occurrence's own date is not the series' start.
A dashed occurrence cannot be edited by itself: edit the series instead, or wait until it is posted.
Dragging an occurrence to another time in the calendar asks the same
question, this occurrence or the whole series, with the same
outcomes; a dashed occurrence cannot be dragged at all. From Discord,
/event edit on an occurrence always changes that occurrence alone, and
detaches it the same way. See
moving an event by dragging.
Cancelling
Cancelling an occurrence asks the same question.
This occurrence cancels that date and records it as an exception in the rule: the series carries on, and that date never comes back, even if you later change the rule. Use it for a skipped week.
The whole series cancels every occurrence that had not started, lets a
live one finish, removes the series' native Discord event, and stops
producing dates. From Discord that is /event cancel reference:<id> series:True; without series the command cancels the one occurrence.
What members see
The panel of an occurrence carries a Repeats line with the rule in plain
words, so someone reading "Every week on Tuesday" knows there will be a next
one. /event list marks occurrences with ↻ and shows their kind and, on
an event with sign-up slots, the count per slot; so does the Next up list
on the dashboard.
Reminders, the waitlist, the slots and the calendar entries all work per occurrence. A member who said Going to this week's raid has not said anything about next week's; that is by design, and it is why the panel is posted fresh each time. To copy one occurrence as a stand-alone event, open it and press Duplicate.
Next: Discord scheduled events.
