EventsRSVP events with capacity, reminders, and recurrence.

Overview

Create a community event once, collect Going, Maybe, and Declined RSVPs, and keep attendees updated with reminders, capacity limits, and recurrence.

What Events can do

  • Live RSVP cards - members react with Going, Maybe, or Declined, and the event message updates its counts.
  • Capacity and waitlists - set a Going limit and show waitlist totals when the event fills up.
  • Automatic reminders - post reminders before the event, in the event channel or by DM.
  • Recurring events - repeat daily, weekly, or monthly until an optional end date.
  • Dashboard management - create and manage events from the Events page without using commands.

Permission required

Manage Guild

Creating an event, previewing it, and using the setup wizard require Manage Guild. The event host or a member with Manage Guild can edit, remind, cancel, or delete an event. Everyone can list, view, and check the attendee list for an event.

Quick start

Open the guided setup and answer the prompts in the channel:

Fluxer
f!events setup

Send skip to leave an optional prompt blank, or cancel to stop. After the questions, the bot posts a preview and asks you to confirm it.

You can also create an event in one command:

Fluxer
f!events create Game Night | 2026-11-14 20:00 | tz:Europe/London | channel:#events | capacity:20 | remind:24h,1h

The command form is f!events create <title> | <when> | [flags]. Use f!events preview with the same arguments to preview without creating anything.

Event flags

FlagWhat it does
desc:Description shown on the event card.
end:End time. Required for recurring events.
tz:IANA timezone for the event, such as Europe/London.
channel:Channel where the event card is posted. Defaults to the current channel.
location:Location shown on the card.
capacity:Maximum number of Going RSVPs, from 1 to 1000.
waitlist:Enable or disable the waitlist with yes or no.
remind:Comma-separated reminder offsets, such as 24h,1h. Minimum offset is 1 minute.
dm:Also send reminders by DM.
ping:Role to ping for the event.
require:Role required to RSVP.
repeat:daily, weekly, or monthly.
repeatuntil:Stop recurring after this time.
color:Event accent color, such as #A52F05.
image:HTTP or HTTPS image URL for the event card.
footer:Custom footer template for the card.
going: maybe: declined:Custom emojis for the three RSVP reactions.
goinglabel: maybelabel: declinedlabel:Custom labels for the RSVP choices.

Description and footer templates support {title}, {host}, {start}, {end}, {location}, {capacity}, {going}, {waitlist}, and {requirements}.

Time formats

The start and end time accept any of these formats:

  • YYYY-MM-DD HH:mm - a date and time.
  • YYYY-MM-DD - a date at midnight.
  • A Unix timestamp, such as <t:1763150400>.
  • A relative duration, such as 2h or 3d.

Add tz:when the time should be read in a timezone other than the host's saved timezone.

RSVPs, capacity, and waitlists

Members react with the configured Going, Maybe, and Declined emojis. The card keeps the counts up to date and the who command shows the full attendee list.

With capacity: set, the card shows Going against the limit and tracks waitlisted members. Set waitlist:no if you do not want a waitlist. Use require: to limit RSVPs to a role.

Recurring events

Add repeat:daily, repeat:weekly, or repeat:monthly to run an event more than once. Recurring events need an end: time, and the bot schedules the next occurrence automatically.

Add repeatuntil: to stop after a specific time. Without it, the event keeps repeating until you cancel or delete it.

Limits and channel permissions

  • Up to 25 active events per community.
  • Capacity can be between 1 and 1000.
  • An event can last up to 30 days.
  • The bot needs View Channel, Send Messages, Embed Links, and Add Reactions in the event channel.

Dashboard

The Events page in the dashboard can create, edit, and manage events alongside the Fluxer commands. Open it from your community's dashboard sidebar under Events.